49
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Aug 2024
49 points (100.0% liked)
Fediverse
28550 readers
877 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
It was never unusable beyond the stability issues large instances (from 1k to howevermany people ff.social had) had. For smaller instances it worked fine and continues to do so. The issues with large servers were the result of it being based on an ancient codebase (Misskey v12) with extremely questionable changes thrown on top (muting enough words could cause the entire instance to slow down), and the issues with ff.social were specifically caused by throwing everything at the wall to try to duct-tape that ancient codebase to function (ScyllaDB was the nail in the coffin i believe...?)
Firefish itself is still going (see firefish.dev), there are forks like Iceshrimp which reigned in the issues enough for larger servers to not fall over every few seconds (iirc both the infosec.exchange hosted Firefish instances migrated over which caused the main issues to be found and fixed). I wouldn't be surprised if "Modern" Firefish took the most important changes over from Iceshrimp (the devs are friendly, and the Mastodon API implementation and some security fixes were shared between both)
If you want something a bit lighter, Misskey itself is still ongoing, and there are forks like Sharkey that do some of the modifications Firefish and similar forks did to tailor it towards a non-Japanese audience.
(And Iceshrimp.NET is a project worth keeping an eye on, which aims to get rid of the technical debt of the Misskey codebase by completely rewriting it, but is not ready for much more than a single user instance just yet considering it's been a thing for just about a year)
I'll keep an eye on Iceshrimp. I always wanted to like Mastodon, but the chronological feed never did it for me - I think I've been spoiled by algorithms. Antennas in Firefish seemed like a decent compromise.
I also wish there was an app that let me browse/post/comment on Lemmy using a Firefish/Iceshrimp account so I could theoretically consolidate accounts.
that'll be difficult. Lemmy killed interoperability when they first decided that users and groups could share the same username, and now itd be a breaking change in order to solve this on Lemmy's end.
each software willing to federate with Lemmy correctly needs to be modified to handle multiple "users" having the exact same username, and i suspect most have more important priorities to tackle before getting to that
(misskey 12 derived software also has their own interoperability bugs regarding Lemmy, but those are usually not as big of a refactor as the username thing)
Wait, what? Can a Lemmy instance have a /c/foo and /u/foo at the same time?
I haven't been keeping up on backend development so I didn't realise Lemmy made that change. That's a shame. Thanks for being so helpful though!
oh no that's not a new change afaik it was always like this
I'm fairly sure I was able to comment on Lemmy threads while experimenting with Firefish like a year ago - though it of course struggled with displaying threaded content.
that post will have been a text post, not a link (those are likely broken now, and certainly were broken a year ago due to a bug in the misskey 12 codebase inherited by firefish and forks. modern versions of misskey just fixed that a couple months ago)
the username thing does not completely break federation, but it will randomly confuse instances. there's a 50/50 chance whether an instance will get the correct user it asks or not, and once an instance resolves a user once it'll have a similar 50/50 chance for each profile update (icon change, sidebar change, etc.). of course, if there's no conflicting user for a community (or vice versa) then federation will be fine.
Ah, I see! Thanks for the explanation. I'd go back and check but firefish.social isn't around anymore.
It's really a shame since interoperability is such (theoretical) benefit of ActivityPub, but what can you do.
the specs are so open ended that i doubt real interoperability will ever happen. you can break interoperability with basically every other current software out there and still be compliant with the specs