That’s the problem with Netflix.

You open a browser. Because Netflix app is just a webapp anyway.

Powershell. I checked and the command is like PS > [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String(“YmxhaGJsYWg=”))

Noone is going to actually use this. Why it can’t be just “base64 -d” like on *nix?

For whois in Windows 11 search results points to a .exe program to download manually from Microsoft site. I didn’t know they included recorder recently, my bad. FTP client I didn’t know too, still it’s a console client and no integration in Explorer.

Office365 in the menu is just a webview.

It need to talk RCS first, then it could encrypt with MLS.

Like web browser that needs to speak http and then encrypts the traffic via TLS.

Oh but average person don’t care about C compiler, torrent client, blah blah blah.

Yes, they care. When they need help with their computer, call me and I have to install 10 different programs to do basic stuff. And I can’t just type names of programs into package manager and install all at once, no no no.

Yes! Really, how do you even calculate base64 using Windows? With freakn Microsoft Edge!

Windows don’t have preinstalled git, torrent, PDF reader, stresstest, whois tool, FTP client, C compiler, screen recorder, disk imager, markdown editor, 7zip/RAR/tar opener. Most Linux distros have it out-of-the-box and with smaller footprint.

Even Office. Office suite is not preinstalled on Windows, but on Linux is! But what is preinstalled is TikTok and Netflix download shortcut.

Isn’t dMLS just MLS but adopted for multiple servers?

Nope. This is standard purely for encrypting messages, nothing to do with open APIs or formatting messages themselfs. Basically TLS but for E2EE instead of SSL.

Only if Signal developers want to swap their Signal encryption protocol for MLS. And I doubt they will for next years, as MLS is not as battle tested yet. Signal is laser focus on security for “normies”, not interoperability or free software.

Good to remind that MLS is just an end2end encryption standard, not whole messaging standard. And like TLS is useless on it’s own and needs content protocol like HTTP to combine it with.

Stil really good, since this means bridges between networks adopting MLS, like XMPP, Matrix and RCS could work with full E2EE.

All of them.

Of course, but someone needs to add it and who still uses web browser to download system packages besides using some outdated system at friend’s house :).

Most software sites are staticly pre-generated. For just description, download, recent versions, links… there is no need for server side code. Also many browser obfuscate used operating system to currently most popular for fingerprinting restistace.

Wallabag is nice, you share a link and it archives it’s content like in reader view.

Companies to protect us from problem they created.

Instead of a fish, I’m going to give you a rod.

https://privacyguides.org https://gofoss.net https://european-alternatives.eu/ https://github.com/tycrek/degoogle

Pretty much, it’s going to be secured on VLAN and firewall anyway. Can be a preconfigured password, a pair button.

Can be a web interface, but one that does not send me an app compiled to JavaScript to run and those are hard to find there days. Can be even an SSH connection.

Most of those are propietary and unnessesary exist.

There are no FOSS friendly GIF repositories I know of.

Also it’s better to have one GIF keyboard for whole OS, not one per every app.