So, I used messaging here in the broad sense. One possible application for it is instant messaging, which there are ActivityPub implementations out there doing that. But it can also be used for statuses or pretty much anything else that gets federated.

It’s not, the demo video actually shows that being one such use case. There’s nothing stopping anyone from writing a chat service in ActivityPub. But this can also apply to statuses, media, all kinds of other stuff.

Actually, there’s a pretty decent possibility of this happening! Ben from Bandwagon is currently looking into this for the underlying Emissary platform. If it proves easy enough to integrate, there’s literally no reason not to.

Proving it in one project might see adoption across similar efforts.

Support for other providers is coming. Bandwagon is in a similar situation. The overall goal is to support a multitude of options, so that no one payment solution has a monopoly.

Probably not, but the tradeoff is that you’re limiting audience reach. Occasionally, this can also break context in public conversations, where someone might follow someone else who responds to you, but can’t see your original post.

OwnCast is wonderful. It’s dead simple to set up and use, and works great with OBS.

I tend to prefer streaming through PeerTube, simply because the platform has more features. But for simplicity, OwnCast can’t be beat!

If anyone is interested in seeing the recorded talks, we’re in the process of uploading them all to PeerTube! First day is uploaded, currently working through day two!

https://spectra.video/c/fedicon_videos/videos

I would imagine that this is getting addressed in the update as well.

A significant portion of the code is available, I think it’s just a matter of getting the latest code pushed out to public release status. Judging by the server repo, seems like a lot of development is happening out in the open.

https://github.com/joinloops

I mean, all of the videos are uploaded to PeerTube, and that instance (run by me) federates across a big chunk of the network. Like, yeah, the videos themselves live in an S3 bucket somewhere, but the metadata federation and P2P video capabilities (plus the ability to mirror redundant copies) somewhat mitigates that.

Wanting to get paid for your work, so that you can keep making stuff, is in fact not the same thing as greed. We have this assumption that everything on the Web should be free, or at least helped along by donations, but it’s not sustainable.

Channel is basically a white label instance of PatchWork, which is a Mastodon fork with custom feeds and community curation tools.

The main intent behind the project is to help existing communities and organizations get onto the Fediverse, and have some curation capabilities. Ideally, it can be used to get a large amount of people and accounts onto the network with minimal friction.

I always liked the concept of Matrix, and still actively use it, but there’s some serious jank. Synapse is generally bloated and not fun to run an instance, Dendrite is perpetually in Beta, and the clients themselves range from adequate to awful. The default Element client on Android is so broken for me that I’m forced to use Element X, because I can’t even log in with Element.

It’s disappointing, but there’s a ton of issues that aren’t so easy to resolve. New Vector and the Element Foundation are basically two separate entities that have some kind of hard split between them, neither of which seems to have the money necessary to support comprehensive development. The protocol is said to be bloated and overtly complex, and trying to develop a client or a server implementation is something of a nightmare.

I want to see Matrix succeed, I think a lot of people see the potential of what it could be. I’m not sure it’ll ever get there.

Thank you! I’ve been thinking about it a lot, and I think it could be used to solve a bunch of different problems, like importing stuff from other networks, and having everything ready to go before you join an instance.

There’s some UX questions that have to be figured out, the last thing I want is some super-cluttered design that asks for a million different options. Also, platforms would need to provide some necessary APIs (for registration and data import) to make it fully useable.

My main critique is just that, within the Mastodon side of the Fediverse, the design is highly misleading about what the feature does. It resembles a normal DM feature, but the message addressing is purely handled by mentions in the message body.

Basically, it’s an antipattern, causing people to accidentally mention other people in what’s assumed to be a Direct Message. It’s less about privacy, more about poor telegraphing of side-effects.

I used to feel that way, but there’s so much crap on that timeline, especially when you’re on a bigger instance. I used to use it for the exact same thing, discovery. A lot of it is just noise to me now, though.

Well, no, this was just responding to a critique on UX shortcomings, and highlighting how different efforts could solve various problems.

It sounds more like you’re talking about one of my previous blog posts, where I was talking about a super-flexible frontend that’s basically a pagebuilder. Make no mistake, I would love to see custom profile music and radios! And I agree that accessibility needs to be way better!

Yes

Oh nice!

I think a lot of people do it because they want to build communities and bring people together. It’s easy to underestimate the workload and what kind of problems come up. A big problem is that people start instances, and gradually realize that they’re basically stuck running things until they either hand it off to someone else, or shut down.