this post was submitted on 16 Jun 2023
128 points (100.0% liked)

Technology

37821 readers
653 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Perhaps I've misunderstood how Lemmy works, but from what I can tell Lemmy is resulting in fragmentation between communities. If I've got this wrong, or browsing Lemmy wrong, please correct me!

I'll try and explain this with an example comparison to Reddit.

As a reddit user I can go to /r/technology and see all posts from any user to the technology subreddit. I can interact with any posts and communicate with anyone on that subreddit.

In Lemmy, I understand that I can browse posts from other instances from Beehaw, for example I could check out /c/[email protected], /c/[email protected], or many of the other technology communities from other instances, but I can't just open up /c/technology in Beehaw and have a single view across the technology community. There could be posts I'm interested in on the technology@slrpnk instance but I wouldn't know about it unless I specifically look at it, which adds up to a horrible experience of trying to see the latest tech news and conversation.

This adds up to a huge fragmentation across what was previously a single community.

Have I got this completely wrong?

Do you think this will change over time where one community on a specific instance will gain the market share and all others will evaporate away? And if it does, doesn't that just place us back in the reddit situation?

EDIT: commented a reply here: https://beehaw.org/comment/288898. Thanks for the discussion helping me understand what this is (and isnt!)

(page 4) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 2 years ago

This is a problem that is big now, but I think can also be solved with maturing the technology in the future.

Right now I have multiple accounts for multiple bubbles, but I can easily imagine some app or website that can congregate the content coming from multiple instances and choosing the appropriate account for it to post/view with.

Thus allowing one to access bubbles that have shut each other off in one central place. Unless they do it by completely blocking sign ups in which case they isolate themselves willingly and that is also good in a way to have as an option.

If I can imagine all this as a random system engineer, surely some developers with a passion for this and open source collaboration etc. can too.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

IMO this is just a temporary problem - as communities establish themselves one will eventually become dominant. E.g. /c/[email protected] might become the dominant technology community, while others die out or stay small.

Think about it - it's a feed forward system. If one community of a certain subject has more users, it will generate on average more content and therefore will attract more subscribers, thus generating even more content.

[–] [email protected] 1 points 2 years ago (3 children)

Ultimately this is a problem that's never going away until we replace URLs. The HTTP approach to find documents by URL, i.e. server/path, is fundamentally brittle. Doesn't matter how careful you are, doesn't matter how much best practice you follow, that URL is going to be dead in a few years. The problem is made worse by DNS, which in turn makes URLs expensive and expire.

There are approaches like IPFS, which uses content-based addressing (i.e. fancy file hashes), but that's note enough either, as it provide no good way to update a resource.

The best™ solution would be some kind of global blockchain thing that keeps record of what people publish, giving each document a unique id, hash, and some way to update that resource in a non-destructive way (i.e. the version history is preserved). Hosting itself would still need to be done by other parties, but a global log file that lists out all the stuff humans have published would make it much easier and reliable to mirror it.

The end result should be "Internet as globally distributed immutable data structure".

Bit frustrating that this whole problem isn't getting the attention it deserves.

load more comments (3 replies)
[–] [email protected] 1 points 2 years ago

These things have a way to sort themselves out with time so no point in stressing over it.

load more comments
view more: ‹ prev next ›