@p @nepfag @sjw
>what does it do
it signs object fetches with an instance-wide fetching actor signature to authentifucate the fetch. although we originally wanted to implement it when OCAP is a thing so we could only sign the capability negotiation, instead of every fetch, mastodon implemented "safe mode" which requires signing fetches of even public posts with httpsigs, so we decided to implement them as a temporary bandaid.
> What is it supposed to solve
admitedly, the feature probably originated from people who don't want blocked instances to see their public posts, but I am intrested in it because it allows
1. to send deletes/updates to instances that fetched the post, which is much better than our current approach (send deletes only to recipients of original activity) and mastodon's approach (send deletes to every known instance)
2. to delete fo posts/dms when compacting objects as well, because they can actually be refetched now
>what does it do
it signs object fetches with an instance-wide fetching actor signature to authentifucate the fetch. although we originally wanted to implement it when OCAP is a thing so we could only sign the capability negotiation, instead of every fetch, mastodon implemented "safe mode" which requires signing fetches of even public posts with httpsigs, so we decided to implement them as a temporary bandaid.
> What is it supposed to solve
admitedly, the feature probably originated from people who don't want blocked instances to see their public posts, but I am intrested in it because it allows
1. to send deletes/updates to instances that fetched the post, which is much better than our current approach (send deletes only to recipients of original activity) and mastodon's approach (send deletes to every known instance)
2. to delete fo posts/dms when compacting objects as well, because they can actually be refetched now
@rin @nepfag @sjw
> people who don't want blocked instances to see their public posts
If fetching unsigned works, and fetching signed does not, there'd be no way to stop an unsigned req after a failed signed req. There'd be almost no reason to fetch requests signed.
> because they can actually be refetched
The bofa.lol posts get to remain alive in all the instances that federated with bofa despite the server dying. I think this is a feature. A cool feature, in fact. You can have an instance with abysmal uptime but that allows people to still read and interact with the posts, because you don't have to rely on refetching.
> people who don't want blocked instances to see their public posts
If fetching unsigned works, and fetching signed does not, there'd be no way to stop an unsigned req after a failed signed req. There'd be almost no reason to fetch requests signed.
> because they can actually be refetched
The bofa.lol posts get to remain alive in all the instances that federated with bofa despite the server dying. I think this is a feature. A cool feature, in fact. You can have an instance with abysmal uptime but that allows people to still read and interact with the posts, because you don't have to rely on refetching.
@p @nepfag @sjw
> If fetching unsigned works
mastodon disallows unsigned fetches with their "safe mode", we probably will have something like this as well when there is a sane way to authentifucate fetches, but of course it won't be anbled by defaul until OCAP is the standart and is implemented by the majority of software
> The bofa.lol posts get to remain alive in all the instances that federated with bofa despite the server dying. I think this is a feature
we won't purge posts unless the users explicitly request it, I agree that having posts from dead instances is cool, but not everyone is going to keep a 100gb database just for that. being able to exclude dead instances from purges would be nice though
> If fetching unsigned works
mastodon disallows unsigned fetches with their "safe mode", we probably will have something like this as well when there is a sane way to authentifucate fetches, but of course it won't be anbled by defaul until OCAP is the standart and is implemented by the majority of software
> The bofa.lol posts get to remain alive in all the instances that federated with bofa despite the server dying. I think this is a feature
we won't purge posts unless the users explicitly request it, I agree that having posts from dead instances is cool, but not everyone is going to keep a 100gb database just for that. being able to exclude dead instances from purges would be nice though
@rin @nepfag @sjw
> mastodon disallows unsigned fetches with their "safe mode", we probably will have something like this as well
I think this is a really a bad plan and it makes me sad. It's not effective or sensible, especially given that if you wanted, you could just send requests through a server that was previously unknown: then you've made a signed request, it's "safe". They should just whitelist instances if that's what they want. This is worse, it just solidifies the stupid cracks in the federation that the same people caused to begin with.
> mastodon disallows unsigned fetches with their "safe mode", we probably will have something like this as well
I think this is a really a bad plan and it makes me sad. It's not effective or sensible, especially given that if you wanted, you could just send requests through a server that was previously unknown: then you've made a signed request, it's "safe". They should just whitelist instances if that's what they want. This is worse, it just solidifies the stupid cracks in the federation that the same people caused to begin with.
