Goofed Home

Profiles are the primary way for people using Mastodon to ‘meet’ one another on a deeper level – beyond a threaded conversation or search results. You might have noticed that the overall design of Profiles hasn’t been explored in a while, and in the meantime, we’ve heard requests and challenges from people who use Mastodon every day.

The profile redesign supports some of our current priorities:

Make the Fediverse Intuitive. We want people who are new to Mastodon and the Fediverse to be able to discover and connect with interesting accounts, without having to understand the details of decentralisation. The new Profiles view includes an updated handle explainer, and a new editing experience delivers a more consistent, unified experience across web and native mobile apps.
A Home for Everyone. As well as individuals, Mastodon is also home to organisations (NGOs, local governments, software projects, etc) that want to share news and interact with their communities. The layout changes offer us a solid starting point from which to explore features that will help these “institutional users” to make their most out of their presence in the Fediverse.

ooh facebooky

@silverpill @liaizon Which, fine, all resources from other places need to be restricted to prevent DoS attacks anyway.

New post: Can we have a more “social” media?

https://profpatsch.de/essays/a-more-social-media

On advertising, the Fediverse, and what a more human social web could look like.

Special mentions: @smallcircles, @phnt, @happy-programming

#fediverse #activitypub #socialmedia

@Profpatsch You need to create a new signature because the request target is changing. It is a part of a signature base, so the initial signature becomes invalid when the client follows a redirect.

@liaizon

@Profpatsch @liaizon The guide recommends limiting the response size, to prevent DoS.

I also found this in your SECURITY.md:

https://codeberg.org/Profpatsch/Profpatsch/src/commit/249aa389a2023814b328af8fc795750fd28d995d/users/Profpatsch/activitypub-go/security.md#response-body-size-limits

@fedilore Thank you 💕

@webbeef You're a new web browser? Neat! 👍

I don't think we have a “just do this one thing” solution for browser builders in ActivityPub right now. FedCM is a thing that people seem to be working on, but I gather it's a future target.

Maybe you'd like to incorporate the functionality of https://streetpass.social natively, I think that'd be a low barrier start.

Or talk to @benpate about what native browser support for Activity Intents might look like. I hear he doesn't have enough to do yet. 😇

Awesome!

I don’t mind Sonya Walger, I could see her in this role, whether or not she pulls it off is another story.

My ongoing #ActivityPub projects in order of priority, for anyone waiting for something:

– Interaction policy / reply controls FEP: highest priority, stalled for the past few weeks due to other responsibilities
– @encyclia: probably migrating from Deno+Fresh to Node+Hono for @fedify 2.0, boring infra work
– Updating @fedidevs starter packs for compatibility with @loops and @Mastodon packs: on warm hold, will get to it, but vainly hoping someone will write a Python lib for it before I have to 🙃

@north @liaizon @Edent Check https://datatracker.ietf.org/doc/html/rfc7564

@jdp23 Are they also using Bluesky's servers for DMs, since those are stored off-protocol?

Or do non-Bluesky AppViews just don't have DMs? (Or whichever part of the stack is responsible for that.)

@jaredwhite @_elena

@jdp23 Looks a bit involved. Interesting read, though, thank you for sharing!

@_elena @jaredwhite