| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
Port 0ba49eca8b49c6ce0ec04fd546951c95938da4e6 to glitch-soc
|
|
Port 9a1a55ce526c956ac6b35897d483c316b7ad4394 to glitch-soc
|
|
Port 0128b86d3098042cdbc3a1629f74b70f665f8dfb to glitch-soc
|
|
|
|
Port d185f3ddafc941e280de7efc6d448449ab5ce2c9 to glitch-soc
This doesn't change anything for glitch-style fields, but those will go
away eventually
|
|
Port the UI part of 76f3d5d16be2fb97d2252909589510165ec05e12 to glitch-soc
|
|
Unlike boosts and like, there is no confirmation dialog as misclicking
can be recovered without another user seeing it.
|
|
|
|
Port 51310125051a75ef7af4e8ffc8b6532c151e96b6 to glitch
|
|
|
|
Fix glitch async chunks
|
|
|
|
#6223)
|
|
flavours/glitch/util/initial_state is used in places where we want to
exhibit different behavior based on user preferences. This means that
it's used in places where no preference is defined, i.e. on an
unauthenticated access. All values exported from that module must
therefore expect that case; previously, the max chars value didn't.
Addresses #306.
|
|
Threaded mode~
|
|
|
|
max_toot_chars is present in the root of the initial state object.
(Previously, we were trying to read it from the meta child object.)
|
