JadedBlueEyes

Edited, ty

But yeah the support room is more likely to be able to help debug

Given nginx is logging a client disconnect error and curl succeeding, it sounds like the issue is in the client. Trying different clients and/or browsers may reveal the problem.

Moderation tools are powerful but desperate to the server. Asgard.chat offers some hosted options, but meowlnir, Draupnir and policyserv are the usual tools.

Element X doesn’t support the traditional way of making accounts, try use cinny.in to make an account in the browser and then log in with element X. Fluffychat should also present a “create a new account” button above the login button. Make sure to follow instructions in the console for registering the first account.

The federation port not being accessible won’t break local functionality but will break federation, so you won’t be able to talk with other people. Either change the configured port in the well-known file or forward the port via your reverse proxy.

I’d suggest joining the support room via an alt account, you’ll get faster responses.

Posting a 3 coming on 4 year old post, of course it’s not going to be accurate any more. And that’s for the points that aren’t just fear mongering in the first place.

• Redaction exists and removes the contents of events, while keeping metadata needed for the functionality of the room.
• Any program can handily ignore deletion - back when I used discord I had a handy plugin to view deleted messages for moderation, for example.
• Badly behaving servers can behave badly and it will not affect correctly behaving ones, they will apply redactions as expected.
• “Room joins leaves, etc are permanently a part of the room’s history” well yeah, that’s expected. You can upgrade a room if you want to start from scratch there.
• We can now prevent spammers from ever entering the room with join gates, among other things - but if you’re not running a big public community, then our antispam tech is probably completely unnecessary for you
• Currently, timeline ordering is defined by the server. Continuwuity uses a simple, understandable and secure scheme - it orders by the time your server receives messages.
• As per the above point, this doesn’t affect Continuwuity
• That’s a tradeoff of allowing public rooms with tens of thousands of people in the same app as end-to-end encrypted DMs. Good job Matrix isn’t really meant to be a Signal competitor.
• this point was relevant… Four years ago. You’ll only encounter issues if you’re using a broken server or ancient client now.
• “Started trying to filter recently” god you can tell how outdated this is
• It defines it pretty damn strictly now, and this isn’t an issue in practice for a very long time.
• Mmm yeah I don’t think you’re particularly likely to experience one of those in day-to-day usage.
• and this is false lol
• Ancient and fixed
• False. There are many ways to do this.
• I’ve never encountered this, and it’s impossible in new rooms versions.
• Aand outdated by years again
• see above
• see above
• see above

Because it’s not true, and hasn’t been true since 2018 at the latest.

That is slightly misleading, they are/were sponsored by epost.ch / Swiss Post AG, which is a limited company.

Voilà

Image

The alternative is to search the name right next to the code in this design

Also fonts.google.com/specimen/Sour+Gummy?preview.scri… is way better than comic sans, you can’t convince me otherwise

Everything there (aside from perhaps not printing the full URL under the QR code) is deliberate and a part of the ‘brand’. Roboto + Sour Gummy for the fonts, asymmetry, whimsy. If you don’t like it, I’m sure you can use Element’s Synapse and you’ll be able to talk to people using Continuwuity just fine. That’s kind of the point.

It is!

Yeah, I see your point, and I included the link in the alt text. On the actual design itself though, any URL I wrote in could be completely different from the QR so it seems slightly pointless - especially as it would just be writing Continuwuity a third time haha

On desktop? Yes. On Element X? Not yet. Requires additional setup, as it’s not a core part of the homeserver

A lot of the people reporting issues with Matrix being slow and resource heavy are reporting issues with Synapse, which is Element’s big Python implementation. My Continuwuity instance, which is a server written in Rust, uses a fraction of a CPU and a total storage in the hundreds of megabytes. A few less features, but it has most of the ones people care about.

That page seemed outdated, but: From further down that page:

The recommended strategy is to share the keys automatically only to verified devices of the same user

This is the same situation where the key backup is accessible - which is not described on that page, but it’s a key store of all the megolm keys. This is what is now generally used instead of that as it doesn’t require devices to be online and allows recovering keys if all devices are lost.

Matrix encryption keys don’t need other people online - they get queued up as messages for each device you have.

You might want to check out matrixrooms.info, which is good for a search around. Some project communities also have offtopic rooms that are good to chat in. Even very small rooms can be very active.

continuwuity.org or forgejo.ellis.link/continuwuation/continuwuity

As for the difference: lemmy.world/post/33271240

“can’t guarantee the authenticity of this message” just means it was restored from backup. In the same vein, if you can decrypt a message in any client, it should upload the keys to the message backup so it can be decrypted on other clients, even ones that haven’t logged in.

Continuwuity developer here - Conduit is reviving itself, and you can no longer move from Conduit to tuwunel or Continuwuity. You haven’t been able to for as long as either project has existed. You might be confusing conduwuit with Conduit.

I’ve only seen this message in the last months where different servers are having network issues and can’t talk