Free human being of this Earth. Be excellent to each other! All my posts here are CC BY-SA 4.0 (or later).
#Vegan #Permaculture #Transition #PeerProduction #FreeCode #CreativeCommons #SciFi #Comedy #Juggling
Timezone: UTC+12
deleted by creator
@regalia
> I recommend actually looking at what it looks like on the site, it’s extremely different then how it looks on mastodon
Yes, I’m familiar. I’ve been following Lemmy development for several years, as part of research for fediverse.party. That’s the background to my comments about the algorithm determining what appears on a Lemmy front page.
If you’re proposing that there’s a more complicated algorithm at work, what do you think it is?
@regalia
> Are you replying from Mastodon right now
Yes. Here’s the post you just replied to, on the public-facing web page of the Mastodon server I use:
@regalia
> the algo for active/hot favor large communties, so smaller ones tend not to show up on the front page
I presume it’s the same as what determines which posts appear on the front page of a Mastodon server; chronological order of posts. That would favour the larger communities, since people post there more often.
The other limiting factor, I presume, is a Lemmy server only knows about the communities its accounts are members of. Larger communities will have members on more servers.
@regalia
> our algo doesn’t do a good job of promoting smaller communities
Lemmy has an algo for that?
@deadsuperhero
> development of a Go-based backend implementation, Dendrite
Also Rust-based homeserver implementations like Construct and Conduit. Both of which are usable, although missing a few nice-to-have added features. Eg Conduit is still working on;
“E2EE emoji comparison over federation (E2EE chat works)… Outgoing read receipts, typing, presence over federation”
@deadsuperhero
> the reference implementation everyone uses by default is known to be bloated and slow, and poor at scaling
This doesn’t seem to stop the fediverse growing (*cough* Mastodon *cough*).
@smileyhead
> But noone figured out how to prevent that in federated systems
You’ve basically got a choice been a centralised service where metadata can be limited but E2EE is mostly pointless (you have to trust the service operators’ E2EE deployment), or a decentralised network where E2EE is reliable, but it’s harder to limit metadata.
Which one is best depends on the situation/ threat model.
@deadsuperhero
> I’d really love to see a “modern” WhatsApp-like take on an XMPP messenger, but I haven’t found any
Have you looked at @snikket_im ?
@Rambi
> but how come your username says @null?
No idea. Maybe a bug in your app? Maybe something to do with the fact I’m posting from a Mastodon server rather than Lemmy server?
@theKalash
> Lemmy neads a feature where people can “merge” communities from different instances so it appears like a single one
I’m confused by this. I’ll admit I haven’t used Lemmy much yet, but I thought communities do exist across all servers? So if I join “c/fediverse” on any one server, and you join “c/fediverse” on any other server, we’re joining the same community. Is that not how it works?
@itadakimasu
Plus, the Lemmy servers are part of a much larger network; the fediverse. Not just other forum apps like KBin either. Right now I’m replying to this from Mastodon.
I have an alt on a .nz Lemmy server, but haven’t got into the habit of using it yet. So at least some of the perceived shrinkage *is* due to that, rather than any failure of the network. Also due to spam and troll accounts being purged.
(2/2)
@itadakimasu
> there’s only 60k of us? And that’s a good thing?
A centralised platform is a numbers game. The money for upgrading servers for growth has to come from one company, and if the platform shrinks it gets harder to get a return on that spending.
It just doesn’t matter as much in a federated network. The cost of growth is spread across many servers. Some of which will end up shutting down, for a range of reasons. But others have room for growth.
(1/2)
@theory
> Is there a good fedi or p2p alternative to twitch?
#OwnCast was designed specifically for this:
#PeerTube also has livestreaming capabilities, as well as being able to host recordings of livestreams for future playback after they’re over:
There’s also #GreatApe, which is entering beta and looking for testers:
@Hexadecimalkink
> Did peerfed ever figure out the bandwidth issues? Is there a way this can scale?
If this is the PeerFed you meant, I’m guessing the answer to both these questions is ‘no’;
“This paper has been archived and no longer reflects the author’s current thinking.”
https://github.com/joshdoman/peerfed-paper
Although I do find this concept intriguing;
“The system consists of two convertible assets, interest-bearing cash and a paid-in-kind perpetual bond.”
https://github.com/joshdoman/peerfed-paper/blob/main/peerfed.pdf
@yogthos