Conversation

Notices

Embed this notice
:mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Wednesday, 14-Feb-2024 18:53:37 JST :mima_rule: Mima-sama
in reply to

Oh, don't block fed.brid.gy too
In conversation about 10 months ago from makai.chaotic.ninja permalink
Attachments
1. Domain not in remote thumbnail source whitelist: fed.brid.gy
  
  Bridgy Fed
- Embed this notice
  :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Wednesday, 14-Feb-2024 18:53:39 JST :mima_rule: Mima-sama
  
  Anyway if your #fediverse instance has already blocked the brid.gy root domain I suggest bugging your #MastoAdmin / #FediAdmin to change that to only block atproto.brid.gy (and maybe bsky.brid.gy as well, though I'm getting conflicting info on which subdomain is going to be used) and nostr.brid.gy.
  
  web.brid.gy which actually works right now is perfectly fine, and you're just doing a disservice to your users who would want to interact with the #indieweb. :seija_coffee:
  
  #fediblock #fediblockmeta #fediversemeta #bridgy #bridgyfed #bluesky #blueskybridge #nostr
  
  RE: https://makai.chaotic.ninja/notes/9pp4ngznnl
  In conversation about 10 months ago permalink
  Attachments
  1. Domain not in remote thumbnail source whitelist: fed.brid.gy
    
    Bridgy Fed
  2. Domain not in remote thumbnail source whitelist: brid.gy
    
    Bridgy
  3. Domain not in remote thumbnail source whitelist: makai.chaotic.ninja
    
    :mima_rule: Mima-sama (@mima)
    
    @Weirdaholic@snowmans.land Worse because of this overreaction, many indieweb-powered websites depending on @snarfed.org@fed.brid.gy's bridge will now find themselves unable to interact with plenty of fedi instances. Great job folks, you really showed Jack Dorsey, or Bluesky, or big corp that we're tough in protecting our dear web! By killing the indie web... :reimu_sigh: RE: #fediblockmeta I only have a limited view into the discussions regarding that bridge to bluesky, but I already have seen one post calling to block not just the bridge, but also the instance of its creator. Is there any good reason to do so, except wanting to punish the creator(s) over a service, that seemingly can be blocked like any other instance (assuming, I can trust them on this).
  AnthonyJK-Admin repeated this.

Public

Conversation

Notices

Feeds