this post was submitted on 21 Jan 2025
1677 points (98.9% liked)

Technology

60674 readers
4119 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
1677
Decentralized Social Media Is the Only Alternative to the Tech Oligarchy (www.404media.co)
submitted 19 hours ago by FundMECFSResearch@lemmy.blahaj.zone to c/technology@lemmy.world
287 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] futatorius@lemm.ee 1 points 3 hours ago (1 children)

and they suddenly decide they’re not into gaming anymore, you and everyone who relies on you will not get gaming feeds anymore

I was thinking along the same lines for different reasons. For multi-hop trust delegations, I'd really want a way to see what I'm seeing through the composition of all those blocklists. And once I've seen that, a "flatten into my own blocklist" command might be interesting: I want a snapshot of how A through B through C would look, and I'd like to mash it down into my own list so I can manage it there.

If a person A whitelists some content and person B blacklists it, and you follow both, what should be done?

Merge conflict alerts, just like version-control systems use? Allowing an order of precedence would be another way, but I think it'd get messy fast.

[–] Allero@lemmy.today 1 points 1 hour ago* (last edited 1 hour ago)

I imagine merge conflict alerts would be very common as well as it all grows.

Ideally, no user configuration on an everyday basis should be required.