That’s because most of the parties here suck.

“It sounds like a password”

But did they have lowercase english language?

Salve! John Doe nomen meum est.

Only latin characters allowed

(That’s all the latin I remember from school back then)

The Romans also had spaces in between words

\n already is an escape sequence, consisting of \, the escape character, and n, the code that is responsible for the new line. Together they form an escape sequence.

Easy, John\nDoe

Hands down, Rust 🦀

they can subsidize EV manufacturing to the same degree

Meaning that we would either have to increase tax rates or borrow more money? Wow, what a great solution.

AMERICA 🇺🇲🇺🇲🇺🇲🇺🇲🦅🦅🦅🦅❗❕❕🗣️🗣️🗣️🗣️🗣️🔊🔊🔊🔊🇺🇲🦅🦅🇺🇲🦅🇺🇲🦅🍔🍔🍔🍔🍔🍔 FREEDOM 🗣️🗣️🗣️🗣️🔊🔊🔊🔊🔥🔥🔥🔥🥶🥶🥶🥶🥵🥵🥵🥵🦅🦅🦅🇺🇲🇺🇲🇺🇲🇺🇲🇺🇲🇺🇲🇺🇲🦅🦅🇺🇲❗🇺🇲🇺🇲❗🦅❗🦅❗❕❗❕❕❗❕❕❗🇺🇲🇺🇲🇺🇲🇺🇲🗣️🗣️🗣️🔊🔊🔊🔥🔥🔥🔥 DELIVERING DEMOCRACY TO THE DESERT 🦅🦅🦅🦅❗🔊❗❗❗🔥🇺🇲🇺🇲🔥❗❕🔊✈️✈️✈️✈️✈️💣💣💣💣💣💣💣💣💣☢️☢️☢️☢️☢️💥💥💥💥💥🦅🇺🇲🦅🇺🇲🔥🔥🔥🥶🥶🥶🥵🥵🥵🦅🦅🦅🇺🇲🇺🇲

Fuck yeah

You mean like this?

Violentmonkey is better anyway

Firefox should really implement a feature that hides this bullshit from the previous sites menu

For my fellow fish shell users: git log --graph --abbrev-commit --no-decorate --date=format:'%Y-%m-%d %H:%M:%S' --format=format:'%C(8)%>|(16)%h %C(7)%ad %C(8)%<(16,trunc)%an %C(auto)%d %>|(1)%s' --all

So it knows about all metadata

Metadata is encrypted on the client-side using Signal’s sealed sender implementation. The client also removes as much metadata as possible. All of this is open-source and happens in the client application.

plus registration with phone number

Signal doesn’t store phone numbers. It derives a user id from your phone number along with other parameters. It’s in the open-source server code, you can check it out yourself.

you need to use the client built by Signal

No you don’t. I myself use a fork of Signal called Molly.

with dependencies from Google Services and the like

Not true again. You don’t need to use the official binary that includes Google libraries. These aren’t required for the app to function. You can use Signal-FOSS or Molly-FOSS, and it works just fine.

and you can’t use one built from the source they provide

If this was true, forks like Signal-FOSS or Molly wouldn’t exist.

Which at that point means they can introduce whatever they want in whichever version.

Stupid conclusion, because all of your previous points are false

Stop spreading false information, focus on the facts.

Yes, but metadata is still important.

We Kill People Based on Metadata

– Michael Hayden, former director of the NSA

Signal having the server code closed source for more than a year so the Signal devs could get a headstart and insider knowledge

That argument makes absolutely no sense. This server-side code does almost nothing. The only task it really has is passing around encrypted packets between clients. All of the encryption is client-side, of course including metadata encryption. That’s how end-to-end encryption works. The server code really doesn’t matter. The Signal protocol, which is used for client-side, local, on-device end-to-end encryption has always been fully open, and it can be used by any app/platform.

How one can trust Signal after them showcasing what they truly stand for is mind blowing

It’s very simple. The client is open source, and the encryption happens locally within the client application. You don’t need to trust anything or anyone except for the code and mathematics, which are fully open, so you can verify them yourself.

It’s mind-boggling how people attempt to spread so much misinformation while having absolutely no understanding of the topic their talking about.

Unencrypted means that it’s not just exposed to participants of the conversation, but also the server, as well as anyone who tries to snoop in on the conversation.

Thankfully there are Signal proxies, VPNs and Tor (which can be used on mobile devices through Orbot.

Matrix lacks metadata encryption