It’s Twitter
It’s Twitter
You cannot specify ports in a DNS A or AAAA record. www.example.com cannot resolve to 1.2.3.4:443 and app.domain.com cannot resolve to 1.2.3.4:5555
If the application (be it a game or whatnot) supports it, SRV records can identify a port for a hostname. So, you could have minecraft1.domain.com and an SRV record to specify port 25565, and minecraft2.domain.com SRV 25566.
This means you can have multiple Minecraft servers with the same IP address, but you won’t need to give people the port numbers to remember; the hostname allows the game to look up the port via the SRV record.
This is great for selfhosters because we generally only get one IP (until they rollout IPv6; probably half the reason they don’t)
NEFTLIX
Almost like an AI wrote it
Yeah I’ve fallen into this trap before as well. When I shop for a desktop, I tend to go as high-end as I can afford and then sit on the same machine for 7-10 years until it becomes unusable/support begins to wain. That desktop sits under my desk and doesn’t move that whole time, it is in a very controlled environment.
You cannot shop that way for a laptop that will be moved and handled and charged and stowed and scratched and bumped and bent and twisted. Even if you take excellent care of it.
You are correct, but the way people reacted is certainly conditioning from the rug-pulling enshittification going on daily in the tech world. (What are we all using instead of redis, again?)
This is a much more level take than your first comment.
They didn’t try anything. Stop inventing. Go read an actual article on the subject instead of feeding the scarebait frenzy.
“I only read the headline and the comments from the threads a week ago, I am truly disappointed in Bitwarden’s stance against FOSS as I’ve misunderstood it.”
I can’t believe Microsoft is doing EEE on malware
I wish instead of complaining to people that they didn’t read the docs or whatever that linux devs would scour the internet for these criticisms (like when specifics are provided) and then develop solutions for them.
Yeah, people are shitting on your product because it’s not obvious. Make it more obvious!
(Thankfully this is starting to happen…)
A motorcycle the dude works on himself
I own several Analogue products. They’re solid AF.
FPGAs would be considered “hardware emulation” but a lot of people don’t like that term, and think emulation should be a term limited to software.
Like, there aren’t real N64 chips in there. The hardware IS emulating an N64 - it’s just not doing so in a way that’s comparable with software emulation at all.
Passkeys are basically client certs for website logins.
Server stores a public key, encrypts a challenge on login attempt. Client browser uses private key to decrypt challenge (and sign it maybe?) and respond to web server to authenticate.
Hackers can’t get a shared secret (like a password or password hash) by hacking the website’s database becaus the public key is all they store; useless without the private key.
Not foolproof, but much harder to exploit than passwords - which many people re-use across multiple sites.
Wasn’t there multiple password managers that got powned over the years ?
Pretty much only LastPass
That’s weird, it works for me. Is there something you need to click on the mobile site?
Bitwarden just announced a consortium with Apple, Google, 1Password, etc to create a secure import/export format for credentials; spurred by the need for passkeys to be portable between password managers (but also works for passwords/other credential types)
All the major password managers store passkeys now. I have every passkey I’ve been able to make stored in Bitwarden, and they’re accessible on all my devices.
Article is behind the times, and this dude was wrong to “rip out” passkeys as an option.
That is patently false. Encrypted email and patient portals are absolutely allowed under regulation.
What you have here is a practice that has probably been in operation since the 80s or before, and they refuse to change their ways.