Age | Commit message (Collapse) | Author |
|
Port 0e9668051e58b2ff4e48b82fa7cc17d385c7a5c9 to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
Fixes #647
The option is found in `/settings` (because that was easier to write it this
way) but only affects the glitch-soc front-end.
|
|
blocked
Port 111a0628fc161df4d76967d7dc7116b8a43fe8e2 to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
|
|
Port 7de8c51873b51d8450f7a6597a43d454964d0407 to glitch-soc
|
|
Port 729723f857d11434c0f78d63fe16537d77f1c77c to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
|
|
Port 84ff3938426da348e31651dfad376d83a9784343 to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
Port front-end changes from e64e6a03dd1e0978fee48f0596dcfbc7fd29958f to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
Port 3086c645fde2345d34e401bdf3e2f19f19da3294 to glitch-soc
|
|
Port 5b20284f6f7ebb2514d81fb27fcaa40f8edf14ff to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
|
|
|
|
Port 1e5532e693d9533ee37f553aeb191e284178fa52 to glitch-soc
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
|
|
Inspired by https://github.com/kubevirt/kubevirt/issues/1242
|
|
|
|
|
|
This reverts commit 49bea8c46b006d8c86285c8b1158cd700dc2eb45.
|
|
Port 68f2211f00dfa3f823ad780ed748c1af0078a0cf to glitch-soc
|
|
Port db06b25376ac7e844e86fb9890fa9f1c2edd2d60 to glitch-soc
|
|
mounted
Port be1c634b2b4372a525d304d2ff830392f04c5cc5 to glitch-soc
|
|
Also does not enable polls if no limits are provided by the server
|
|
Port 5092d17f2936146fa26e5d8a9b9e391f77010f28 to glitch-soc
|
|
This fixes crashes in pleroma when writing toots with a content warning,
since pleroma inserts a “nsfw” hashtag that isn't part of the toot's text.
|
|
Port compatibility changes from 8f5fdab5bf681ff45a07965940bc45c9061a2f89 to glitch-soc
|
|
Port 2ee779dcd3aaec4f1384400ba68e2422ea878156 to glitch-soc
|
|
Port relevant parts of 9d4541c612b506889675c4c19ced5cd17ad3710f to glitch-soc
|
|
|
|
Port bb5558de627ca9bc26949570025f6193cd7cbd98 to glitch-soc
|
|
|
|
e.g., typing “blob_cat_p” used to search for “blob” and “cat”, but not
“blob_cat_p”, which means “blob_cat_patpat” is very unlikely to show up,
although it is likely what the user wanted to type in the first place.
|
|
Fixes #778
|
|
Port f7a6f9489da9b2a1820366654df47b8a52f5c5bc to glitch-soc
[API] [vanilla required] [glitch-soc optional] initial_state show_sensitive_media boolean changed to show_media string with options "default", "hide_all", "show_all"
|
|
|
|
Port a060beee726de5295e1f608231975a90b7709a0a to glitch-soc
|
|
Fixes #678
|
|
Port 7901f9f63e156732ab10154c34f3c2d188471a9d to glitch-soc
|
|
Port 460e380d386367b6809d319859e13d17a6a2acea to glitch-soc
|
|
Inspired by f9b23a5d6247445ea5b70b431c934a4bb99213bc
|
|
|
|
Port Mastodon's hashtag stats thing to glitch-soc.
This doesn't change how hashtags are ordered, and doesn't add a trending
hashtags section, but it does change how hashtag searches are rendered,
displaying a trend line alongside each hashtag.
|
|
|
|
Upstream's implementation has been merged a while ago and is the preferred
way to set fields, as it is the only one compatible with upstream and is
more user-friendly.
This commit deletes the legacy glitch-soc FrontMatter functionality in order
to clean up the code and make it easier to maintain.
|
|
Port WebUI part of 0fb0037ca7ea9910b490818a1cc13f4005ba6134 to glitch-soc
|
|
|
|
Port c75493755f482d0506884b1f7b7b44e5306a4d8b to glitch-soc
|
|
Fixes #541.
|
|
See also the following commits:
- 0c3ce41031d292734e0e4cc70d227228d1993bea
- 268d90e8103770e8b90f6d5680a466c1ec83c6ff
|
|
So far, glitch-soc used history.length to decide whether to call `goBack()` or
go to / in order to not leave the webUI. This made clicking the “Back” button
go to the “Getting started” column instead of going back in the browser's
history when such an action would leave the web UI, but also when:
- The WebUI is refreshed (F5)
- A tab is restored
- The history length reaches its maximum (e.g., 50 in Firefox)
This commit fixes these shortcomings by checking `window.history.state`.
Indeed, we only want to go back in the browser's history when the current
location has been reached from within the WebUI, which only happens via
`pushState` as far as I know. Since browser store the serialized state in
the browser history, this also survives page reload and session restoration.
|
|
Port dafd7afc5ef94fc9513efa341910f7e3c31b909a to glitch-soc
|