The name does do what it says & in just 4 char

JMP does that

One of my longer-term goals is to integrate Mumble on XMPP (others have thought about this too) since its chat is pretty shit & needing accounts to join isn’t great but or two good foundational protocols.

XMPP is better for modularity which is why everything is at extension with means the foundations are simple & easy to implement where you can build something optimized & bespoke on it like Fornite’s coms or Nintendo’s presense. It’s a little harder to understand tho since out of the box you get almost nothing—but the big servers intended for chat like Prosody & ejabberd have sane defaults.

The centralization you are referring to seems more a client issue since the protocol & servers already ‘do the things’ but it sounds like you want a single ‘app’. For community building where you consider group calls less common, both Movim & Libervia offer more than Element (note the other Matrix clients are lacking feature parity) since they both can do integrated posts like forums—where Libervia supports calendars/events too. There’s no reason a client couldn’t exist with Jitsi or Mumble integration.

Ultimately use the right tool for you—it’s just nice to dispel myths that Matrix has some special sauce or that predecessors can’t fill the same roles (while also using less resources in all directions).

Treating social media as social media makes sense. If you don’t want your issue tracker to turn out like this, then stop using the social media code forge.

Independent but then their coms are purely proprietary, US-based sludge. If you think folks should be contributing to your project, you should be using technology where you can where you & your contributors can patch & make better too. There is no good reason to be limited to only Microsoft Github & Discord.

Don’t get it wrong: I have followed for years & want the project to succeed, but this reliance on corporations & not giving your users a private option where they can control their data needs to stop. Normies have ignorance excuse but software makers do not as they generally know better about how these tech firms operate.

What does indexing have to do with actually getting to own your data & not participating in corporate-owned social media? If you want to straight hide it all, you would never post it to the internet. Most of us sought the refuge of Lemmy to avoid these platforms & know our post aren’t harvested to profit for a Lemmy IPO.

Recruiters can find you regardless, but also are not very useful for getting a job versus having a network & the cut they take means you get the shaft if hired thru them too. A platform like LinkedIn is drivel that will absolutely rot your mind so it should be an easy skip.

History / sync is known as message archive management (MAM) & every normal modern client & server supports it. OMEMO uses same double-ratchet encryption & multiple clients as Matrix (with the same old client key dropping issues sadly). By default it does not support groups you are correct, however, FOSS Jitsi (& Zoom for that matter) is powered by XMPP under the hood & can be stood up by yourself.

Personally three of my circles have opted for separate Mumble servers for voice coms (I run one of them from my living room) as video is only ever rarely needed & the system resources is minimal. Having web cams on is seen as a chore & distraction sometimes. The only time video is helpful in my experience is screen share which is different—but screensharing is the worst tool for trying to do code pairing / debugging a terminal using upterm provides a crisper view experience, lower data/system requirements, & observers can optionally drive the remote session.

You can easily self-host your static landing pages. There are decentralized (& self-hostable) social media options—such as Lemmy that you are on now. There is no need to involve Microsoft, & these big places like Reddit, or whatever, someone will eventually repost your content if it is good.

Also you code forge itself doesn’t need to be social media web 2.0. You can keep these separate.

Entice how? Spinning up XMPP on any hardware is simple to federate with you—& I wouldn’t wish they all self-host Matrix instances. XMPP’s jingle protocol works for voice/video & I use it self-hosted with my partner. What are the others missing considering the weight of the applications is literally felt. If you want a web client with stickers & reactions (& calling), what is Movim missing? Replacing forums is a part of the problem, not something to replicate… Movim & Libervia cover community posts that are web searchable.

IRCv3 for accessibility if I need it to be centralized & TLS is the only useful encryption (such as a public chat room); otherwise XMPP + OMEMO for decentralized (but also is great for public chat rooms). No need to reinvent battle-tested, mature standards.

Cheeky answer would be: CodeForges ∩ {MS GitHub}^c^ (anything but)

I’ve been primarily using Darcs & a little Pijul, but have been using Codeberg when I need to use Git or just self-hosting via SSH.

You could switch some of the problems with perf in switching away from the Python implementation server as well as Element clients but these support the most up-to-date features & the majority of users are now relying on these features that often don’t degrade graacefully.

The bigger issue is eventual consistency. Eventual consistency will not scale for small self-hosting. Every message & every attachment for every user in every chatroom they have joined must be duplicated to your server. This is why joining rooms sometmies takes 10 minutes. Even if you make this async from the client side instead of the current long wait, your server & storage are still taking the hit. A lot of small collectives had to drop their servers for performance & cost (read about yet another one today on the Techlore thread at c/privacy where now only Discord is used for realtime coms). This model is required to copycat the ability to search the entire history like the big, proprietary chat apps such as Slack/Telegram/Discord, but they are centralized so it is easier to manage—but its overuse for all announcement & trying to replace forums turns it into a black hole for information. Your small community probably does not need persistent chat like this—persistent info is lighter & easier to crawl as feeds & forums. With medium-sized servers shutting down, only the biggest & smallest hosts are still kicking with most metadata is largely centralized around Matrix.org who also hosts some of the other larger instances.

If you agree that chat can be chatter as well as ephemeral there is lightweight centralized chat in IRCv3 with TLS has most of the features you need with a longer legacy & massive choice for clients & XMPP for lightweight decentralized chat with a long legacy, client options too, & can be self-hosted in a bedroom on a toaster in comparison which increases the chances of self-hosters & decentralization. These were built in a time when we didn’t have such wasteful taste in tech since they needed to be efficient & only sip power/data in comparison both for clients & servers & storage. The bigger question IMO is what are fundamentally wrong with these two mature options that we need a new option built on unextensible JSON & Israeli Intelligence money?