I’ve owned/used HPs, Dells, and several Thnkpads and the thinkpads by far are always the best machines. They are built to last, support is top notch.
Album on lemmy.ca, beehaw.org, shit.itjust.works & lemmy.world
I’ve owned/used HPs, Dells, and several Thnkpads and the thinkpads by far are always the best machines. They are built to last, support is top notch.
Mull is Fenix stripped of it’s play store requirements with arkenfox built in.
Only lawyers and politicians would be dumb enough to break DNS
I dunno how regular arrests and shutdowns is shaking the sabre. It’s straight up using it.
Where’s the fear mongering?
These shutdowns and arrests occur regularly.
The 40 warnings here were to resellers, not viewers. Although they have warned users of services in previous busts.
How do you think Spotify works?
Are you gatekeeping gatekeeping now?
Yea, prolly already using it.
I thankfully have never had the misfortune of cgnat
Yeah dropping Nat is the biggest net benefit I agree but I think the avg person won’t really find that much value in it when Nat works ok
Your prefix can change yes but the recommendation is that it shouldn’t in practice. You’ll find ISPs doing it right will extend your PD lease infinitely unless you release it for a long enough period of time. Similar to ipv4.
The privacy is similar to ipv4 also. All your traffic on ipv4 looks like it’s coming from your WAN IP… Your PD is in this sense equivalent (though not literally equivalent for all the pedants reading) to your WAN IP.
It’s honestly super simple to set up. Outside of your ISP config it’s almost all autoconfig. 100% of the complication (at least for me) comes from knowing ipv4 first for 20 years and then trying to incorrectly map those concepts to V6.
As soon as I “let go” it was fine.
There’s not a huge net benefit you’re right. I mostly wanted to learn and I hope to be at the front edge of disabling ipv4 in the near distant future.
I agree with this but I would say the prefix is the only thing you should focus on.
It’s important that ISPs don’t regularly rotate your PD and it’s part of the rfc recommendations that they don’t. And the remainder of the prefix is your vlan space that is as important for VLAN routing as always.
Ipv6 requires fundamental rethinking about how addressing is done. If you’re trying to apply v4 concepts to V6 you likely end up running into something they intentionally designed out.
A unique local address is an address space where you could do that. It’s the equivalent to RFC1918 eg. 172/192/10. So you could statically assign fd0::x, and that is expected, but not required generally.
I wouldn’t give each device a static unique global address unless they need to be accessed via wan without domain consistently. You lose device privacy really quickly that way because every device gets a unique globally routable address. It’s fine for internet facing services but most Linux, Windows, and mobile implementations are using ipv6 privacy extensions by default to ensure you get a random GUA every day.
My network is dual stack and I connect mostly over ipv6 to all my internal clients using internal DNS. If my internal DNS is ever down I can fall back to ipv4 or it’s basically the one box on my network with an easy to remember ULA.
Super cool!!
Chmod +t
And then chown root
The irony isn’t lost on me but the comments show it wasn’t that simple. If it was they surely would have done it.
It doesn’t really surprise me that a self hosted project cant afford to self host it’s own self or be able to find a neutral hosting location.
I don’t use linux on desktop anymore but that seems like a major step backwards from 10 years ago where your worst worry for running multiple DEs was the bloat from having to run GTK and QT in a mixed environment.
Not patching the 3000 series seems like a big mistake because it was so popular. There’s gotta be lots of those chips out in the wild. It’s also a 5 year old chip. So I get not being able to go that far back.
Can anyone just release a chip without massive security flaws these days?