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.

Yeah, it was kind of an obscure project to begin with. Still, it struck me as an excellent way to prototype federated services that all hooked into a singular identity.

Hopefully, it inspires future work.

Nope! The main thing going for a distributed ledger would be global consistency, but there are some very negative downsides. It’s slow, scales poorly, puts a massive burden on admins operating instances, and the blocks would be effectively immutable…meaning that if the contents of each activity were fully nested inside of a block, edits or deletions would be impossible. We already see problems with CSAM showing up in various blockchains, and a Fediverse blockchain used for social purposes would be no different.

It’s just not the right tool for the job when it comes to social networks. There were a few early experiments in this area, such as Twister, which tried to build a Twitter clone on top of a blockchain using DHT. It has a huge list of limitations, though, and development stopped around 2020.

Yeah, Wafrn uses both protocols, and basically runs its own PDS and AppView.

Remote profiles appear to show up, it might be possible to also remotely pull in posts. I didn’t see Subscribe functionality in Lemmy, but maybe PieFed or MBin support that.

Honestly, it’s a tough choice. Hubzilla can theoretically do everything you want, but there’s a steep learning curve.

One thing that might help is to narrow down what kind of features you want. What I’m seeing so far from your description is:

• Blog / HTML hosting site
• space for webgames and assets
• code?
• Something like Facebook?

Friendica and Hubzilla] (and everything derived from them) are theoretically right up your alley, but each interface is kind of janky and introduces a learning curve of some kind. Misskey is extremely good, and often feels like the most polished option for long-form stuff. You’re kind of limited on clients, though, as most mobile apps use the Mastodon API. Some Misskey forks add support for it, though.

I know you said you didn’t like WordPress, and I get it. However, the actual ActivityPub integration is really really good, and continues to improve. If you self-host WordPress, there’s hypothetically enough extensibility there to build everything you want. However, WordPress as a platform can be extremely janky. We tried doing it for We Distribute, and there’s a bunch of stuff under the hood that doesn’t quite work right with Fediverse integration. Then again, we’ve been doing a lot of experimental stuff over the years, so it might be different with a fresh install.

Yeah, I was a long-term Hubzilla user some years back. There’s some really cool stuff that it can do, but it seems to get slower and more bloated the longer you run it.

Yeah, it’s not great. Unfortunately, there’s not a great way to describe this stuff without either leaning into abstract terms, or using oversimplifications.

The short of it is: only half of the ActivityPub protocol really got adopted by most of the Fediverse: the stuff that lets servers talk to each other. The other half would allow for a lot of cool things to be built, with not everything being its own Fediverse server.

Honestly, it would be kind of cool if you just had a simple app to log in with your Fediverse identity, and it rendered your existing profile on the page and allowed you to put additional links.

I don’t think it necessarily needs to federate.

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.