differences in akkoma compared to pleroma: - older fe (but it can be rather slow and even unstable at times) - hashtag following - bubble timeline (echo chamber) - no Pleroma chats or shoutbox (kind of fair actually) - broken features that the developer has broken on purpose (regular pleroma blockbots do NOT work on akkoma afaik)
There's just so little difference and the changes that are there are either beneficial in an extremely minor sense or just bad
@kirby I do follow hashtags and I use the bubble timeline to check for new accounts (the known timeline is a clusterfuck cause old and popular-ish instance). Couldn't care less for the chat and shoutbox features, but I guess those can be also disabled in Pleroma?
I guess the biggest reason people still run Akkoma is that migrating to Pleroma wouldn't bring big enough advantages to be worth it. Migrating from Pleroma to Akkoma is the same: why go through the trouble?
I can't say anything about the devs involved in either project. Isn't there still cooperation between the forks? The code doesn't differ that much AFAIK.
@susie really in the most dire situations is there cooperation it seems, like security vulns and stuff. Akkoma and pleroma teams communicated with each other about the webfinger impersonation vulnerability
Honestly I disagree with you on your opinion on the twkn timeline but that's a matter of opinion. Probably shouldn't have said the echo chamber comment
Hashtag following is a very minor thing though. Mostly convenience, Could live without it. But kind of sucks that pleroma doesn't have it I'll admit. Only ever had a need to use it once though 🤷
@kirby I'm still pretty new to the fediverse and social media in general (this is my first social media account if you can believe that). So finding people to follow was a chore at first. Hashtags helped a lot on that, because like I mentioned this instance is pretty big so there are plenty of hashtagged posts get federated to my timeline.
I don't know if I am in the minority here, but I like my art and photography spam. So by following some popular hashtags I get a lot of those without following even one account (I do then follow those I like that appear on my timeline). There however isn't that many "text-only" hashtags in use. Like I can't just follow a <common sport event> etc.
Groups do alleviate the need for hashtags, if people actually used them! So I can see not needing hashtags if those would finally get popular.
@maija@susie@kirby@coolboymew i don't think they were "promised" at any point, but always considered. At least in develop there's "group actor" support which just lets you create an account that repeats whatever you throw at it.
@kirby it's also about 1000 commits behind us, like I spent all of January crawling through the codebase with Dialyzer (static code analysis) and fixing things. It's tedious as hell because most of it doesn't REALLY matter in the long run, but it gives you another tool to rely on to double check the current quality of the codebase
@kirby@susie we do not hesitate to notify Rebased and Akkoma if there are security things we encounter and we hope they'll do the same for us
Like, I'm not mad about what they've done with their forks it's just annoying we couldn't all collaborate on the same codebase. Half of it is related to a culture war that the Fedi kicked off, though. Lots of ridiculous people slinging ridiculous libel around and of course the hivemind on Fedi gobbled it right up nom nom nom without doing 5 seconds of research
@kirby strongly doubting that tbh, benchmarks are a useful tool but do not reflect reality.
e.g., they just backported my work to refactor Rich Media (link previews) because every page of posts you requested would hang while it tried to find the link previews for each post with a URL in it. If CNN.com was running slow, the timeline would hang until that HTTP request timed out.
This is something that cannot be measured by that benchmark. I do not trust it.
@coolboymew@kirby Sort of! By tagging the group account to the post the group account boosts/repeats the post in question. So everyone who follows the group account gets it to their timeline even if the post isn't federated to your instance/you don't follow the account. And you can also get a timeline of sorts by going to that group account's profile and browsing the post history there.
It is a bit clunky like old posts won't appear if you just started following the group account (if users in the instance hadn't followed it before) and it works with repeats so get "double posts" if already follow the account who wrote it in the first place. Still kinda neat though!
@hj@susie@kirby@coolboymew idk specific implementations off the top of my head friendica is an obvious one but i dont recall if groups are with activitypub
@maija@susie@kirby@coolboymew friendica is also quite... weird. It feels like they exist in their own bubble and not acknowledge anyone else's existence. Friendica posts always look weird on the outside.
people seem to get really upset when i point out that the akkoma developer removes/breaks functionality on purpose just to make a political statement or something
@olivia@kirby i will never not be proud of my accomplishment on that front
and again i would like to say that floating ghost is retarded and that is not even remotely needed for mfm and this was the worst possible approach in the first place you should just be using classes and if your this bad at webdev maybe you shouldnt run a fucking project like this dumbass
@hj@susie@kirby@mkljczk@coolboymew > Smithereen supports various features not found in most other ActivityPub server software. See the federation document if you would like to implement these ActivityPub extensions in your project. they do seem more than open to helping
@jihadjimmy@kirby i was always suspicious of akkoma from the start honestly, i just felt one person managing an entire fedi software like pleroma is untrustworthy
@meso@PurpCat@kirby@jihadjimmy yeah i don't even really blame kainoa for it dying so much as that trottier guy who had apparently schmoozer-hijacked the project and caused the rebranding
@apophis@PurpCat@kirby@jihadjimmy yeah it was so random the dude was just like Im gonna change the name of it cuz i dont wanna take the credit all of a sudden, i didnt really know insights into the drama but like yeah it was very obvious some power hungry hijacker was pulling some strings
> autistic guy makes good thing > smooth-talking rich white male schmoozer presents growth opportunity partnership > smooth-talking schmoozer starts getting handed control of vital stuff > schmoozing parasite's total lack of any deep understanding of what made the good thing good becomes more and more unavoidable as the drama starts piling up > schmoozer parasite manipulates everyone into dumping all the blame on the autistic guy who made the good thing in the first place > bad ending: good thing dies and is gone forever, autistic guy burns out and disappears > good ending: good thing still lives on in name and in law, but every single good thing about it has now been turned irredeemably bad; autistic guy languishes in the outer darkness doing a very tiny version of the good thing but with a lot of lessons learned > bad ending part 2: schmoozer-hijacked zombie former good thing uses its pre-existing clout to snuff out even that
@apophis@PurpCat@kirby@jihadjimmy yes. this happens in a lot of places where manipulative people like that aren't weeded out quick. GrapheneOS is one example. Micay isn't at fault for anything he's just really paranoid, but a bunch of good-for-nothing mentally ill social parasites try to abuse that and cause normal people to not really want to use a project that volatile
@apophis@PurpCat@kirby@jihadjimmy i think they ruin perfectly good projects with their manipulative and hostile to everyone behavior. it's a shame naive people like Micay let them rise into their circles
@meso@PurpCat@kirby@jihadjimmy tbh the mental illness and resulting volatility probably mitigates a lot of the damage... it's the mentally stable neurotypical (but apparently sociopathic) parasites that do the real long-term harm
@apophis@PurpCat@jihadjimmy@kirby at least neurotypical faggots just turn the project into a soulless shell until it eventually dies due to losing everything that made it special, the other kind of manipulative parasite just turns it into a mess
@susie@kirby@coolboymew >By tagging the group account to the post the group account boosts/repeats the post in question And they laughed at me a few years ago when I said that "Freedom patriot" bot was basically all the backend logic you need for AP groups
@kirby regular akkoma user (not hoster, not admin, my admin should know better than me anyway) 1) it sucks sometimes, for example the emoji picker is slow at inserting selected emoji in input field 2) never used hashtag following, I don't even use them nor search because search is non-indexed garbage right now 3) never used those, not sure why even needed in SOCIAL MEDIA 4) no shoutbox is sad, I remember using such on one forum, it was fun 5) not sure which ones are broken tbh but I heard Akkoma cut some features because they are part of infamous "Pleroma crimes" meme or something. I don't agree with the "software/feature crimes" policy because we all know it depends on a person and their intentions, just like how we use technology in everyday life now.
The only specific useful thing I see here (at the time of writing) is option to enable separated post/replies tab in profiles and user profile preview in feed. Emoji reactions are already in Pleroma so if some other QoL stuff get merged too it will be more preferable to use Pleroma as a more maintained software.
@olivia@kirby btw if your instance isn't Akkoma and you're an admin I highly recommend supporting federation over Tor and i2p. It makes the experience better for people on hidden service instances and makes it more feasible to set up an instance without having to buy a domain
@kirby though I won't stop use Akkoma unless the instance I'm on dies or get migrated to Pleroma (impossible). Akkoma is not awful, it's just not perfect now.
@nukie I was thinking of a way to maybe solve the problem earlier actually. One way I thought of was just having a claiming web page where you use the same password hashing algorithm to verify an accounts owner and if it's them redirect them to a password reset form. This would probably not take too long to spin up actually you'd just need to know what hashing algo akkoma uses
@kirby those fags also broke upgrade path to pleroma for multi-user instances since you have to reset passwords for everyone. some of my oomfies never returned :menherasad:
@nukie The problem is that doing that in vanilla pleroma will basically just be maintaining your own fork because you're going to have to deal with merge conflicts eventually