

Doesn’t happen with Antergos either.
I mean, I’ve gotten a NXDomain error ever since they shut down, but at least it’s not a certificate expiry!


Doesn’t happen with Antergos either.
I mean, I’ve gotten a NXDomain error ever since they shut down, but at least it’s not a certificate expiry!


At one point in time, I was obsessed with getting a Thinkpad to the lowest power consumption possible.
I think I managed to drop it down to ~3w, with the screen and radio fully disabled.


Well who needs systrays anyways? While we’re at it, let’s remove theming support too! Surely nobody would miss that feature?
I really miss KDE. Sadly my experience with new major versions (5, 6) tends to be that plasma is unstable for daily use for at least a year or two. I’ll be back once things settle down a bit.


I’m not moving around from one point to another. I am simply stating that a majority of home users do not need the reliability and operate off of larger tolerances. Reliability costs money. If you need it, good for you. But a majority of people (including those in tech) do not need it, otherwise we’d all be on infiniband and ditching Ethernet by now. There is nothing wrong with a wireless transport, beam forming tech has come a long way to minimize interference, and direct point to point wireless IS faster than underground fiber with no retransmissions.
I’ve been in networking research for more than half a decade now, spanning from various forms of wireless (RFID, LoRA, wifi, 4G, 5G, etc) to wired Ethernet (1Gbps, 100Gbps, 800Gbps), at both the transport level and protocol level (Ethernet, IP, NDN, RoCE, TCP, QUIC, BGP). I’ve taught courses on how these things work. Before that, I was in IT networking for 4 years. From what we’ve seen, no matter how good you say they are, ISP and carrier operators inevitably screw it up on the configuration end (because they are human). BGP, NAT, 5G mobility are all a buggy mess because of this. When it comes to deploying new tech, corners are always cut and it comes back to bite people in the end. Wireless transport is fine, it’s human error that plagues both wired and wireless tech.
Shortwave for trading isn’t some “legacy shit”, it’s where industry and research is headed in the last decade. Your dismissal of new technology and skills is indicative of what this argument has been about: you start from your conclusion and dismiss all evidence before you even think. Issuing blanket statements that are too broad in scope. Everything I said has been quantified with specific assumptions and conditions.


You’re still missing my point. What type of application are you running at home that requires that level of SLA? If you are somehow running something that has that type of reliability/QoS constraints, how can you guarantee that your residential ISP with a fiber connection isn’t oversubscribing the links, causing the same sorts of periodic service disruption outside of the end user’s control?
I see no reasonable situation where user experience for home applications would degrade over wireless any more than bgp policy misconfigurations or congested links would. Especially when Spectrum drops packets to NTT almost every Monday night.
As a side note, high frequency trading uses shortwave instead of fiber for transferring data due to latency reasons. There is nothing saying wireless is always worse in latency than fiber. But that’s no longer in the realm of home use, so I don’t really think it matters.


I’ve mentioned plenty of times under ideal conditions. If the condition is as you say (where there is known massive interference) I’d say that’s a good indicator to either 1. figure out what the interference is and whether it’s possible to mitigate it or 2. Switch to a hard link. This is very much the right tool for the right place problem.
For a majority of users wireless is definitely sufficient and that they can tolerate a reasonable amount of disconnects/drops/latency spikes. I’m not saying for every scenario wireless is a good substitute, but it can definitely handle certain scenarios good enough for home users for a fraction of the cost.
Besides, if I’m not having any major sources of interference now but somehow that develops later, that’s no different than getting a congested link at peek hours, or a faulty switch somewhere along the path 2 years down the line. It’s just another form of network disruption, those can develop in the same way in hard links.
Side note: I’ve done work over ssh and webapps with a constant 200-500ms latency and periodic disconnects for prolonged (months) periods of time. It is absolutely usable though a bit slow. I’ve even played PvP in MMOs (SWTOR, ESO) with those network stats back in the day and still managed to do well enough. People overestimate the quality of Internet service they need all the time.


They were checking against a whitelist of IMEIs to force people to migrate to 5G phones. While my new phone was 5G, it was acquired internationally and thus not on the whitelist. So as soon as it got on the network, the line got terminated.


I agree LEO Sat is different from 60GHz. But the detrimental effects of wireless is completely overblown. People running into issues should just run a signal test first to make sure it’s not their setup that’s the problem.
There is no such thing as weather in SoCal (other than that one week of continuous rain each year).
If you are just looking at 4 9s or 3 9s latency while the link is not saturated, it’s fine for general use (assuming my first bullet point holds). It’s not like I’m running aws off of my home network.
Even in the rain, the latency is mostly fine. It’s usually just the minute it starts raining that the latency goes through the roof. My assumption is that it’s sampling and adjusting the modulation/coding scheme.


I don’t run starlink, but I run Starry (fixed point wireless) when AT&T and Spectrum are available because:


Sorry, but the fungus has been burping and slurping on radiation.
This came up last time the cert expired iirc.
Tl;dr one of the founders is holding up the infra not allowing any change. According to someone who worked on Manjaro, it was trivially easy to get this fixed, but that single person simply wouldn’t approve it. Last I checked they sent the founder an ultimatum: either hand over the project or see the staff walk. I suppose the staff walked.