sknebelwhat do you mean by "trust"? its a HTTP endpoint, of course everybody can send whatever they want, its on the server to verify that it wants to do something with what it gets sent
sknebelreply to someone on the server. there might be some implementations that push out comments a post receives to all followers of the original poster (I dont think most do, but it'd have a use case to provide a more complete view of threads everywhere)
sknebelor if A shows posts publicly anyone could just randomly find it on the web, decide to reply and do so (e.g. in mastodon you can put a post URL in the search UI and it'll try to fetch it as an AP post, if it can it lets you interact with it)
Loqi[preview] [prologic] β³
In-reply-to
Β»
@prologic It seems to me this distinction is pedantic and mostly at the server level. I have a mastodon account and I have no impression that I am being forced to read things I don't want to read. I follow the people I want to foll...
sknebelthat could be something like from above " there might be some implementations that push out comments a post receives to all followers of the original poster (I dont think most do, but it'd have a use case to provide a more complete view of threads everywhere)"
Soni<Soni> uh we don't think there is a best approach. something like cehttps/content-enabled http makes more sense from a "what's a protocol" point of view, but it does lack this... uh, well, we can't easily push it on browser developers like we can with fedicraft.
Soni<Soni> for what it's worth, something like https://modrinth.com/mod/fedicraft can be done entirely without browser support, as we currently do, which enables us to push it on browser developers. however, it requires website support instead. it also might not be the best approach.
Sonibrowser devs don't trust users with privacy-preserving cross-app interactions, they think any cross-app interactions are too dangerous yet it's fine to do it using a centralized service instead
[aciccarello]Like, I think it'd be cool if we didn't need to stay within the feed but could still like/comment/share from the browser. That's what's cool to me about the indieweb and tools like omnibear.
aaronpkhttps://fedidocs.org/ Possibly interesting to those who have attempted to interop with other ActivityPub software
ross[m]123, benatkin, micheledm[m], starrwulfe[m], Gorro_Rojo[m], geoffo, vladimyr, cambridgeport90[, jbrr[m], cellular and [jamietanna] joined the channel
Soni[aciccarello]: tools like that seem to train the user to give their interests away to other websites. which is extremely phishable. just give the user a plausible-looking phishing page that looks exactly like what they'd see with such a tool and they'll happily just give away all of that info without knowing any better.
aaronpkin theory you sohuld be able to use the refresh token to get a new access token. i haven't actually tried that yet or seen whether logging in on the phone revokes that refresh token too
[pfefferle]I tried to re-use the access token from my first api call experiments, following your post to change the handle and that seemed to be revoked
[pfefferle]Then I will try to find out how to refresh a token, so that I only need username and password for the first call and do not have to persist them