Comment

This is the solution. Communities need to congregate on smaller, like-minded instances. It makes sense to concentrate users on large instances, but communities should be spread out.

source

Sort:hotnew top

_Mantissa@lemmy.world ⁨1⁩ ⁨year⁩ ago
[deleted]
source
- cerevant@lemmy.world ⁨1⁩ ⁨year⁩ ago
  
  Is there a place for something in between de-federated and federated?
  
  That’s what blocking a community is - if the instance does not allow anyone to subscribe to a community, the content from that community will not be mirrored locally.
  
  Is there not some kind of ‘gray-list’ that would allow risky content to stay accessible through home instances but behave more as a direct link
  
  The indirect approach you describe isn’t compatible with the underlying ActivityPub protocol. My understanding is that all communities are effectively local, even when their home is on a different instance. Federation just allows modification of the “local” content by another instance.
  
  (That is not to say that technology@lemmy.world is the same community as technology@lemmy.ml, rather that the two communities are accessed in the same way by the UI)
  
  source
  - _Mantissa@lemmy.world ⁨1⁩ ⁨year⁩ ago
    [deleted]
    source
    cerevant@lemmy.world ⁨1⁩ ⁨year⁩ ago
    
    I suppose it could still be done as a read-only display of content …
    
    If the content is hyperlinks / torrent links to copyrighted content, then even a read-only copy is illegal. Lemmy (by virtue of ActivityPub) isn’t designed to access stuff remotely - the closest it could probably come would be to have links to the posts on the remote community, though adding a level of indirection is probably not enough to become legal.
    
    If you want to do illegal stuff on the internet, you need to use services that are hosted where it isn’t illegal. People yelling about freedom doesn’t change the fact that admins aren’t willing to go to jail for your warez.
    
    source