@newt@stereophonic.space It's solely about control with these people. They don't act in good faith, they're bad actor narcissists with power fetishes. In another life they'd be law enforcement officers. @Kuara@stereophonic.space
Conversation
Notices
-
:verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Friday, 24-Nov-2023 04:31:03 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶 -
Pawlicker (purpcat@clubcyberia.co)'s status on Friday, 24-Nov-2023 04:31:00 JST Pawlicker @adiz @newt @Kuara cc @mint but basically if you wonder why a blocked instance won't show their posts on yours that's why.
As a happy little side effect it results in clients that don't support it yet being unable to federate. likes this. -
:verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Friday, 24-Nov-2023 04:31:01 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶 @PurpCat@clubcyberia.co I don't actually know enough about that to comment. @newt@stereophonic.space @Kuara@stereophonic.space
-
Pawlicker (purpcat@clubcyberia.co)'s status on Friday, 24-Nov-2023 04:31:02 JST Pawlicker @adiz @newt @Kuara the same people who push for authorized fetches btw -
(mint@ryona.agency)'s status on Friday, 24-Nov-2023 04:33:25 JST @adiz @newt @Kuara @PurpCat Will just quote myself.
"Basically, every ActivityPub instance uses HTTP signatures provided by other instances to verify that new messages actually come from said instances, this is normal since otherwise anyone with a copy of curl could forge them. Signed fetches extend this to GET requests for objects/activities (fetching posts from users no one is subscribed too as part of the thread context, for example) which is retarded since once the message leaves your instance, you have no control over it anyway: people can just go to your instance if API isn't locked, and if it is, go to the neighboring one."
-