The Pleroma family of ActivityPub servers are on Elixir and their bottleneck seems to be their awful database schema where everything is JSONB, and even then they’re known to be quite lightweight, so I assume with a proper DB schema it’d work quite well…

small correction: the post that displays the instance you’re on (https://void.rehab/notes/9umvfd1lgoulvm0j) won’t work with “'regular” iceshrimp. it depends on an extra patch added to the version on void.rehab to function.

this is what happens when lemmy tries to handle microblog content not specifically tailored to it’s exact quirks

After seeing a team of fedi software developers drop their Matrix bridge to their Discord after the total lack of moderation tooling resulted in an extremely transphobic spam wave, I for one am not surprised.

Another team I’m aware of also dropped Matrix for other reasons, but went for Zulip instead, which is also open, but more collaboration oriented a la Slack rather than community oriented like Discord, which probably would not fit what the group in the OP is looking for.

people in real: hey how’s it going

Lemmy’s cross posts are separate posts that just happen to link to the same thing. so only replies to the original post would be sent with the current design.

that said, i severely doubt Lemmy will gain anything from this. publishers will not be sending out their posts to any communities, and i highly doubt they will expose any fep-1b12 group actors you can subscribe as a community.

kbin/mbin with it’s ability to follow users may work better, assuming people test their federation with software other than mastodon, and accept any of the interoperability bugs as actual bugs instead of ignoring them. (lemmy itself is no stranger to this: the fact that users and communities can share the same username break quite a bit)

i dont think i have the ai on my google yet + the pic works better if its obviously faked

while i don’t have any specific opinions about this that other people haven’t addressed, i just want to flag up something;

How this could be enforced? No voting from the All and/or Local feed. Seems easy and straight forward.

this seems unenforcable. as in, you can’t really tell where someone discovered a post from. yeah you can just remove the buttons from those views clientside and it’ll probably work for the majority of cases, but alternate clients or modifications to lemmy-ui can simply put the buttons back in (or in cases of unmaintained or differently opinionated clients, just not remove the buttons at all). the backend can’t really differentiate which view a vote comes from. federation especially can’t differentiate which view a vote comes from.

https://git.arielaw.ar/arisunz/ir34/

wdw and it’s circle is hands down the best fedi has to offer. miss me with that mastodon.social shit

at least you can use mastodon in the meantime

I would absolutely boost this to the microblog-verse if Lemmy federation with Misskey wasn’t broken

this is how it starts. first you open one for your cat as a joke and next thing you know you’re going meow meow :3 nyaaa~~ at people online and suddenly social media starts makign sense

and nyaizes your text so all your "na"s end up "nya"s. western forks like firefish/iceshrimp/sharkey have that separate from the cat ears toggle but honestly why would you disable that?

misskey cat mode my beloved <3

I mean, there’s only so much you can do when your upstream is developed exclusively in Japanese (to the point the code comments are also in Japanese) with a focus on adding Reversi and a Suika Game clone into the software instead of refactoring so the same piece of code isn’t duplicated in 10 different files split across the frontend and the backend and refuses to implement editing because they find it too hard when both major fork families (Firefish/Iceshrimp and Sharkey) have it and it works fine enough (alt text edits don’t federate, but that’s comparatively rare)

I’m also very curious to see how (if at all) you migrate an existing server with all its existing ActivityPub keys and subscriptions to a new piece of software, on the same domain, without unfixably breaking its federation with every other instance. My guess is that they will switch to a different beehaw.(whatever) domain but I’m curious if there’s a good solution I’m not aware of.

If the software you’re migrating to is built to allow that to happen, it’s absolutely possible. In the microblogging side of the fedi migrating between software isn’t uncommon, though in nearly all cases they’re forks from the same “family tree” so things work out mostly due to that, (Misskey is infamous for having a LOT of forks with most being capable of migrating to most, Mastodon can migrate to/from it’s forks Glitch-soc/Chuckya/Hometown, and Pleroma and Akkoma can migrate between each other…).

There are software being built from-scratch to be migratable from other software (aside from Sublinks, Iceshrimp.NET comes to mind as a total rewrite of Iceshrimp, which started out as a fork of Firefish and therefore is in the Misskey family tree, but found the existing codebase to be un-salvagable) but it’s definitely a rare case.

Surely that would be possible with Authorised Fetch, yet nobody mentions the possibility.

Not really (in practice, anyway). Authorized fetch without cooperation from the remote instance only works on a per-instance basis. If you have a mutual from an instance then every follower from that instance would see your theoratical “mutuals only” post, if the only access control you have is authorized fetch.

There are some people working on circles and other ways of limiting visibility more granularly than what we have, but those will have to be supported by both ends. You may be able to hack together a gigantic mentions only thread with double digits of people on there without modifying server code too much, but the UX there would be terrible enough for that to not be viable (and certain anti-spam functionality like hellthread MRFs may end up kicking in which prevent that from federating to instances that have those enabled (especially after the recent Japanese spam attacks))

Look into opening an account on an Iceshrimp instance like https://fedia.social, or an Akkoma instance like http://pleroma.envs.net. Their APIs are an extension on top of the Mastodon APIs (and both support Markdown and should expose them to apps). Sharkey also has some Mastodon API compatibility but it’s quite broken and might require some odd workarounds to get stuff working.

That said, for rich text, parsing the HTML will be more than enough for nearly all cases.

epic megapost