Create a Starter Kit with all your existing friends/fam and share the link or QR code and the invited person will be onboarded and auto follow all accounts in the kit, along with other auto settings.

The best part is Pixelfed Starter Kits are ActivityPub objects, and will be compatible with other software!

I am working on a FEP 🚀

#pixelfed#starterKits #fediverse #fep

I could make start.fedi.pub a landing page for Starter Kits, allowing users to select the client of their choice, aside from Pixelfed.

Lots of possibilities with Starter Kits, and I look forward to working with other projects to establish a shared spec, aka FEP!

#pixelfed#starterKits #fediverse #activitypub #fep

@thisismissem@hachyderm.io in a post yesterday brought back the idea that better post controls could be achieved if the reply were sent to the target only, and the target then forwards it if applicable.

It reminded me of @trwnh@mastodon.social's https://w3id.org/fep/7888, which attempts to govern a similar flow where a reply is sent to the context owner (instead of inReplyTo, which I think was Em's intent), and the context owner (and/or originating server) federates out an Add if approved.

Which got me thinking about whether that federated server could actually send out a Remove too!

Let's say a reply is made but later on, a mod decides that it is to be deleted. A Remove would be a way to signal to other instances that the content actually be removed/deleted!

We could even take it one step further; servers will always exist who don't adhere to the philosophy of the context owner approving replies. If they federate their own replies out, the context owner could actually proactively send a Reject and limit the spread of those replies...