A clean, calm space to share ideas, follow meaningful conversations, and connect across the Fediverse.Come take a look and tell me what you think #Fediverse #Typent #SocialWeb #ActivityPub

"how to not regret c2s"w.on-t.work/activitypub/c2smy opinions about how activitypub c2s ought to be implemented, probably with way too much snark for anyone to take it seriously. wrote pretty much all of it at like 1 am so expect the writing to not be great. will prolly regret it tomorrow but eh. whatever#activityPub #fediDevs

@evan @fribygda meowth that's right!

@julian Cool!

@nixCraft summarizes it pretty well

#ImportColetivosFelizmente tem gente que não curte a #efemeridade atual da internet... E teve o dom de criar e manter uma linha do tempo do #fediverso!Começa lá em 2008 com Evan , isto é, o #fediverso já é um adolescente!#ActivityPub começa em 2014 e #Mastodon chegou em 2016. #Zot chegou em 2018https://im.youronly.one/techmagus/kb/ddfon/federated-social-network-timeline/Originalmente publicado **aqui**

@Flipboard @Sarahp @Techcrunch @renchap @imanijoy I know I'm the selfish curmudgeon: New faces always mean disruption of a kind. I love the people I've found on Mastodon. I don't want those voices drowned out.In the same breath I'm so excited for new people to join up and bring their excitement and energy. Hopefully while finding a way to make everyone feel safe here.

What does a Discord replacement look like, and how might the open social web play a part? @laurenshof looks at what needs to happen — different apps built on the same protocols, active collaboration to make sure it all fits together — and how that's already fundamental to the Atmosphere and fediverse.flip.it/QdL.F…#ActivityPub #Mastodon #ATProtocol #Bluesky #Blacksky #Discord #Technology #Tech

My reply from the threadiverse to you

Great! Works okay.

Recently, I noticed in my blog database export that a couple of ActivityPub users unfollowed. All at the same time. It was strange. Until I noticed all were GoToSocial (GTS) users. In the logs I found the reason: GoBlog failed to deliver some updates to the users, and so the accounts were marked as dead and removed after twenty failed tries. This sent me on a new journey to check GoBlog’s ActivityPub implementation. First I fixed HTTP signatures to be compatible again with GTS. I also added a test with GTS’s HTTP signature library to prevent that from happening again. But now, I also added more complete integration tests: the tests will start a GTS container in a Docker network. Another Docker container with Caddy inside proxies requests back to GoBlog on an example domain. This way I can completely test ActivityPub interactions. All local, no public access needed. And it also runs in GitHub Actions, verifying no commit is breaking ActivityPub. I hope that’s a great base for implementing more ActivityPub functionality, such as following people (I still have to think about the UX here; maybe the received posts can be exported as a private RSS/JSON feed?) or the option to move actors (which might help with the domain migration I might want to do one day). If you are interested in how I implemented this without a big framework like TestContainers, take a look at this file. AI helped implement this, but I took over the wheel after AI failed after hours of trying. Real intelligence sometimes still beats artificial ones.

Mastodon is a black hole. ActivityPub Academy receives my notes, Mastodon accepts them and ignores them. That's a bit annoying. In the meantime, I've remembered the mention speciality, which I'll probably never understand. You can only federate if you adapt to the peculiarities of Mastodon. The spec is ActivityPub, but federation is unfortunately Mastodon. #activitypub #mastodon

Listening to that podcast about a forky fediverse and it kicks off with the idea that EXPLAINING it must be super hard and complex.I don't see that at all. I see journos trying to overthink a very simple idea. There was once a time when using a "computer" meant going into the office and connecting your screen to a big machine. But things changed and people started using computers in the home. And eventually, even in the palm of your hand. Computing became "distributed" instead of "centralised".That's the difference between the Fediverse and the Zuckerverse. It's pretty simple really. I think journos just look for complexity sometimes instead of getting to the point.I'll agree that getting started as an individual can be awkward. Not complex even, just awkward. It's a new frontier. New rules. New tools. But none of this is unfamiliar really. We just need a friend to help us log on and get started. The internet was always like this.#Fediverse #ActivityPub #SearchEngine

the time is now...https://www.youtube.com/watch?v=-GY9DWIfpwc#fediverse #atproto #activitypub

@julian Yeah thanks for quicker and more simple setup process as well, Discourse was not simple to get running on a janky network like mine.

@joel@gts.tumfatig.net I am on NodeBB, and it parses the Markdown if sent, but uses the HTML more or less as-is (with sanitization for safety). So — yes. I can also see your italics <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f604.png?v=03884acde30" title="" />

Tudo que a extrema direita e a burguesia quer é nos ver desunidos. Vamos somar ao invés de fragmentar. #oBonde + #ActivityPub = ️

Tudo que a extrema direita e a burguesia quer é nos ver desunidos. Vamos somar ao invés de fragmentar. #oBonde + #ActivityPub = ️

Bonfire has just released a new version, which includes initial support for Mastodon API endpoints (interested how this will work, as Bonfire has sooo many more post control options) And…initial work on an ActivityPub C2S API! https://bonfirenetworks.org/posts/bonfire-1-0-1-building-momentum/#ActivityPub #Fediverse #Bonfire

@eyeinthesky@mastodon.social said in The W3C/SocialCG #ActivityPub "API" (AKA Social API or C2S protocol) Task Force states that it is inspired by the Facebook Platform.: > (I didn't receive a notification for your reply and only saw it by accident. Maybe an AP interop issue?) Just interjecting quickly — you didn't receive the notification because @evan didn't tag you in his response. Mastodon was sent the response, but did not notify you. It is a limitation of the Mastodon platform that it will not notify unless you are directly mentioned. Possible solution is for me to just sneak in a mention even if it is not in text, but I don't much like that approach.