Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@julian Got it (and thank you!) - if you don't mind could you try to remove and re-add? I made some config changes that might punch it through.
-
Two exciting changes for the #Mastodon community this week:
1. It’s thrilling to see the team's hard work and thoughtfulness come to fruition with the launch of Quote Posts! (Coming soon to an instance near you in Mastodon version 4.5.) https://blog.joinmastodon.org/2025/09/introducing-quote-posts/
2. And the official launch of Mastodon’s managed hosting and service offerings. It’s an important step to help secure Mastodon’s financial future. It’s also one way Mastodon is working towards growing Mastodon and the #Fediverse beyond Mastodon.Social and Mastodon.Online. More to come on that front :) https://blog.joinmastodon.org/2025/09/service-offerings-from-mastodon/
Congrats to the @Mastodon team! <3
-
Sure, activitypub.space will hook up. It's pending right now though, which means the Follow got sent but we haven't received an Accept or reciprocal Follow.
-
Crakila Can you please try again with the latest develop commit? I updated the blocking logic to handle both activity retrieval and sending. Prior to this, it was only checking the domain on incoming activities.
I don't know whether this would explain why the posts from fairy.id still show up for you, but it's worth a shot.
-
Posting about my Mastodon Relay again, registration is open so feel free to add it (location of the relay is US East Coast). Would love to test traffic and jobs but haven't been able to with only 2 instances connected. https://circlewithadot.net/services/aprelay.html #mastodon #activitypub #fediverse
-
FWIW deleting an account won't block the user from coming back. If you navigate back to their profile (via direct link or clicked link, or if they're mentioned, etc.) NodeBB will just pull their account info in again.
-
That's a really good question! It might be that posts are still leaking through due to some other reason (maybe relays, maybe something else).
I'll have to audit the instance deny-list code and double check.
As for blocking individual users, there is no way to do this instance-wide yet. However that is a good idea, I will look into implementing this.
