Amber <amber@transfem.org> To: fediverseobservatory@cyber.harvard.edu Subject: Fediverse Observatory Hello, I am quite interested in this. I am Amber (@puppygirlhornypost2@transfem.social) and I help manage an instance with ~1,600 users. I also work closely with projects like https://activitypub.software/TransFem-org/Sharkey/ & https://iceshrimp.dev/iceshrimp/iceshrimp.net I think this would be a great tool to help validate our AP implementations! I noticed on the page that it'll be an open source project. > This application will be open source under a to-be-determined license, and a hosted version will be available to the public to explore the data (which only a preapproved set of researchers will have the ability to annotate). I have a couple of questions: 1) When do you think we'll be able to experiment with hosting an instance of this ourselves? 2) How is this going to work with Authorized Fetch? 3) Is there any plan on having integration with specific fediverse software? 4) What's the procedure to opting in as a relay? I ask the third one because Misskey uses Redis (or a redis equivalent like valkey) to store our inbound and outbound job queue. If you made a component that could fetch from redis (and other server software's preferred software of choice for said queues. Iceshrimp.NET uses postgres for all of the job queues) that would allow instance administrators to explicitly opt-in, providing you a lot more data than a simple relay would. This is important because recently there was an issue related to Akkoma and Sharkey (a fork of misskey) having broken federation for report forwarding. We were unable to send and receive reports from remote akkoma instances.

Amber <amber@transfem.org> To: fediverseobservatory@cyber.harvard.edu Subject: Fediverse Observatory Hello, I am quite interested in this. I am Amber (@puppygirlhornypost2@transfem.social) and I help manage an instance with ~1,600 users. I also work closely with projects like https://activitypub.software/TransFem-org/Sharkey/ & https://iceshrimp.dev/iceshrimp/iceshrimp.net I think this would be a great tool to help validate our AP implementations! I noticed on the page that it'll be an open source project. > This application will be open source under a to-be-determined license, and a hosted version will be available to the public to explore the data (which only a preapproved set of researchers will have the ability to annotate). I have a couple of questions: 1) When do you think we'll be able to experiment with hosting an instance of this ourselves? 2) How is this going to work with Authorized Fetch? 3) Is there any plan on having integration with specific fediverse software? 4) What's the procedure to opting in as a relay? I ask the third one because Misskey uses Redis (or a redis equivalent like valkey) to store our inbound and outbound job queue. If you made a component that could fetch from redis (and other server software's preferred software of choice for said queues. Iceshrimp.NET uses postgres for all of the job queues) that would allow instance administrators to explicitly opt-in, providing you a lot more data than a simple relay would. This is important because recently there was an issue related to Akkoma and Sharkey (a fork of misskey) having broken federation for report forwarding. We were unable to send and receive reports from remote akkoma instances.
https://cdn.transfem.social/files/9afa1ebd-f887-4a68-a26c-b694afde8f83.webp

Notices where this attachment appears

Public

Notices where this attachment appears