My ISP publicly supports IPv6, but I've never gotten it to work properly, and none of the technical support I've been able to been forwarded to knows what's wrong either. Colleagues using the same ISP has the same problem, so doesn't seem to be an isolated incident.
I'm sure there are more people out there in the same situation.
If you look at the weekly profiles you'll notice that offices/companied are lagging behind private users. IT departments not willing to do anything. And IPv6 is used a lot on phones.
Oh no, the Godwin's law equivalent for networking is proving itself once again.
>someone will again complain about the address format, without realizing that shoving in extra address bits on an IPv4 datagram is already a new protocol
So you are having all the pains of transitioning to a new Internet Protocol, but none of the benefits of having an actually huge address space.
Do you really think your solution of "IPv4 with extra octets" will not introduce so called "broken everything"...?
Whether it's the addition of one octet or twelve octets, you are nevertheless introducing a new Internet Protocol, and therefore you are going to face the reality of introducing a new Internet Protocol.
To think otherwise is delusional and is the reason why the "Godwin's law of networking" has become sort of a meme.
For all of the bullshit that is Comcast and their ongoing mission to fully enshittify every single aspect of last-mile Internet delivery at the expense of consumers and taxpayers, I will say that at least they've had great IPv6 support for well over a decade at this point.
Yeah, I'm a Comcast customer and I'm very happy with their IPv6 support. The only things I would want different are a prefix larger than a /60 (say a /56), and the ability to have a permanently assigned prefix on my residential connection (but that's unlikely, I know). As evil as the Comcast business people are, their engineers clearly are trying to do right by customers.
Yeah, it's ridiculous. Specially when there are good or even better alternatives out there.
Postman was awesome back in the days, but now it's just slow, bloated and too complicated for 99.9% of use cases. It has become the Microsoft Word of API development platforms.
What we really need is a community-driven alternative without lock-in.
Many other use cases are covered by great FOSS products, but somehow API clients are abused as a sync cash cow:
(minor correction, Obsidian broke the 3rd party sync, not insomnia)
Point still stands.
I agree it's an annoying problem, but it's hard to see a way around it. The developers was that they need some way to fund development. Sync tends to be the up sell target since it's more for power users willing to pay.
There are quite a few open source Insomnia and Postman clones. Since most of them operate on config and workspaces, I think syncthing is good enough for this use case at least.
Bridge tournaments don't require the players to bring their own royal court to hold. Everyone gets to use cards proxying the various kings, provided by the tournament.
MTG tournaments become a test of playing skill, deck building skill, and the skill to have enough money to buy important limited production cards. It is what it is, but sometimes it feels gross.
In the sixties, hexavelent chromium was used as a rust inhibitor in cooling towers in a Hinkley PG&E compressor station. It caused ground water contamination affecting the health of many.
And then there is FATCA and CRS : when opening a bank account for my non-profit I had to answer 15 pages of questions related to me, other directors and the non-profit itself. I'm a non-US citizen outside of the US.
