Conversation

Notices

1. Embed this notice
   :blobcathug: (jain@blob.cat)'s status on Friday, 28-Apr-2023 22:23:08 JST :blobcathug:

   • puffaboo :puffhyper:
   @emilis Do you mind explain me why? At least i would like to understand why not...
   • Embed this notice
     :blobcathug: (jain@blob.cat)'s status on Friday, 28-Apr-2023 23:20:11 JST :blobcathug:

     in reply to

     • puffaboo :puffhyper:
     @emilis well, thank you for your response... feel free to ignore my answer if you dont wana discuss that further, but i would like to give you my insights on this:
     For admins its an easy thing to detect if someone blocked their server or not. Based on this fact, i wouldnt say that there will be more drama than without communicating them... The only benefit from making this information transparent is that it is easier to find out an issue when someone asks an admin and it would be more transparent for the servers user in the first place tho :blobcatshrug2:
   • Embed this notice
     puffaboo :puffhyper: (emilis@puff.place)'s status on Friday, 28-Apr-2023 23:20:12 JST puffaboo :puffhyper:

     in reply to

     @Jain@blob.cat federating instance rejects or having them be public creates social issues. People cannot behave on the internet and will assume all kinds of shit about a block, which leads to rumors, pitchforks, "reeeee u block me" shit, etc.
     And for what? So you can check if someone will get your reply by going out of your way to do so (when fedi software doesnt make that apparent on the user end anyway).
     Then you have people actively obsessing over being blocked. Whether its because they want the drama and are like oh no woe is me im blocked again, or the braindead "haha look how hard i can piss" type. Why feed that kind of derangement? It's absolutely absurd.
     
     It's literally not that deep, the issues caused by the lack of publicly available block info is not even worthy of a tiny violin.

   • Embed this notice
     :blobcathug: (jain@blob.cat)'s status on Friday, 28-Apr-2023 23:26:50 JST :blobcathug:

     in reply to

     • puffaboo :puffhyper:
     • Jeder :blobPikaSleepy: :baa:
     @jeder @emilis thats one simple way to check so (but a not exactly reliable way)... i think its easier to just look at the about page and on the best case it would even have a reason for the block
   • Embed this notice
     Jeder :blobPikaSleepy: :baa: (jeder@miau.jeder.pl)'s status on Friday, 28-Apr-2023 23:26:59 JST Jeder :blobPikaSleepy: :baa:

     in reply to

     • puffaboo :puffhyper:

     @Jain@blob.cat @emilis@puff.place for me best workaround for this is to just answer like you would and then check if this even shows up on the other side, it's probably faster than having to check the damn list anyway

   • Embed this notice
     :blobcathug: (jain@blob.cat)'s status on Friday, 28-Apr-2023 23:32:45 JST :blobcathug:

     in reply to

     • puffaboo :puffhyper:
     • Jeder :blobPikaSleepy: :baa:
     @jeder @emilis :blobcatgoogly: they do that?
   • Embed this notice
     puffaboo :puffhyper: (emilis@puff.place)'s status on Friday, 28-Apr-2023 23:32:46 JST puffaboo :puffhyper:

     in reply to

     @Jain@blob.cat The "if there's any way around it, it's pointless" train of thought is completely besides the point. Not to mention that instances that federate this information (or have it be scrapeable) will inevitably have it be scraped by block databases, like fba. The complexity increase in figuring out the network of blocks is huge between openly shouting it and not.

   • Embed this notice
     Jeder :blobPikaSleepy: :baa: (jeder@miau.jeder.pl)'s status on Friday, 28-Apr-2023 23:32:49 JST Jeder :blobPikaSleepy: :baa:

     in reply to

     • puffaboo :puffhyper:

     @Jain@blob.cat @emilis@puff.place yeah i'd rather not have to deal with fash trying to persuade me in emails that they aren't bad