People complain about how they hate to use the command line in Linux. But they don't similarly complain about these ultra obscure, ugly commands. When Microsoft necessitates commands, somehow it's different.
Do people complain about that? Like, life long windows/mac users who aren't interested in linux I guess? I always thought people loved being able to do everything from the command line.
You didn't have to use to do this to your OS when Windows was still good.
It's only the absolute shitfest that Win 10/11 ended up being that you have to conjure 300 arcane powershell commands just to get the OS to resemble a productive environment.
> People complain about how they hate to use the command line in Linux
They do? How else does one use Linux if not via CLI? You mean those kiddies that like GNOME/KDE? pfffft, they're not "using" Linux. They're just using Linux to run other apps no different than using a ChromeBook
You're not supposed to do this, this is to get around a restriction on installing Windows 11 on certain hardware. If your computer is supported and you install it the way Microsoft wants you to, then you won't be typing any commands anywhere.
Generally curious, I don't see anything about hardware. Isn't this is about making a login that doesn't require you to login to MS's cloud. Also, what HW restriction does Microsoft want? Why do they care?
Windows 11 requires TPM 2.0, that's the actual reason a massive number of PCs can't update to it. There's apparently some way you can hack around that and install it. I assumed that's what these videos were about. But from the reddit post it looks like it's talking about both that and the account login issue which I wasn't familiar with.
> including how to install Windows 11 without logging into a Microsoft account and how to install Windows 11 on unsupported hardware.
That's not really the use-case for this. It's not possible anymore to use Windows with a local account (for a long time), the official UI only lets you login with a Microsoft Account. These commands are not used to install Windows on an unsupported PC, they're being used to create a local-only account.
I for one still got a Windows boot partition next to my Linux, but I refuse to create an account for it. The only way I can install Windows on my supported PC with a local account is by using these commands.
You used to be able to just press a small button. Then you had to disconnect the LAN cable and not connect a WLAN to create a local account. Then you had to open the Commandline and execute a single command. Now we're at the point where you have to execute multiple commands.
If they actually manage to make it impossible to use Windows local-only, that will truly be the nail in the coffin for me. Currently use Windows to play games which aren't supported on Linux, but this will turn into a hate_for_online_forcing > appreciation_for_kernel_level_anticheat_shitgames.
You'd be surprised, most of the people who actually signed up so far have been lovely folk just looking to pick my brain about what they're building, ask about what I've been thinking about, tell me about their kids birthdays, and all round just be nice humans interacting with (a questionable) human (me)
DoH is the enemy of all self-hosters. When port 443 is used, you can't discriminate on it - to perhaps monitor it, work towards debugging it, block it, re-route it, etc. DNS shouldn't be a stow-away within some other protocol like HTTP, hiding from network-level scrutiny and control.
DoT is the friend of all self-hosters. Self-hosters need to control their own DNS if they want to use SSL within their LANs, within their self-hosted VPNs, and within their own self-hosted VPN subnets especially (I use Wireguard subnets a lot). Secure DNS with TLS, sure, but this control-ability, at the port level (853), is what a self-hoster needs to keep their life sane.
WebRTC is very, very hard to code for. But if FFmpeg abstracts that complexity away, then WebRTC becomes much easier to add to a software project wishing to benfit from that which WebRTC offers.
I guess I still don't understand. You don't really "code" with ffmpeg. It just is used to transform media formats or publish to a public streaming endpoint.
All of ffmpeg’s functionality is accessible from C (and transitively most other programming languages) via libavformat, libavcodec etc. FFmpeg supporting WebRTC means that projects using these libraries gain support for WebRTC in code.
Gajim, the XMPP client, has been awaiting this for a long time! Their Audio/Video calling features fell into deprecation, and they've been patiently waiting for FFmpeg to make it much easier for them to add Audio/Video calling features back again.
"If I type the @ symbol in a group to mention a participant Meta AI is in the list." - I just tried it myself in a group chat, but I don't see it. Maybe it's just starting to be added? or was made invisible to being listed by "@"?
I run Prosody XMPP server on a cheap VPS, and appreciate how it's a stock Debian package, greatly simplifying security updates. It's delightfully lightweight on the server.
I use Conversations as a client in Android, and Gajim in Linux.
The basics like OMEMO, file attachments, push-to-talk voice memos (in Conversations, but not Gajim) work well. All comms are at least client-to-server-encrypted, and the OMEMO-protected comms are end-to-end encrypted.
actually, push-to-talk voice memos do work Gajim. An underrated feature!
Prosody allows voice and video calls - I have a TURN server all set up with it - but QOS rules (which are beyond my control, and are the fault of the ISPs I use) can sometimes squash calls made.
Gajim 1.9.3 (Flatpak) seems support voice and video calls to Conversations, but then it doesn't work. One Conversations smartphone can make voice and video calls to another Conversations smartphone.
reply