hexbear visible again?

⁨15⁩ ⁨likes⁩

Submitted ⁨⁨4⁩ ⁨days⁩ ago⁩ by ⁨GrayBackgroundMusic@lemm.ee⁩ to ⁨meta@lemm.ee⁩

Hexbear disappeared for a while. I guess they’re federating with us again? What changed to make them want to do that again?

Comments

Sort:hotnew top

silent_water@hexbear.net ⁨4⁩ ⁨days⁩ ago
local-only comms landed in Lemmy so our comms for marginalized folks don’t have to deal with the influx of people randomly driving by with soft bigotry. we also got controls for whether DMs are federated or not, which also helps.

source
- GrayBackgroundMusic@lemm.ee ⁨4⁩ ⁨days⁩ ago
  What are local-only comms? comms = communications or communities? I’m going to assume communities. Does that mean that hexbear can have communities that only native hexbear users can see?
  
  source
  - silent_water@hexbear.net ⁨4⁩ ⁨days⁩ ago
    yup, you got it. comms are communities, which is why it’s /c/comm_name on lemmy. an unfederated/local-only comm is only visible through the instance that hosts it. you can access it without logging in but only via the hosting instance.
    
    e.g. people from other instances don’t need access to the instance feedback comm and shouldn’t be able to participate in internal discussions about instance policies.
    
    source
  - Leon_Grotsky@hexbear.net ⁨4⁩ ⁨days⁩ ago
    
    I’m going to assume communities.
    
    Correct.
    
    Does that mean that hexbear can have communities that only native hexbear users can see?
    
    Correct, though this was a Lemmy update not Hexbear so most instances should be able to use this feature if I understand correctly.
    
    source