HNHacker News
TopNewBestAskShowJobs

unquietwiki

175 karma · joined September 17, 2020

Website: https://unquietwiki.com/

IT Pro & Casual Geek

submissionscomments
unquietwiki··on DragonFly BSD 6.4
I used it to help recover a messed-up Linux instance, copying files over with either Samba or NFS; think NFS kept messing up. But yeah, it'll work as a Windows-friendly file server!
unquietwiki··on 26 Programming Languages in 25 Days
That's really cool. It's basically a good way to practice multiple languages to see what you might like; and without an Advent of Code, I've used over 20 languages myself. I'm sad Nim wasn't on his list: I've started using that lately, and find it to be useful.
unquietwiki··on Soyuz module on International Space Station is leaking something
Given https://arstechnica.com/science/2022/12/space-debris-expert-... came out earlier today, it could very well be mechanical, or debris induced. Planned spacewalk is cancelled; be curious to see how the situation evolves (might have to sit tight for a new ride, unless they can put more coolant back in).

Youtube has a livestream from NASA: https://www.youtube.com/watch?v=21X5lGlDOfg

unquietwiki··on Alt-Enter doesn’t Window DOS graphics in XP, but worked in NT and Win2000 (2006)
Why did I just read a 17-yo post about XP & DOS incompatibility; on a newsgroup archive that seems curated to alt-right viewership?

https://reactos.org/ implements Windows roughly akin to 2003; dunno if that would be able to re-create this issue, but might be worth trying?

unquietwiki··on Alt-Enter doesn’t Window DOS graphics in XP, but worked in NT and Win2000 (2006)
https://en.wikipedia.org/wiki/DriveSpace

There was a patent lawsuit in the 90s about drive compression software in DOS 6.2. It was yanked in .21, and re-added in .22 with some changes.

unquietwiki··on Tell HN: IPv6-only still pretty much unusable
Windows Vista came out in 2007, and it explicitly had a dual-stack IPv4+IPv6 implementation. Around that same time, the BSDs were finishing up KAME, and Linux support was decently mature. That was 15 years ago. Software and OS-wise; with the exception of some features of Mikrotik routers + managed Meraki & Ubiquiti stuff just now getting onboard; the support is there. Node's using it properly now. I was able to update Pidgin to use it 10+ years ago. So I think we've got the software-side long figured out; we just needed to get the damn vendors on-board.

I'm glad we agree on NAT sucking. Though given a lot of ISPs are doing DHCPv6 without fixed net-ranges to clients; a work environment does benefit from having ULAs still; sometimes even with NAT66. Performance & security-wise, IPv6 still wins that battle: most routers disable automatic inbound traffic, and you can pinhole traffic directly between hosts.

unquietwiki··on Tell HN: IPv6-only still pretty much unusable
I think if you're using the Meinberg NTP client on Windows, or chrony on Linux, that's feasible. Older systems may prefer to snag it from DHCP: which probably would only do IPv4 anyway.
unquietwiki··on Tell HN: IPv6-only still pretty much unusable
I think HE's been begging to peer to Cogent for years now. I've even seen cakes posted online.
unquietwiki··on Tell HN: IPv6-only still pretty much unusable
You might appreciate this. Basically, it leverages Babel routing to bridge IPv4 with IPv6.

https://datatracker.ietf.org/doc/rfc9229/

unquietwiki··on Tell HN: IPv6-only still pretty much unusable
Hey all... unquietwiki from r/ipv6; been lead-mod there for a while now (though the rest of the folks are really amazing on the mod-side).

IPv6 has saved my bacon more times in the past 15 years, than IPv4 has fought with me. No clashing of IPv4 ranges. No fighting with NAT. Ability to easily have concurrent networks, for different purposes. Ability to assign multiple network addresses. Internally, it "just works" on basically anything not an older licensing server, or LAN game. Microsoft is using it internally. Apple has been mandating MacOS and iOS apps to support it for several years now. Usage over the Internet is exceeding 50% in major countries.

Where it falls short... a lot of ISPs use equipment that don't handle it well, and/or don't have the staff to implement it properly; and the ISP buyouts and mergers here in the US of the past 15-20 years REALLY messed up the timeline on adoption. Cloud services, a lot of the stuff Google & Microsoft built up their public offerings on, they were designed largely on older virtualization setups that precluded how IPv6 works, until recently; same goes for Docker & Kubernetes. A lot of VPS hosts support it just fine; but a lot of businesses aren't leveraging those, as they could be. And lastly... a lot of IT guys still don't care for IPv6; as those biases show up in these & on Reddit; so that perpetuates the cycle.

← PreviousPage 3 of 3