Mauve 👁💜 @mauve@mastodon.mauve.moe

One thing I like about chronological timelines is I have no clue who I follow is "an influencer" or a random shitposter. A person with 100 followers is just as visible as 100 thousand.

on algo based media it's just mostly cool kida that get shoved in people's faces and I guess into each others faces.

@smallcircles Interesting. The vibe I'm getting after reading the landing page is that this is a way you can coordinate volunteers to pool time together to work on stuff that they're all interested in. Is that an accurate read?

@smallcircles Neat is it more of a "lifestyle" community sort of thing?

personally I'm going to be experimenting with cooperstive governance models for distributed publishing this year so I'll add this to my todo list for figuring out the tradeoffs. :)

Gonna be taking a couple weeks off work though so I'll get back into it in october

@helge @mariusor Interesting, are folks relying on videos ti use libraries instead of docs these days? For some reason I thought folks only needed videos for "learn to code" type scenarios. I typically read example code and unit tests to get a feel for how stuff works.

@mariusor @helge actually could you send me a link to your code? I have a golang based database I want to connct to the fediverse anyway and it'd be nice to reuse something :P

@smallcircles Neat! Is this cryptonomocs or consumer coop type stuff?

@helge right now I'm focused on making it easier for web publishers to use this stuff and with all our work being in the open for devs to peek at and reuse 🥰

My wip blog post about it: https://github.com/RangerMauve/blog.mauve.moe/pull/1

Tbh these two guides and peeking at my mastodon data got me all I needed. :P

https://paul.kinlan.me/adding-activity-pub-to-your-static-site/

https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/

It was honestly trivial compared to some of the stuff out there 😅

@mariusor @helge Are you using your library for yourself and your own interests? That's the best way to do open source IMO. Whether a thing is "popular" or not is secondary. As long as it's useful to *someone* it's a win IMO. Unless you want to makey money off of it I guess, but that's a whole other ball game 😅

One thing the fediverse has that email doesn't is communities that care about their instance. I genuinely think this is it's biggest strength to combat centralization.

@steve @evan @djsf @bengo Like when they inevitably try to add ads to AP or whatever shit we can give them the finger and fork from any impl that's shitty enough to go with it. Prople thay want big social media corps can go ahead and use em, and existing AP communiyies can do fine without it.

I think it's mostly the monolith instances like .social that will cave to incorporate whatever facebook wants of them

@steve @evan @djsf @bengo Yeah but will existing fediverse users even give a shit about it or its standards? These are spaxes people made for theor communities and to talk to other small communities. If we wanted millions of users one the one big instance we'd already be on facebook or whatever.

@evan @djsf @bengo yeah! I'd love to see them put out implementations based on the current specs and gain community trust before going behind closed doors to make decisions on something that is used by thousands of people that could be harmed by corporate control 🤷

@evan @djsf @bengo Hmm I think maybe the difference is I'd like them to implement but not be in charge. The power dynamics would be so imbalanced compared to anything else. IMO it'd be nice if AP was more like HTTP where we had the core more set in stone unlike how stuff like Group Ware and email got turned into something non–corpo impls couldn't coexist with easily.

@evan @djsf @bengo I'm only willing to bet that if Google and or Facebook have more sway over ActivityPub that it'll lead to another XMPP EEE moment. "Gmail 2: the death of mastodon"

@evan @djsf @bengo I don't disagree with that statement. I'm just not a fan of large corporations being at the streering wheel. We already have a great ecosystem and community of folks working on implementations. They should be in charge since they're the ones most affected.

My hot take is that the #ActivityStreams and #ActivityPub specs are fine. Having some more standards for working with groups might be nice but honestly I'm happy with how much folks are able to do already and how many implementations are out there that can work together. This is from a few months of working on a new implementation. Honestly there's been a decent amount of docs spread around the place to go off of.