>meanwhile just referencing the activity ID of the Follow alone would be insufficient
In theory this should be sufficient. I do that, works with most software.
>meanwhile just referencing the activity ID of the Follow alone would be insufficient
In theory this should be sufficient. I do that, works with most software.
An Accept can be as simple as (have a Follow activity as the object field):
{ "@context": [ "https://www.w3.org/ns/activitystreams" ], "type": "Accept", "actor": "https://example.social/users/subscriber", "to": [ "https://fedi.example/users/poster" ], "object": { "type": "Follow", "actor": "https://fedi.example/users/poster", "object": "https://example.social/users/subscriber" } }For the best case, you can just copy the whole Follow activity into the ‘object’ field; meanwhile just referencing the activity ID of the Follow alone would be insufficient.
So thanks to @arcanicanis I've gotten past the signature roadblock and have run right into the next problem. Sending an Accept message when I get a follow/unfollow/etc.
This should be straight forward, and I'll start poking at this over the weekend, as of right now I'm tired and $WORK is being a total beetch.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.