handmade.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
handmade.social is for all handmade artisans to create accounts for their Etsy and other handmade business shops.

Server stats:

36
active users

#activitypub

20 posts15 participants0 posts today
Continued thread

(7/7) In short, we say #WebSocial instead of the #Fediverse to truly unlock the potential of what it can be, and that is a communication system built on top of established, decentralized technology, under the umbrella of none other than #W3C.

By unpoliticizing the word, we've basically given it verbage and actual purpose. Are you going to post content on #WebSocial with #ActivityPub? How will you do it? Single user? Multi user? Actual platform?

Giving creators that power can foster magic.

Continued thread

#WebSocial and #ActivityPub is the future for the #web, as any other web #technology, but we must also see how it can be used to create more diversity and opportunity.

Of course some of you are twitching, because now you're afraid of #ActivitySpam. It can't be helped though. At some junction that's just going to be a problem no matter what.

The point is Web Social is a tool to interact with other sites, with audiences, as well as users. Communicating like this encompasses it's purpose.

Continued thread

Of course, you do realize that I want the original #SpaceJam #Website to have at least a couple of posts using the #ActivityPub protocol, preferably one by @BugsBunny@SpaceJam.com that says:

"Michael sure can play! But everyone's distracted by Lola..."

And maybe some homage to Tex Avery, if he wasn't a complete monster.

In any case, you get my point. It's not actually a #SocialPlatform, a #Service, or any kind of #platform at all. The web just got a jungle telegraph. Have at it, Hoss.

Continued thread

This way, when I do promotional stuff for the web in future, I'll be taking into account that a domain can be project specific, like say a film that needs promotional static website, and that you don't want to run anything heavy here - because it needs to run for a long time.

But you might want the facade of #WebSocial. Like a site having tops 10 posts in it's lifetime - and that's it. All comment functions, all interactive parts of #ActivityPub are non functional because it was a one off.

Continued thread

Lately I've been pondering about how to actually create a sustainable business around #WebSocial, which framed thusly puts the job squarely in the lap of companies that do #WebDesign and #SysOps - where it always belonged.

It's more typified, normalized and familiar and can then also be viewed in a utilitarian way, in that #ActivityPub provides a public broadcasting function via the web.

Yes inbox, yes outbox, but no braining. Stahp!

Web Social a tool to broadcast content on the web. Das it.

(1/7) I have to remember to stop using the hashtag #fediverse, because we're supposed to say #WebSocial now instead. Why does that matter?

Language and optics go hand in hand, and as times have revealed, federation might not be the silver bullet people believe it to be, nor does it actually condense what the underlying technology is about.

We've essentially created a jungle telegraph in protocol form, that can take #ActivityPub into a weird and wonderful future.

Exciting community updates! 2TonWaffle is evolving with a clearer focus for both our main site and Indie Creator Hub. We're fully embracing the #Fediverse with #ActivityPub integration through #NodeBB and #Ghost platforms, making our content more accessible and connected than ever. Learn about our streaming plans on #Moonbeam and our vision for a more streamlined 2025!
2tonwaffle.com/platform-clarit
#IndieGaming #CreatorCommunity #CommunityBuilding

Hmm, looks like a general "followers only" problem with the ActivityPub protocol. IMHO. This is not so much a Pixelfed issue, as any software can ignore the request to wait for a follow and just follow a user anyway. 🤔 (ie if a bad actor wants to track "follower only" posts, they can build something to subscribe to followers only) #ActivityPub

fokus.cool/2025/03/25/pixelfed

fokus.coolPixelfed leaks private posts from other Fediverse instances - fiona fokus

A reminder, the Fediverse cost money.

Yes, it is free for YOU to use, but your local administrator pays for domain registration, web hosting, storage space, CDN, and of course, bandwidth.

The busier and more active your Fedi site, the most it cost.

If you are able, consider reaching out to your admin, and asking how you can help. Even small contributions add up and make a difference.

A reminder, the Fediverse cost money.

Yes, it is free for YOU to use, but your local administrator pays for domain registration, web hosting, storage space, CDN, and of course, bandwidth.

The busier and more active your Fedi site, the most it cost.

If you are able, consider reaching out to your admin, and asking how you can help. Even small contributions add up and make a difference.

#Fediverse #Fedi #ActivityPub #Mastodon #Misskey

Continued thread

Pixelfed before v0.12.5 has a vulnerability where it could leak your private posts, regardless of whether you are a Pixelfed user or not.
Admins should update ASAP.

When following someone from a different server on the Fediverse, the remote server decides whether you are allowed to do that. This enables features like locked accounts. Due to an implementation mistake, Pixelfed ignores this and allows anyone to follow even private accounts on other servers. If a legitimate user from a Pixelfed instance follows you on your locked account, anyone on that Pixelfed instance can read your private posts.

I wrote a blog post about how I found the vulnerability, how disclosure coordination went and general ramblings about Fediverse safety:
fokus.cool/2025/03/25/pixelfed

fokus.coolPixelfed leaks private posts from other Fediverse instances - fiona fokus

I just discovered why some of my followers from larger #Mastodon instances (like mastodon.social) would mysteriously unfollow me after a while!

A pull request was just merged in Mastodon that fixes a critical bug in their follower synchronization mechanism.

Turns out Mastodon implements the FEP-8fcf specification (Followers collection synchronization across servers), but it expected all followers to be in a single page collection. When followers were split across multiple pages, it would only see the first page and incorrectly remove all followers from subsequent pages!

This explains so much about the strange behavior I've been seeing with #Hollo and other #Fedify-based servers over the past few months. Some people would follow me from large instances, then mysteriously unfollow later without any action on their part.

Thankfully this fix has been marked for backporting, so it should appear in an upcoming patch release rather than waiting for the next major version. Great news for all of us building on #ActivityPub!

This is why I love open source—we can identify, understand, and fix these kinds of interoperability issues together. 😊

Mastodon implements FEP-8fcf: Followers collection synchronization across servers, but requires every identifier to be in a single page.
The reasons for only supporting one page are:

Mastodon must...
GitHubFix follower synchronization mechanism erroneously removing followers from multi-page collections by ClearlyClaire · Pull Request #34272 · mastodon/mastodonBy ClearlyClaire
Replied in thread

@stux
This can work temporarily - perhaps for a couple of years or at most 10 to 20 years. Unfortunately, it can never be a permanent solution. Nothing is free, and if you don’t pay, it comes out of someone else’s pocket.
Some groundbreaking method is needed for an independent #ActivityPub server to run financially independently without compromising its core values.
Thank you for your work @stux