Post Awu0Y64zfuugJJ7xfE by sysrq@lab.nyanide.com
(DIR) More posts by sysrq@lab.nyanide.com
(DIR) Post #AwrC4CaJXZozm3PPay by lain@lain.com
2025-08-05T10:39:32.400248Z
3 likes, 14 repeats
In your daily use of Pleroma/Akkoma, what are you most unhappy about?
(DIR) Post #AwrDJHDWhQBwRIVC4G by mint@ryona.agency
2025-08-05T10:53:26.650896Z
7 likes, 1 repeats
@lain https://git.pleroma.social/pleroma/pleroma/-/issues/3363
(DIR) Post #AwrDKQSXp3OLOR4gpk by kaia@brotka.st
2025-08-05T10:53:33.968415Z
4 likes, 0 repeats
@lain - AkkoFE is serviceable, but especially on mobile quite difficult to use due to small buttons. a new mobile-first FE would be neat!- when mentioning users with @ I want the people I interact with most mentioned first. when I enter (at)la, I don't want Latinix@randominstance. I want the current account to be first, not the account the person used last century.- I'd like some indication when I cannot contact a user, when the message transfer fails. could there be delivered marks for direct messages like Signal?
(DIR) Post #AwrDQgRvHjRAirlfjU by PurpCat@clubcyberia.co
2025-08-05T10:54:48.009573Z
0 likes, 2 repeats
@lain the css load screen on new versions
(DIR) Post #AwrDf2rYkUlaI6biFs by bajax@baj.ax
2025-08-05T10:57:24.901754Z
1 likes, 0 repeats
@lain slow frontend(I know I can change it I'm just lazzy)
(DIR) Post #AwrDzZ50g1KG0AgPom by i@declin.eu
2025-08-05T11:01:05.892118Z
1 likes, 0 repeats
@lain the database is sad to think about, the backend is a mess no one wants to touch, federation and transparency/discovery is out of vogue, and the network still reeks of mastodon
(DIR) Post #AwrGNbWfQwr8RkD69Y by thatbrickster@shitposter.world
2025-08-05T11:27:52.974460Z
3 likes, 2 repeats
@lain When Pleroma hit the scene, one of its main selling points was how lightweight it was. I feel that with subsequent major releases it has gotten heavier and more unwieldly.Perhaps it's time Pleroma shed some weight. Remove unfinished code paths or simplify existing ones. I have expressed interest in improving the front-end, specifically the admin dashboard, but it's too convoluted for me to get started.I refrain from mentioning the limitations of the AP protocol, such as the lack of groups facilitation, as it's a meta meme at this point.
(DIR) Post #AwrGjrROwUcEB2MNXM by sun@shitposter.world
2025-08-05T11:31:53.745111Z
3 likes, 1 repeats
@lain do a release for the unlisted bug
(DIR) Post #AwrINSl2EY4nA0zVA0 by romin@shitposter.world
2025-08-05T11:50:15.745717Z
0 likes, 1 repeats
@lain using bleroma
(DIR) Post #AwrIfKsSGsMjvsz4YS by takao@shitposter.world
2025-08-05T11:53:29.737511Z
0 likes, 1 repeats
@lain Fe is bloated (but there's at least bloat)
(DIR) Post #AwrLbsed2yGPOVYqKu by voice@soc.magicalmirro.red
2025-08-05T12:25:00.981128Z
1 likes, 0 repeats
@lain need to open posts on the original server to see all replies.
(DIR) Post #AwrLg31aQrvWiQHowK by len@nyan.network
2025-08-05T10:56:32.831886Z
2 likes, 0 repeats
@lain FE is a bit too heavy on old phone so I'm reliant on Husky as only performant phone app for it, and Husky has no good emoji react support. (This is probably not something you can do anything about.)I've regularly heard complaints about the admin side of stuff and how hard it is to do things (specifically acting on and dealing with individual reports).Something going viral and notifications is a sad combination.
(DIR) Post #AwrLnQXHPtotf3d5Hs by lain@lain.com
2025-08-05T12:28:33.186270Z
0 likes, 1 repeats
@kaia > could there be delivered marks for direct messages like Signal?that's hard to do because AP is fire-and-forget, you don't actually know if the other side has ingested it. but it's a good feature.
(DIR) Post #AwrLpE7cXfqLjuUAqG by foxcat@pl.foxcat.lol
2025-08-05T10:45:37.880636Z
1 likes, 0 repeats
@lain cant rly think of much bad to say about it tbh
(DIR) Post #AwrM9QxKXF7fKqJ9GK by hj@shigusegubu.club
2025-08-05T12:32:27.913251Z
0 likes, 0 repeats
@kaia @lain >AkkoFE is serviceable, but especially on mobile quite difficult to use due to small buttons. a new mobile-first FE would be neat!Try PleromaFE today! https://akkoma.dev/AkkomaGang/akkoma/pulls/945It's actually built with mobile in mind! You can change the scale!image.png
(DIR) Post #AwrMDiQvUrFshNC1gW by lain@lain.com
2025-08-05T12:33:18.419578Z
0 likes, 1 repeats
@len can i ask you what phone you are using?
(DIR) Post #AwrMNoYhZrQuale4iO by hj@shigusegubu.club
2025-08-05T12:33:01.344906Z
0 likes, 0 repeats
@mia @lain >someone dedicated to identifying issues and working on interface design/guidelinesthat's me!
(DIR) Post #AwrMTSZsDQKm9ksx8K by dwaltiz@pleroma.soykaf.com
2025-08-05T12:35:44.440515Z
1 likes, 0 repeats
Searching for posts still sucks. Most times it finds nothing, even for popular terms in public posts. It's a game of chance.
(DIR) Post #AwrNUWbqoJAYu9sk3k by i@declin.eu
2025-08-05T12:47:32.002206Z
0 likes, 0 repeats
@hj @lain @mia now if only you could find the time to implement them, nlnet/opencollective bounties haven't helped attract outside help either
(DIR) Post #AwrOGcMMjadQdfZTvc by yew@misskey.bubbletea.dev
2025-08-05T12:56:15.150Z
6 likes, 0 repeats
@lain@lain.com after years of using pleroma/akkoma i still don't know what a corndog tastes like
(DIR) Post #AwrOQt3bVb7bJwgzce by hj@shigusegubu.club
2025-08-05T12:58:00.327022Z
2 likes, 0 repeats
@i @lain @mia it did help attract two people ( @vaartis and @yew ) , but both are one-off help, i'm afraid :(
(DIR) Post #AwrOSU7bBo8oZ0K55s by yew@misskey.bubbletea.dev
2025-08-05T12:58:23.970Z
0 likes, 0 repeats
@lain@lain.com something i really like about misskey is the antennas. pleroma doesn't have anything like it at least exposed to users
(DIR) Post #AwrOWLpTxgFm0Jh0Ay by hj@shigusegubu.club
2025-08-05T12:59:03.538677Z
2 likes, 0 repeats
@yew @lain i know one person who would really benefit from it. ( @lebronjames75 searching for "lebron" )
(DIR) Post #AwrOYsxNlWrLKHb1mq by yew@misskey.bubbletea.dev
2025-08-05T12:59:30.737Z
2 likes, 0 repeats
@hj@shigusegubu.club @i@declin.eu @lain@lain.com @mia@shrimptest.0x0.st @vaartis@pl.kotobank.ch im on it i just had to first learn vue and then ask about many things a documentation of pleroma-fe could have explained faster
(DIR) Post #AwrOfFBW2GGy0DEsW8 by lain@lain.com
2025-08-05T13:00:40.959328Z
1 likes, 1 repeats
@yew what's that?
(DIR) Post #AwrOlVcBrS9WhIhexk by yew@misskey.bubbletea.dev
2025-08-05T13:01:50.430Z
1 likes, 0 repeats
@lain@lain.com it let's you "listen" to posts. you can specify how and what to filter for, and you then get a separate antenna timeline. for instance i have an antenna for yew that includes terms related to yew and then gives me all posts mentioning it, from users i follow or not alike.
(DIR) Post #AwrOwSyg0UabhfRhmS by hj@shigusegubu.club
2025-08-05T13:03:43.687715Z
0 likes, 0 repeats
@lain having to do almost everything in the project myself :(And I guess also file names/file titles still not being a thing and everything on NLNet grant list https://git.pleroma.social/pleroma/pleroma-meta/-/issues/71
(DIR) Post #AwrQLYY8WlwgB6Yl7Y by i@declin.eu
2025-08-05T13:19:31.449299Z
1 likes, 0 repeats
@lain @yew like a MRF, but for sorting posts into custom timelines via user supplied rules
(DIR) Post #AwrTuHGF681GYYRCgS by phnt@fluffytail.org
2025-08-05T13:59:26.629413Z
2 likes, 1 repeats
@lain Lack of Release Candidates for testing before release. There's basically no public communication when a release is going to happen besides maybe a post from one of the maintainers that's easy to miss. Currently those who run develop to catch bugs have no idea when to merge upstream besides checking the commit history every few weeks and guessing.The whole 2.7.0 Oban blowing up and follows refusing to work 90% of the time debacle could have been prevented by it, if enough instances admins actually knew when to test stuff.
(DIR) Post #AwrVCpx8x7gRJmuytU by Ripsnort@poa.st
2025-08-05T14:14:00.783458Z
0 likes, 0 repeats
@lain Seeing faggots with gay shitty opinions on my timeline
(DIR) Post #AwrVK9J7OLQTN7gQXQ by jra@soc.jra.sh
2025-08-05T14:14:48.373078Z
3 likes, 0 repeats
@lain My main gripe is the search on pleroma-fe. Its internal logic for selecting which posts to show feels like the Sephirothic Tree.
(DIR) Post #AwrYA4o5ZLwqNf3faC by i@declin.eu
2025-08-05T14:47:05.351938Z
0 likes, 0 repeats
@phnt @lain would have helped if security issues weren't the only reason those releases were made in the first place, usually it's not enough to report them either way until someone like misskey says to fix it or get bent
(DIR) Post #AwrYVtMumF8lHBkZZQ by dwaltiz@pleroma.soykaf.com
2025-08-05T14:48:18.638947Z
0 likes, 0 repeats
@jra @lain most of the time it finds nothing and instead tries to look for users
(DIR) Post #AwrYVuLBABLWI5whVI by i@declin.eu
2025-08-05T14:51:00.537963Z
0 likes, 0 repeats
@dwaltiz @lain @jra the postgresql implementation is definitely trash no matter if it's rum'd or not, and doing four different searches in one query is weird, but at least search is the only thing you can run a different backend for, as expensive as meili/elastic search are
(DIR) Post #AwrcDnC7ORyujQKDh2 by Mercurial@lab.nyanide.com
2025-08-05T15:32:36.239837Z
1 likes, 1 repeats
@lain not enough people :P
(DIR) Post #AwrcWltiRHc8DBlduy by mint@ryona.agency
2025-08-05T15:35:59.843596Z
0 likes, 1 repeats
@i @lain @dwaltiz @jra Elastic isn't even merged as far as I know. I've fixed meili but didn't account for updating indexes on post edits, and it pinned cores at 100% and raped my SSD lifespan anyway.
(DIR) Post #AwrcfwPwhCtHRdDP0q by lain@lain.com
2025-08-05T15:37:39.993118Z
0 likes, 1 repeats
@dwaltiz @jra can you give me an example query?
(DIR) Post #Awrduwo7d0rAx5F7Ue by phnt@fluffytail.org
2025-08-05T15:51:34.866064Z
0 likes, 1 repeats
@i @lain Do you respond with something else besides complaints when talking about Pleroma?
(DIR) Post #AwrdzMrShcKmumuejw by dwaltiz@pleroma.soykaf.com
2025-08-05T15:51:35.107896Z
0 likes, 0 repeats
@lain @jra "akkoma"
(DIR) Post #AwrdzO5g8FIgjAZWXQ by lain@lain.com
2025-08-05T15:52:22.991360Z
0 likes, 1 repeats
@dwaltiz @jra thanks!
(DIR) Post #AwrgUzbSuVnzxMdcvI by i@declin.eu
2025-08-05T16:20:31.306105Z
0 likes, 0 repeats
@phnt @lain usually i'm the only one responding to requests for help debugging issues on the twkn, or reporting fixes with diffs for develop, or sharing custom modulesbut just like glussy you disrespect lain for not owning the project and all you get is a permanent gitlab ban
(DIR) Post #AwsAzx2PUnilbNv5H6 by vriska@lizards.live
2025-08-05T22:02:11Z
1 likes, 0 repeats
@lain i would use pleroma if i could get a 1:1 recreation of the tweetdeck style 3 column layout on the FE
(DIR) Post #AwsDHRJOOJTSKHKVbU by Ree@shitposter.world
2025-08-05T22:27:50.705491Z
0 likes, 1 repeats
@lain no groups
(DIR) Post #AwsDXrqvTrAxH4qfCq by genmaicha@stereophonic.space
2025-08-05T22:30:49.302668Z
1 likes, 0 repeats
@lain - search doesn't work well- I want to be able to follow tags, e.g. #wikifinds- groups or some form of granular post scope would be coolotherwise, I'm a huge fan of the UI, especially how customizable it is. I'd hate to see it change.
(DIR) Post #AwsInthcryXdPrxf7I by Nudhul@shitposter.world
2025-08-05T23:29:45.466394Z
0 likes, 1 repeats
@lain jason is always slacking off
(DIR) Post #AwsIquPggSIwUO0TcO by Nudhul@shitposter.world
2025-08-05T23:30:18.069388Z
1 likes, 1 repeats
@lain also search is very tempermental
(DIR) Post #AwsK891nhRPqh1cGyu by nerthos@shitposter.world
2025-08-05T23:44:36.888164Z
1 likes, 1 repeats
@lain The pleroma foundation has not responded to my requests to add backend furry doxxing functionality.
(DIR) Post #AwsKE8zWkUdKJhPi5I by nerthos@shitposter.world
2025-08-05T23:45:42.221399Z
0 likes, 1 repeats
@lain As for a real answer, scopes. Scopes are the AIDs of fedi and should never have been supported.
(DIR) Post #AwsKZ2oKvHk5EI94ZU by nyanide@lab.nyanide.com
2025-08-05T23:49:27.993039Z
1 likes, 1 repeats
@lain The regressions introduced in new releases which do something weird like use some more ram for some reason. Having run Pleroma alongside other fedi software on another persons machine they complain my Pleroma uses the most ram on their system. It's weird to see.
(DIR) Post #AwsLfvknevfPK8L3WS by scathach@stereophonic.space
2025-08-05T23:50:09.212457Z
0 likes, 0 repeats
@nerthos @lain I like scopes
(DIR) Post #AwsLfx2ur3khKbp2Om by nerthos@shitposter.world
2025-08-06T00:01:53.902860Z
1 likes, 1 repeats
@scathach @lain I think they go completely against the original point of the network as a microblogging network for people to find stuff and talk with random people, and has further fragmented everything into little niches and broken timelines and "you need to follow 6000 people with penis cage symbol accounts or you can't see half the timeline"
(DIR) Post #AwsLrOf2WWWUAA6zku by scathach@stereophonic.space
2025-08-06T00:03:07.055248Z
2 likes, 0 repeats
@nerthos @lain Nah I like followers only scope
(DIR) Post #AwsLrQ4FIIHOWcudgO by nerthos@shitposter.world
2025-08-06T00:03:58.882910Z
0 likes, 1 repeats
@scathach @lain zoomer. I miss early 2010s fedi, just public and DM.
(DIR) Post #AwsM1LThDF3lBeY9Ee by nerthos@shitposter.world
2025-08-06T00:05:47.453163Z
0 likes, 1 repeats
@arcana @lain @scathach Respectable
(DIR) Post #AwsjvyXbSiDtV8Ljw8 by lain@lain.com
2025-08-06T04:33:42.900788Z
1 likes, 1 repeats
@nerthos @scathach and DMs were public too sometimes
(DIR) Post #Awsk3Wd77QhzFkWkV6 by patchuun@social.xenofem.me
2025-08-05T22:07:31.429787Z
1 likes, 0 repeats
@lain I use the RIA on my phone and sometimes I have to close and relaunch it to get my notifs and timelines to refresh but I could probably just be using husky or whatever I guessidk, not a huge deal just a minor annoyance
(DIR) Post #Awsk97Lk1TzeaM4H68 by scathach@stereophonic.space
2025-08-05T22:00:55.634479Z
2 likes, 0 repeats
@lain I'm mostly quite happy with Pleroma, I only have a few things I wish were different:- Search function is basically useless, no way to search my own posts- No good way to browse historical posts, something like a by month/year calendar view like wordpress and livejournal blogs have would be really sweet- /bookmarks endpoint is very slow and tends to time out for some reason, though this might be more of a stereophonic issue- Account archive is missing quite a lot of information
(DIR) Post #AwslfVCB05UxlKbGeO by nerthos@shitposter.world
2025-08-06T04:53:10.662328Z
1 likes, 1 repeats
@lain @scathach On the new implementation (which pleroma uses) yes, in the original implementation (statusnet) they were separate from regular posts, they didn't work across instances but they were more secure within the same instance.
(DIR) Post #AwsllhVG9YvffiTvhw by rude@kys.moe
2025-08-06T04:54:15.969550Z
0 likes, 0 repeats
@lain The notifications query randomly taking 11 seconds to respond. :Rage: Also the pleroma systemd service lying to my face about its state when the database is taken down.
(DIR) Post #AwsmzP9bGwhElqRudc by feld@friedcheese.us
2025-08-06T04:51:10.405565Z
0 likes, 0 repeats
@thatbrickster @lain man I don't get it. I run it on the slowest "server" and it is still so capable and fast. Subscribed to tons of relays, tens of gigabytes for the database, millions of posts, only 4GB of ram and 4 basically celeron coresWhy is it slow for other people ???
(DIR) Post #AwsmzQeThczRPtu5PE by lain@lain.com
2025-08-06T05:07:56.668030Z
1 likes, 1 repeats
@feld @thatbrickster that was one of the reasons I posted this question, my instances run hands-off on small systems without any issues, so I wanted to see if hat other people’s experience is
(DIR) Post #AwsplFcMEM7V0FqJbk by ewen@social.ewenbell.com
2025-08-06T04:58:52.854278Z
1 likes, 0 repeats
@lainSearch is not great. Really wish I could just find old posts from my own account more easily.SoapboxFE is a slick interface but still a work in progress. Not everything works properly.PleromaFE is very busy and not very tunable. Wish it could be tweaked to operate more like the advanced mode of Mastodon.Muting words doesn't work in SoapboxFE or FediLabs App.
(DIR) Post #AwsprgOJbGxxmFLEcC by feld@friedcheese.us
2025-08-06T05:22:45.780000Z
3 likes, 0 repeats
@hj @lain @yew @lebronjames75 we just need to rewrite the query to use search ranking: friends highest, next best matches weighted by most recent activity date maybe (it's already tracked in the users table)It's on my mind, just need to do it
(DIR) Post #AwsrlfKKqNEAeCjqUK by feld@friedcheese.us
2025-08-06T04:52:34.355460Z
0 likes, 0 repeats
@dwaltiz @lain searching from an app gives you better results than in PleromaFE. I don't know why, it's something to do with the query parameters PleromaFE uses by default
(DIR) Post #AwsrlgYuFgTeTgYzq4 by dwaltiz@pleroma.soykaf.com
2025-08-06T06:00:31.384265Z
1 likes, 0 repeats
@feld @lain Searching from Husky doesn't give any results either. Maybe Soykaf is just borked to hell
(DIR) Post #Awst9gRURqj50k6MXw by feld@friedcheese.us
2025-08-06T06:12:25.004508Z
0 likes, 0 repeats
@dwaltiz @lain I think soykaf runs releases not develop branch
(DIR) Post #Awst9hy8lwRBkINx4q by lain@lain.com
2025-08-06T06:17:01.999330Z
0 likes, 1 repeats
@feld @dwaltiz si
(DIR) Post #Awsu3LKO8eZLk4Jv60 by phnt@fluffytail.org
2025-08-06T06:27:07.163605Z
1 likes, 1 repeats
@lain @feld @thatbrickster It's because you aren't running them on a $5 shitbox from $insert_cheap_host. 4 cores and 4 GB of RAM is probably more resources than half of the instances.You can run on those garbage tier VMs, but it needs a little bit of hand holding every few weeks after the first few months. And it doesn't help that these configurations are in the Postgres docs. https://docs.pleroma.social/backend/configuration/postgresql/#example-configurations
(DIR) Post #Awsvq8ycwpCDa0yXyK by phnt@fluffytail.org
2025-08-06T06:47:08.698513Z
2 likes, 1 repeats
@lain @feld @thatbrickster I would say that 1 core and 2GB RAM (with ~2GB swap) is the minimum that is still usable and not in the absolute jank territory. I used to run this instance on that for two years and it did mostly hold up, but I spent probably a few hours configuring Postgres, and opening two different threads in different tabs at the same time would kill it in the end.
(DIR) Post #AwswlO2DdRp4msx1nM by snacks@netzsphaere.xyz
2025-08-06T06:57:26.694584Z
1 likes, 0 repeats
@feld @lain @thatbrickster netusphäre used to be really slow because we ran off of shitty networked storage and i think that's common when using hetzner. Maybe the install.instructions should have a big fat disclaimer for that like goto social
(DIR) Post #Awsx2nSQMquKYcVgwa by lain@lain.com
2025-08-06T07:00:37.809178Z
2 likes, 1 repeats
@phnt @feld @thatbrickster good point, maybe we should remove the 2gb suggestions. 4gb is dirt cheap by now anyway.
(DIR) Post #AwsxbRGIsjW3r3MLGi by hj@shigusegubu.club
2025-08-06T07:06:49.067731Z
1 likes, 0 repeats
@lain @phnt @feld @thatbrickster might also discourage people to run pleroma on low-end raspberry pis
(DIR) Post #AwsxkOjDffPwbS9ltQ by phnt@fluffytail.org
2025-08-06T07:08:30.806414Z
1 likes, 1 repeats
@lain @feld @thatbrickster I would remove the 1GB example, put a note on the 2GB one that it is the minimum requirement for single-user instances only and may need additional optimizations in the future, and add a 1 core 4GB, or 2 core 4GB example.
(DIR) Post #AwsxzRwbzpVCvAb8ng by phnt@fluffytail.org
2025-08-06T07:11:14.214467Z
0 likes, 1 repeats
@hj @feld @lain @thatbrickster I think my Pi4 (2GB version) could probably handle it, but 3B is probably too far.
(DIR) Post #Awsy6qVB5fHt70IDGS by hj@shigusegubu.club
2025-08-06T07:12:29.587054Z
5 likes, 0 repeats
@phnt @feld @lain @thatbrickster biggest concern and should be mentioned to NOT to use database on Rpi at all cost. People be like "Pleroma is lightweight" and then proceed to install PostgreSQL on same shit hardware.
(DIR) Post #AwsyJuxBqkyygRd1No by phnt@fluffytail.org
2025-08-06T07:14:55.840391Z
1 likes, 1 repeats
@hj @feld @lain @thatbrickster The class 10 SD cards are probably more performant than the 200 IOPS slab meme Fran is selling. But it is a good point, that Postgres _will_ wreck the card in no time and random IO is meh depending on the card.
(DIR) Post #AwsyPHPLnEmDlvMCMy by nerthos@shitposter.world
2025-08-06T07:15:54.619538Z
1 likes, 1 repeats
@RedTechEngineer @arcana @lain @scathach While this is a valid argument, I liked getting random replies to all sorts of threads on the timeline, since it's not uncommon for the replies of a thread to become more interesting or a different topic than the OP
(DIR) Post #AwsyUgsKX80cCoUZY8 by hj@shigusegubu.club
2025-08-06T07:16:50.951505Z
1 likes, 0 repeats
@RedTechEngineer @phnt @feld @lain @thatbrickster not like you have much of a choice
(DIR) Post #AwsyVaSjrSoQbewvR2 by phnt@fluffytail.org
2025-08-06T07:17:02.708296Z
0 likes, 1 repeats
@RedTechEngineer @lain >(oh, and the database. it scares me.)Give an example. Bloat (table bloat)? Performance? Bloat (relay activities)? Bloat (size)?
(DIR) Post #Awszapr0AEMpkBMfYW by Ergo@shitposter.world
2025-08-06T07:29:11.504566Z
0 likes, 1 repeats
@lain @phnt @feld @thatbrickster just tell people to make a big swapfile and adjust swappiness
(DIR) Post #Awt05YcgHJpVHQJdDM by Cocoa@nekosat.work
2025-08-06T07:34:41.456623Z
7 likes, 0 repeats
@lain no "marry pleroma-tan" button in pleroma-fe, literally unusable
(DIR) Post #Awt0humULKdn0TC2eO by lanodan@queer.hacktivis.me
2025-08-06T07:41:34.426102Z
3 likes, 0 repeats
@Cocoa @lain live2d pleroma-tan (not in the frontend though, pleroma's not misskey)
(DIR) Post #Awt0kNKRAu727mFIfY by nicholas@aklp.club
2025-08-06T07:42:04.676837Z
1 likes, 0 repeats
Unlisted is good, public or only to OP would also be fine. Replying to a Follower only post, but only to a completely different set of Followers that very well may not even include the the person you're replying to is the only behavior that makes absolutely no sense, so naturally it's the default.
(DIR) Post #Awt0qea9wIpFNBaqgK by hj@shigusegubu.club
2025-08-06T07:43:13.683316Z
5 likes, 0 repeats
@lanodan @lain @Cocoa >not in the frontend though1de88814870e6e2fd0665199c312615…
(DIR) Post #Awt0t7Z39hqdq3Fch6 by hj@shigusegubu.club
2025-08-06T07:43:40.545988Z
0 likes, 0 repeats
@lanodan @Cocoa @lain i still want to do MS Comic Chat like frontend/library though
(DIR) Post #Awt10HywoyNgAwmZhg by lanodan@queer.hacktivis.me
2025-08-06T07:44:53.918425Z
0 likes, 0 repeats
@hj @lain @Cocoa Well could maybe be like ruffle but at least in a nicely separated thing that browser would unload similarly to multimedia stuff.
(DIR) Post #Awt15CrNICY5jmaKkC by hj@shigusegubu.club
2025-08-06T07:45:48.763553Z
0 likes, 0 repeats
@lanodan @lain @Cocoa yeah we can (and already do) code chunking, for instance settings modal is a separate chunk that only loads when needed
(DIR) Post #Awt1A5jjCjTB5oL0OO by lanodan@queer.hacktivis.me
2025-08-06T07:46:40.431856Z
0 likes, 0 repeats
@hj @lain @Cocoa does that ever unloads though?
(DIR) Post #Awt1DxI2YBvS3REHYW by hj@shigusegubu.club
2025-08-06T07:47:26.567988Z
1 likes, 0 repeats
@lanodan @lain @Cocoa no, i don't think so. JS has zero memory management. Even Java has better memory management.
(DIR) Post #Awt1LBFj2IGfNzal96 by lanodan@queer.hacktivis.me
2025-08-06T07:48:40.230115Z
0 likes, 0 repeats
@hj @lain @Cocoa my 2006 brain: iframe then I guess :]
(DIR) Post #Awt1OjSQJt94L5E0Tw by hj@shigusegubu.club
2025-08-06T07:49:20.623350Z
0 likes, 0 repeats
@lanodan @lain @Cocoa no gross hacks please. Only neat hacks allowed.
(DIR) Post #Awt1hUcDj513oFkkiW by lanodan@queer.hacktivis.me
2025-08-06T07:52:42.721308Z
0 likes, 0 repeats
@hj @lain @Cocoa Probably better than most hacks considered neat by current frontend people.It's just somewhat out of fashion to pull frames in instead of a megabyte of JS to do the same thing and fail to free up ressources.
(DIR) Post #Awt1ne09k3XueoskQC by hj@shigusegubu.club
2025-08-06T07:53:50.500458Z
0 likes, 0 repeats
@lanodan @lain @Cocoa most frontend hacks stem for piece of shit that is DOM, browser API, and shit browsers like Safari being opinionated and quirky
(DIR) Post #Awt2ISaiDPfyFIfuZk by hj@shigusegubu.club
2025-08-06T07:59:24.885085Z
0 likes, 0 repeats
@RedTechEngineer @lain @Cocoa @lanodan CSS is never readable and never will be readabledb159ebaa37b1d0ca757402f7223e84…
(DIR) Post #Awt2OWRqmu03whQ8xs by phnt@fluffytail.org
2025-08-06T08:00:35.334718Z
1 likes, 1 repeats
@skylar @RedTechEngineer @lain That's the same game for every fedi server. Mastodon deals with by running the pruning in the background automatically when configured and GTS is the same as Mastodon. And I think that a 30GB DB after 2.5 years isn't that bad.
(DIR) Post #Awt2sGrTIsAQI9adua by hj@shigusegubu.club
2025-08-06T08:05:52.929648Z
0 likes, 0 repeats
@RedTechEngineer @lain @Cocoa @lanodan creadable (in same way aas cute and funny)
(DIR) Post #Awt2tSz9iEHcBPkpA8 by hj@shigusegubu.club
2025-08-06T08:06:09.017352Z
0 likes, 0 repeats
@lanodan @RedTechEngineer @lain @Cocoa sass
(DIR) Post #Awt37M607mLkryZwrw by hj@shigusegubu.club
2025-08-06T08:08:38.046488Z
1 likes, 0 repeats
@lanodan @RedTechEngineer @lain @Cocoa and the beast that i made ISS
(DIR) Post #Awt8sc4n1iWVoUMkAi by thatbrickster@shitposter.world
2025-08-06T09:13:15.913787Z
1 likes, 1 repeats
@feld My comments were more to do with the front-end as I have more experience using it. I have also run local instances of it. The longer it runs, the jankier it gets in a browser.The only things I could say about the back-end is database bloat and the self-resolving(?) errors I see every now and then, whether it's network related or '<!DOCTYPE isn't valid HTML' or 'invalid token/char' or something else.@lain
(DIR) Post #Awt8ybgtNARYM62uZM by feld@friedcheese.us
2025-08-06T04:54:30.904130Z
0 likes, 0 repeats
@i @lain @dwaltiz @jra did you merge my fixed Postgres search in your branch ??? No rum
(DIR) Post #Awt9LOMt4X1NhEYO3s by graf@poa.st
2025-08-06T09:18:25.589971Z
1 likes, 0 repeats
@i @phnt @lain my complaint is I feel like for a while, or maybe the entire time lain discounts what I say because of poast. Feld ran a secondary instance that federated with poast but decided to defederate us on that instance too. the discussion i had with him was productive but i feel like nobody upstream wants to deal with us.in any event: we are in the middle of a security audit for current dev branch (62993871). periodically poast pays or has third parties audit the code we're using since the 0day in may 2023 and there is one we will submit issues or fixes for if they arise in the next couple weeks
(DIR) Post #AwtHJDzpSlFyaBFIxs by kakafarm@shitposter.world
2025-08-06T10:47:42.790191Z
1 likes, 1 repeats
@lain 0. 💚 :lainBear: 💚, so please don't take anything personally.Not being able to separately load the different kinds of notifications. If I mark many accounts for notifications, in order to load all posts directed at me and/or likes I got and/or other sorts of reactions or whatever from other people, I have to load many general posts from accounts I had subscribed to, which takes a bunch of time.Another thing is not being able to subscribe to specific tags. I love reading the #books stuff, for example, which I did on the https://emacs.ch/† Mastodon instance. I could just look that up in the search, but that is different from subscribing to tags on Mastodon in some important way, but I don't remember how.Another another thing is the limitedness of the search. Being able to search within specific people's timelines, specifying time ranges, specific type of posts, existence and maybe kinds of attachments, stuff like that, would be very useful.Thank you.
(DIR) Post #AwtV0yreNoDfnVcCEC by dagda@netzsphaere.xyz
2025-08-06T13:21:17.021773Z
2 likes, 0 repeats
@lain the posts from other users
(DIR) Post #AwtbTjiuM5sYxfcYjI by patchuun@social.xenofem.me
2025-08-06T14:20:15.199706Z
1 likes, 0 repeats
@lain oh also being able to pin followers-only posts would be nice
(DIR) Post #Awtmf1uUB1Ts31ckS0 by feld@friedcheese.us
2025-08-06T16:25:35.609348Z
2 likes, 0 repeats
@hj @lain @lebronjames75 @yew hey, turns out we already have 99% of this in place already! I'm looking at it right now, but the problem is that there's clearly a bug somewhere with the ranking...
(DIR) Post #AwtymTY314UlF7Rgn2 by feld@friedcheese.us
2025-08-06T18:44:18.420608Z
1 likes, 0 repeats
@phnt @lain > The whole 2.7.0 Oban blowing up and follows refusing to work 90% of the time debacle could have been prevented by it, if enough instances admins actually knew when to test stuff.I'm going to push back on this again, for like the millionth time.Follow bug -- this existed in the code for YEARS. It was not a single release that caused it.Oban bug -- very few people experienced this. Nobody on the team was able to reproduce it. People who had the issue were refusing to give us root to go and look deeper at what was happening. Turns out, it wasn't even an Oban bug in the first place! While hunting for the issue we did find another problem in Oban, but all along it was a Postgrex bug which exposed another Oban bug. We didn't even upgrade or change Postgrex. It was just lurking there, waiting for someone to hit the edge case.That edge case: server was too overloaded, too poorly configured, etc causing the Postgres connection to fail and Postgrex was not reconnecting. So the connection Oban was using for NOTIFY would just stop working.Personally I'd rather see us have a "release early, release often" approach than some kind of long QA process, because QA releases would not have helped here.
(DIR) Post #AwtymUxFmqFfbaFKiW by mint@ryona.agency
2025-08-06T18:54:45.653596Z
0 likes, 1 repeats
@feld @phnt @lain Well now there's also a force lockpost bug in latest release. It's been fixed since (https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4353) but never followed with a bugfix release.
(DIR) Post #AwtzVq3UBMU44vmVCC by pernia@cum.estate
2025-08-06T19:02:59.514266Z
0 likes, 0 repeats
@lain right now, this prune has taken 9 days on a 66GB db
(DIR) Post #Awu0LKekAUuvkplKQi by feld@friedcheese.us
2025-08-06T18:36:52.637449Z
0 likes, 0 repeats
@i @lain > the backend is a mess no one wants to toucha mess *how*? The code is all very neatly organized... we don't have crazy modules doing a million unrelated things.
(DIR) Post #Awu0Y64zfuugJJ7xfE by sysrq@lab.nyanide.com
2025-08-06T19:14:37.343089Z
0 likes, 1 repeats
@lain No Ed25519 HTTP sigs, yeah this is an Erlang bug but idk go fuck yourself
(DIR) Post #Awu1FnHOvxTikGlcbg by i@declin.eu
2025-08-06T19:22:29.836293Z
0 likes, 0 repeats
@sysrq @lain could backport it with https://hexdocs.pm/ed25519/Ed25519.html though
(DIR) Post #Awu1lF1XpbRzlmLUcS by phnt@fluffytail.org
2025-08-06T19:28:10.916267Z
1 likes, 1 repeats
@feld @lain >Personally I'd rather see us have a "release early, release often" approach than some kind of long QA process, because QA releases would not have helped here.While I do agree that faster releases would definitely be better than the current pace, but you also have to take into account that there are still instances running 2.5.X and 2.6.X managed by people that are hesitant to upgrade because of previous bugs. There aren't many of those people, but the overall feeling is still "I'll wait for a few months and let others test it for me before I upgrade."I'm not saying do an RC and wait a month or two for it to cook probably with barely any activity in the tracker. Pleroma isn't Mastodon. I'm talking about doing an RC, waiting a week or two to see if something bad happens and then sending it to stable. And since an RC would be a release, people wanting to test can subscribe to new release notifications on GitLab and get them in their inboxes. And if some issue arises after it was formally released as stable, don't wait months to ship a release with 20 other changes. Release a hotfix release with the fixes and those fixes only after some very quick testing and be done with it.Currently as it stands from my point of view, Pleroma suffers from long release gaps while QA isn't good enough to justify the wait. And in my opinion it should try to improve on both fronts. QA done by ~5 maintainers communicating in some probably private channel who know the codebase well and how to properly configure everything can't bump into the same bugs as regular users.>Follow bug -- this existed in the code for YEARS. It was not a single release that caused it.It did exist, yes, I remember it happening way before 2.7.0. But somehow something made it much more prevalent (my best guess is the activity handling rework). 2.6.3 wasn't riddled with follows basically never working unless you try 6 times. 2.7.0 was and it took months for the fix to be released in a new version and the version that looked like it solved the problem (2.7.1) actually didn't solve it. It fixed the inconsistency between accounts appearing as followed but not getting posts in your timelines/delivered to you, because the state was inconsistent when something crashed. The actual proper fix to the follow bug I'm describing arrived in 2.8.0.To give you a reference, I helped at least 3 people apply the patches on top of stable to fix the bugs.>Oban bug -- very few people experienced this...I'm aware of that. I tried experiencing it on the cheapest OVH VM with stock Postgres config on the most esoteric OS I could think of (OpenBSD). I did see it crash due to the load, but only 3 months later when the issue was resolved. I'm also aware of at least two instances (lab.nyanide.com and clubcyberia.co) reverting back to 2.6.3 because of the follow bug and/or fear of Oban randomly falling apart.>That edge case: server was too overloaded, too poorly configured, etc causing the Postgres connection to fail and Postgrex was not reconnecting. So the connection Oban was using for NOTIFY would just stop working.This is way more likely than you think especially when the default query timeouts (15s is the default I think) are to fast for cheap VMs. I see 5-10 random timeouts every day. Mostly when autovacuum gets triggered on one of the large tables. It's not that unusual and I've set the query timeout to 30s, which is around the maximum time (20-25s) queries can take when loading FE (notifs, home timeline and maybe a thread load at the same time). Yes it's high, but the other solution is query->timeout->do same query again->probably timeout->query again->get actual data.And @mint consistently triggered the Oban bugs on an older desktop with an nvme drive hosting 3 instances. A bit too much, but something an nvme can handle. The 2.7.0 release also inexplicably to me came with higher disk usage from Postgres for whatever reason.
(DIR) Post #Awu2UCZbmzgXCUiY9A by mint@ryona.agency
2025-08-06T19:36:17.582853Z
1 likes, 1 repeats
@phnt @feld @lain Two NVMes in RAID0, in fact, with nothing else except postgres writing to them (I don't remember it it was before or after I switched to them from a singular SATA SSD). Third instance is an I2P one that gets barely any traffic do it could be discarded from the stats. And all of them chugged just fine until they didn't. Still, that bug is fixed and I've managed to procure a guinea pig instance for catching it, so not much point in pouring salt on this exact wound.
(DIR) Post #Awu2mCjnuswqvI4Ryi by mint@ryona.agency
2025-08-06T19:39:33.909743Z
1 likes, 1 repeats
@phnt @feld @lain Yeah, turns out that was two months before getting new disks.
(DIR) Post #Awu3RCVVg7vU54vvcG by sysrq@lab.nyanide.com
2025-08-06T19:46:59.351337Z
0 likes, 1 repeats
@i @lain I'm referring to this https://github.com/erlang/otp/issues/9009, it's fixed but no one seems to run the correct version.
(DIR) Post #Awu4JdhwlOEy4zi14K by phnt@fluffytail.org
2025-08-06T19:56:47.185901Z
1 likes, 1 repeats
@mint @feld @lain >so not much point in pouring salt on this exact wound.I didn't want to pour salt on an old wound. I wanted to give an example of something that was preventable if enough people were willing to test and knew when.
(DIR) Post #Awu4uQSD0Hyvgit9ii by phnt@fluffytail.org
2025-08-06T20:03:28.043461Z
0 likes, 1 repeats
@feld Also when you are here, could you check up on Weblate. I think the API key it uses to create GitLab MRs experied.Failed to create pull request: invalid_token: Token is expired. You can either do re-authorization or token refresh. (-1)@lain @mint
(DIR) Post #Awv14xrRRlLNXFQ9ho by mkljczk@pl.fediverse.pl
2025-08-07T06:55:08.113028Z
1 likes, 0 repeats
@lain Some half-baked features that aren’t usually exposed by frontends like the ability to post to a list of users (which has been broken for like 2 years)
(DIR) Post #Awv57Zzr1uTsCsrH28 by mkljczk@pl.fediverse.pl
2025-08-07T07:40:29.453167Z
0 likes, 0 repeats
@mold @lain since 2019. besides pl-fe, i only recall it being used by some @deadsuperhero's experiment to create a diaspora-like frontend
(DIR) Post #AwvDM8UqM9WQtSnz0q by mkljczk@pl.fediverse.pl
2025-08-07T09:12:47.099053Z
1 likes, 0 repeats
@ewen @lain soapbox is not work in progress, it’s dead as a fedi client
(DIR) Post #AwvE16Wma4ISf1FOfw by a1ba@suya.place
2025-08-07T09:20:11.270665Z
1 likes, 0 repeats
@feld @lain @thatbrickster back on expired.mentality.rip I had RUM indices enabled, which ended up taking too much disk space. Also after some upgrade (my fault running Pleroma off develop) it became really slow despite the server has 32 gb of RAM and ryzen 3600x.I didn't had such issues running my suya.place and pleromashit.nexus off of stable branches of Akkoma and Pleroma. Not sure what exactly happened back then, there are so many variables, I'm just saying there is a possibility that some people might've encountered similar bug that ended up making Pleroma less responsive.Search is still broken though.
(DIR) Post #AwvEacMIE6IPW9H72W by a1ba@suya.place
2025-08-07T09:26:35.137093Z
0 likes, 0 repeats
@feld @lain @thatbrickster >some upgrade somewhere around introducing this: https://git.pleroma.social/pleroma/pleroma/-/blob/develop/priv/repo/migrations/20220711192750_switch_to_associated_object_id_index.exs?ref_type=headsNot saying this exact change caused it, I just remember it was around mid-2022. Who can tell now, oh well.
(DIR) Post #AwvF59vVzAG2JZJTFo by hj@shigusegubu.club
2025-08-07T09:32:04.861219Z
1 likes, 0 repeats
@vriska @lainimage.png
(DIR) Post #AwvGNXJvqXbI2I3pcu by thatbrickster@shitposter.world
2025-08-07T09:46:42.614717Z
0 likes, 1 repeats
@a1ba Database bloat and search issues were two things I had considered in the past, but wasn't sure whether any improvements were made in those areas. I think a few instances came and went over the years due to database bloat. I'm no expert though.Speaking of discoverability issues, whenever I'm scrolling my own profile's feed, sometimes the pagination will start from the pinned post date rather than continue the chronological order of them, missing a whole chunk of posts. Reproducibility, however, has been a pain. Most of the time it works fine but it's hard to know when it will break.@feld @lain
(DIR) Post #AwvH98Ovnc22eM5zcW by hj@shigusegubu.club
2025-08-07T09:55:12.478585Z
0 likes, 0 repeats
@ewen @lain >PleromaFE is very busy and not very tunable. Wish it could be tweaked to operate more like the advanced mode of Mastodon.can you give more details on that? PleromaFE is very tunabe and we can make it even more tunable.
(DIR) Post #AwvOaPPTMuUStpIkV6 by threalist@social.fbxl.net
2025-08-07T11:18:36.007182Z
0 likes, 0 repeats
1. Ability to purge the database based on date parameters (e.g. only keep two weeks of local/fedi timeline)This is huge, because the alternative is infinite scaling of storage.2. A "random" button.Scrolling the timeline is great and all, but content is highly dependent on when it was posted, and good stuff gets lost to the void
(DIR) Post #AwvRn4GTb2q8wioz0S by ewen@social.ewenbell.com
2025-08-07T10:12:13.791015Z
0 likes, 0 repeats
Yeah I didn't want to throw out too many specifics to my reply. Happy to elaborate more.The UI is very busy and makes me anxious having that much jammed into a screen. It's trying to do a lot all at once. I'd like to be able to just rearrange what is on screen, or scale back sections to an icon instead for example. The main section with the feed in PleromaFE is especially intense. Tight fonts and lots of icons. Clicking on a post expands that thread, but I'd much prefer to have a break-out section where highlighted or expended content can be viewed instead. A second column for example, like the advanced web UI on Mastodon. Indeed that UI is a very effective and useful way to setup a screen, in my opinion.Overall, the PleromaFE UI feels very dated. 90s dated. At the other end of the spectrum is Soapbox – very clean, and somewhat lacking in features. But it's a calm space and the UI is nicely responsive. It's very smooth. Maybe some inspiration to be found there.Those are my thoughts!
(DIR) Post #AwvRn5V30M5cmCe8MC by hj@shigusegubu.club
2025-08-07T11:54:18.706808Z
0 likes, 0 repeats
@ewen @lain thanks. I'll try to address some of the concerns:>The UI is very busy and makes me anxious having that much jammed into a screen. It's trying to do a lot all at once. I'd like to be able to just rearrange what is on screen, or scale back sections to an icon instead for example. As of current Develop branch, you can:1) Collapse navigation section into a bar and adjust what icons are there (pic 1). Do you want to be able to collapse notifications column, too?2) You can reverse the order of columns and adjust the size of them (pic 2)>Tight fonts and lots of icons.1) being able to adjust margins to be more relaxed is on my to-do list, right now you can only scale the UI in general.2) you can adjust which icons show up on posts (pic 3)>Overall, the PleromaFE UI feels very dated. 90s dated.Apart from tight margins, I wonder if it's a theme problem. PleromaFE has an outstanding theme support (pic4), perhaps Mammal (Mastodon-inspired theme) looks better? I do want to make a material-like theme.if you have any more ideas, i'm willing to listen and implement themimage.pngimage.pngimage.pngimage.png
(DIR) Post #AwvX45G9eOdIj1bVse by ewen@social.ewenbell.com
2025-08-07T12:35:07.788186Z
0 likes, 0 repeats
Thanks so much for taking time to look at this.[ I've just spent the evening trying to switch back to Pleroma-FE and spend more time with it. I grabbed an updated Soapbox a week ago and it's blatted my static folder... so I'm trying work out how to get back to Pleroma-FE. It's ignoring my admin settings! ]Anyway, I will figure it out. Then I'll look more closely again at your suggestions.One more thing that was a big issue for me, which I forgot about, was having a larger box to write my posts in. One reason I started exploring self-hosting an instance was to give myself freedom for very long posts. Is there flexibility on the Pleroma-FE interface to create a nice big space for typing long posts?Am attaching a screenshot of this post by way of example.I should add, I'm a 55 year old ex-geek with bad eyesight. My feedback is probably not going to reflect what a lot of younger audiences are thinking. I might be boring :)
(DIR) Post #AwvX46XCuTrqgCae6C by hj@shigusegubu.club
2025-08-07T12:53:29.238815Z
2 likes, 1 repeats
@ewen @lain >Is there flexibility on the Pleroma-FE interface to create a nice big space for typing long posts?PleromaFE automatically scales input form with length of your post (pic1), not sure if you want fixed adjustable height or minimum height or something else?You can also adjust column width. (pic 2 and 3)>I should add, I'm a 55 year old ex-geek with bad eyesight. My feedback is probably not going to reflect what a lot of younger audiences are thinking. I might be boring :)No, it's ok, I try to please _everyone_ even if it's futile.image.pngimage.pngimage.png
(DIR) Post #AwvXZAKMrFzbQ7OaTw by j@annihilation.social
2025-08-07T12:59:16.918772Z
1 likes, 1 repeats
@hj @lain @ewen you do good :Salute:
(DIR) Post #AwvZxM1xCKc0ZhRcOW by ewen@social.ewenbell.com
2025-08-07T13:14:25.620831Z
1 likes, 0 repeats
@hj @lain Okeys I got my instance back under control and have PleromaFE back online.- I had no idea that the boxes expanded on the fly as the post is typed. That is good to know. I can see that works well. - One of the big pluses with PleromaFE is that you can more quickly move through a timeline compared to Soapbox. When my brain is moving fast, this is a bonus. And I can see that being able to respond to a post without leaving the timeline can be helpful to keep your train of thought.- It's a fine line between quick access to things, versus crowding the screen.- I'm a very visual person and so little things like chunky icons or mis-aligned icons tends to distract me. Even the shading on buttons can impart a design signal.I'll spend the next few days just with PleromaFE and see if my brain finds any specific friction.
(DIR) Post #AwvZxSq9saKth8ynTs by hj@shigusegubu.club
2025-08-07T13:25:58.731756Z
0 likes, 0 repeats
@ewen @lain thanks!
(DIR) Post #Awvs7DqUHZktGCw6kK by feld@friedcheese.us
2025-08-07T16:41:33.783624Z
1 likes, 0 repeats
@thatbrickster @lain @a1ba > sometimes the pagination will start from the pinned post date rather than continue the chronological order of themThere is a bug lurking in PleromaFE that does this. It has not been isolated yet. Sometimes it also happens if someone boosts a really old post. So far we think it's when the post with the old date is the last item in a page (last of 20 items), so then when it paginates to load the next 20 it starts from the wrong post/date
(DIR) Post #Awvt3ghHAhIZXNVRAG by thatbrickster@shitposter.world
2025-08-07T17:00:07.419541Z
0 likes, 1 repeats
@feld I'm honestly relieved to hear that. It has been bugging me for years!@lain @a1ba
(DIR) Post #AwvvZaRCB9ntIcK54q by feld@friedcheese.us
2025-08-07T17:27:40.503741Z
1 likes, 0 repeats
@thatbrickster @lain @a1ba if you feel like hunting through the FE pagination code to figure out how exactly it gets triggered that would be cool, lol
(DIR) Post #AwvvZbg7Z9Kx9CJVyq by thatbrickster@shitposter.world
2025-08-07T17:28:17.154231Z
0 likes, 1 repeats
@feld I tried. It's too convoluted, as I posted earlier.@lain @a1ba
(DIR) Post #AxeKo1wDmCk8SC3VtA by patchuun@social.xenofem.me
2025-08-29T01:03:03.585212Z
1 likes, 0 repeats
@lain super late but also I do think it'd be nice to be able to send stuff to the drafts instead of out right posting it,but usually I just go "fuck it" and post it anyway