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.

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)

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/

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

mastodon doesn’t “discover” akkoma content and won’t show anything unless you’re following a user from there, which kinda sucks.

I mean – that’s how all of them work. Even Lemmy. Unless your instance administrator joins relays (which have tradeoffs between privacy / effectiveness of blocking) your instance is only ever aware of posts from followed people (and reply threads followed people are involved in)

(also MUCH lighter on server resources, compared to most other twitter-like alternatives)

Mastodon is just unusually heavy, really. Even Misskey & forks are lighter than Masto on the server side (preferring being bloated on the client instead)

Mastodon feels like a fucking funeral.

You’re clearly nowhere near the good parts, then.

In my experience, once when you find your way into the correct circles the microblog-verse makes the “shitposting” of Lemmy look like r/memes. I do agree that discoverability could be better though, it took me 4-5 months before I got the hang of it. And now I barely check Lemmy despite my Lemmy account being older than my earliest microblog account (under this name, anyway).

One important thing is that your instance matters quite a bit more than here. Starting on a large general purpose instance (especially if it’s mastodon.social) and just following Large Accounts and Nobody Else like most people recommend for some reason is just setting yourself up for disappointment. Instead, get on a smaller interest-specific instance (rule of thumb: the weirder the domain the better your experience will be!) and follow the local timeline (and on good software, the bubble/recommended timelines). And post stuff/interact with people. Don’t be that one person that does nothing but boost news bots and occasionally butt into replies of people asking rhetorical questions they already know the answer for.

(Perhaps Lemmy is better at news or whatever, I wouldn’t know as I block all news communities I can find – I just don’t see the point as all the discussion around most news ends up predictable, unproductive (not that internet communities necessarily need to be “productive”), and unnecessarily angry)

Also in a world with usable™ Misskey forks and Akkoma I think the limitations of Mastodon the software are really starting to show, and I urge anyone who’s been disappointed in Mastodon to try other microblog software. (Quotes are already a thing if you know where to look! So are emoji reactions, because people have more emotions than :star:)

What I’m more worried about are posts relating to news mainly. Where even if the immediate first level comments are fine, there are threads that get out of hand really quickly.

I agree that while posts inherently designed to be controversial may not benefit from Active considering the influences voting has (though me being on an instance that has downvotes disabled may be influencing my view here!), Active may make it significantly easier for an otherwise innocent post to devolve into a flame war.

The main excuse for this kind of algorithm seems to be around “promoting discussion”, but in my experience tech that’s intended to promote discussion does inherently promote flame wars too, as they’re extremely difficult if not impossible to distinguish without a human in the loop. I’ve attempted to write something about this on the microblogging side of the fedi, directly influenced by this post

deleted by creator

I’m just throwing this out there but having the default sort incentivize comments seems like it’d highlight posts meant to cause flame wars… Is that what we want out of this platform?

the 0.19 implementation is so half-assed I genuinely think the Lemmy devs just don’t want that functionality but expected quite a lot of backlash if they outright said as much, so they decided to implement something that ticks the box in the “wanted features” list without having any effect

afaik it only blocks communities and explicitly lets users from blocked instances through

…and I thought of a web game you can make with this, if anyone’s bored and looking for something to do: https://brain.d.on-t.work/notes/9on0iba4evg40hic

• pick a random page
• find all pages nearby
• make the player guess the random page from the nearby pages
• if they haven’t guessed the exact page, compare the coordinates and score based on distance to the correct page

I have just been informed you can also see pages nearby other pages with a special URL query (apparently no interface exists for this yet)

https://en.wikipedia.org/wiki/Special:Nearby#/page/Utrecht

yeah same here unfortunately. but then I am currently somewhere I’d consider middle of nowhere

actually there was one plane crash but that’s not necessarily an article I’m interested in

tbf Lemmy’s behavior is documented and standardized (https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md) it’s just that their fallback code for instances that don’t federate the Lemmy way also boosts the target posts for each update as opposed to just once on creation like you’d expect

5. Linux tech support

how many times did you edit that post per chance? Lemmy seems to boost edited posts for some odd reason

see https://brain.d.on-t.work/notes/9md8phwlkzlj0xe9 and https://brain.d.on-t.work/notes/9m1y542jlg8002bj for it happening on my misskey instance hacked together to support Lemmy federation