lots of low end switches use RTL837x series as basis nowadays
HN user
tepmoc
its basically AISC plus microcontroller - https://svanheule.net/switches/rtl8370
I love https, but I also hate that its basically killed on-site caching and give CDNs more power as its only way to distribute content closer to user
First time, eh? I remeber namecheap had problems 10 years ago when they upgraded interface and something was wrong with dns srv records. So i had to move out to gandi at time
eh, you can just add search domain via dhcp or static configuration and just type out http://mything/ no need to enter whole domain unless you need todo ssl
Diameter in mobile network is heavy user of SCTP, but from what I've read they moving away from diameter into HTTP calls for 6G.
As previous owner of Archer C7, Archer AX23 barely upgrade if you want to install additional packages as it have same 16/128 flash/memory configuration just like C7.
Personally I upgraded to xiaomi Router AX3200 with 128/256 flash memory configuration and 4:4 MIMO, though it lacks USB and have WAN+3LAN ports compare to usual WAN+4LAN.
residential - not many. Corporate on other hand is different story, thus why happy eyeballs for transport still would needed to gradual rollout anyway.
SCTP still have some donwsides it has to resolve https://http3-explained.haxx.se/en/why-quic/why-tcpudp#why-n...
Plus we need happy eyeballs for transport if SCTP run over IP and not encapuslated https://datatracker.ietf.org/doc/html/draft-grinnemo-taps-he
But IPv4 pretty much non-workable since most end-users behind NAT and there no known implementation to work around that.
SCTP works fine on internet, as long your egress is comming from public IP and you don't perform NAT. So in case IPv6 its non issue at all unless you sit behind middle boxes.
Probably best approuch would be is like happy eye balls but for transport. https://datatracker.ietf.org/doc/html/draft-grinnemo-taps-he
WinUI essentially webpage
in 2015 they had 3500 limit for everyone and 6 was only for partners, nowadays its 6Mbps for everyone and 8Mbps for partners.
You treat ipv6 /64 just like /32 in ipv4
bitcoin [lighting] is privacy nightmare
you can lookup domain count for TLDs here https://deployment.rdap.org/ (sorting works)
Asssited GPS[1] solved that exactly problem, since not network connected GPS devices need download GPS almanac and ephemerides via GPS 50bits/s connection, which can take a while.
Nowadays i found that watt per fps is better metric. And nvida is just milking performance by power draw more current (less efficient)
I actually did same just couple months ago, 980ti->3070. Though TDP claimed to be 220 but depend on vendor it seem it can peak to 250. Also one thing i liked after upgrade that 3070 have fan off when you aren't have load on it like desktop apps.
Well now I have to carry this additional junk all time, plus this just create additional waste for no reason at all. as people will break and throw away them eventually
https://github.com/priestc/Autotip
was nice back in days when fee was low
16:9 fine for desktop displays where its usually large diagonals, but on 15' or smaller is kinda lose too much vertical space.
Anyway is about personal choice and currently there isn't much choice for 3:2 laptops for reasonable price/specs
Last argument I heard in chrome bugtracker it was - doing additional dns lookup slowdown user experience, which is why they abandoned idea adding it
200K antminter S9 will produce about 50% hashrate of current bitcoin network that cost about 300M$ not counting electricity (200MW). But that means they have to R&D themselves these chips if they want attack quick. Otherwise they won't getting that much hashpower in one piece.
If they decide slowly enter game, attack price will raise significantly since network difficulty will be adjusted as they will add more of their miners into network and their projected 50% hashrate will be just 25%
So realistically its about 1 billion $ to attack current bitcoin network.
Here recent detailed answer from Nick
https://meta.stackoverflow.com/questions/348223/stack-overfl...
SCTP droped 100% time as there no proper PNAT available for it. To make traction other protocols there need "happy eyeballs for transport" so it can be transparent for end-users
SCTP can't go through NAT (there is ietf draft in works for that). But SCTP already exist in your favorite browser Chrome, Firefox both use usrsctplib (https://github.com/sctplab/usrsctp) to provide sctp over udp for webrtc signaling.
But there also need to be sctp over udp over dtls (or just sctp over dtls) happen as you can't use TLS with SCTP unordered mode or multihoming.
SCTP slowly gain traction in userspace besides being only in mobile operator networks (lte)