I use both Lemmy and Akkoma, but yes I used to be quite active on Hubzilla when I ran an instance of it.

Ah, good to know, thanks for the correction 👍

I don’t really have a need for most of the features Hubzilla offers, so I think I’ll stick to my Akkoma instance. But I encourage people to check out Hubzilla, as it is a neat project overall.

Since Pixelfed already supports that, I would assume yes.

It’s true that Hubzilla has access permissions for files on your WebDAV folder, and those access permissions sort of federate to other Zot protocol using sites (but not the wider Fediverse), but Nextcloud also has its own inter-Nextcloud federation where you can access files on other Nextcloud instances right inside your Nextcloud.

Well, for various reasons I stopped hosting my own Hubzilla instance some years ago, but back then it absolutely had CalDAV and CardDAV. The problem was mainly that this wasn’t well exposed in the Hubzilla web-interface, other than an event calendar. But with Thunderbird and DAVx5 etc. you could connect to it and manage it just fine. The WebDAV file storage part worked fine in the web-interface as well.

Edit: these parts are not federated though AFAIK (contrary to Nextcloud which does have some kind of file-sharing federation).

Yes and WebDAV support.

I think originally it tried to be a Facebook alternative, but over time it developed into a personal cloud space of sorts. I would agree with the comparison to Nextcloud as of 5 years ago, but these days they pivoted into the enterprise space and isn’t that nice for home users any longer.

Wordpress obviously.

Friendica, Hubzilla and Streams also work quite well for long-form blogs.

The original project was called Owncloud and was made largely by the same people, but they split over a disagreement in management.

I briefly talked with the responsible person at the EDPS during last year’s CCC congress, and “money” isn’t the real issue.

The EDPS overstepped their mandate when setting up this pilot and due to the typical bureocratic clusterfuck no other organisation wants to take responsibility for the necessary infrastructure.

Ugh, that will be a pain to fix indeed then. Makes it much more understandable that they take their time with it, but hopefully they also fix their backups.

Ok, good to know that it is still the same as before.

The web-UI and Pictrs image host has been down for more than a week now, but the backend API for app use and federation was still working. But I have the feeling that sometimes during the last 24h that also went down, or at least I haven’t seen a post relayed from them during that time.

I really don’t know what’s going on there, but at least initially someone said they ran out of storage on their server. But it seems odd that this takes more than a week to fix. Maybe the main admin is on holidays?

I think this could be easily achived with an activitypub FEP and an alternative Frontend for Mastodon etc.

Why reinvent the wheel?

This is very likely fake somehow. The source-code of the banner links to: https://github.com/Linuzifer/domain_seizure

Wikipedia is not a good source on this. By the time Google’s XMPP based messaging product was renamed “Google Talk” it had long ceased to be compatible with the wider Jabber federation.

While I agree that Google does also sabotage their own messengers, it was deeply involved in XMPP specs development and other stuff around the ecosystem in the beginning, and then just quietly began to blockage urgently needed changes as they were unwilling to implement them in their system.

But I guess this discussion has reached the end of being useful as you clearly have a lack of understanding what actually happened back then.

Google Talk was never Jabber. The Google Jabber integration was way before that in Gmail. Google Talk was what came after Google decided to abandon Jabber.

And yes Google very much held Jabber back by having the largest user-base in their Gmail integration and refusing to even implement SSL for that let alone supporting any other innovations like better mobile support. If Google had actually supported Jabber instead of sabotaging it, we would not have this discussion.

It’s not dead, and works fine. I am not disagreeing that it had a serious set-back but that’s water down the river.

Also WhatsApp is using a slightly modified version of XMPP, so your argument is a bit funny :)

Well, Monal on iOS doesn’t work worse than Telegram on iOS, so then apparently it’s flawless as well. I am not an iOS user, but I heard complaints about Telegram on iOS as well regarding notifications.

That’s a bad implementation then. Modern open-source XMPP works great on mobile, no problems with notifications at all on Android. iOS is more of a mixed bag, but that is solely Apple’s fault and applies to all messengers other than iMessage.