You can use the JSON-LD for your movie reviews even if you're not a big site. I use it on my site for reviews (books, games, movies) and it seems to show up in most search engines with the star rating etc.
That said, I don’t think that works well in a single centralized forge today either. Usually you still need A to actually make a release with the fix, which isn’t tracked by the issue/PR system.
I'm not sure. On GitHub I see plenty of bug reports which say "this is broken" with references to other repos. Those backlins are useful when someone does figure out the fix.
That said, I'm very much in favour of people and projects moving away from GitHub.
I used to work at two (UK) telcos. There's a historic reason and a modern reason.
The historic reason was, just like the Internet, the international phone network was built on gentlemen agreements by engineers who largely trusted each other.
A big national telco is unlikely to attack its peers, so there was little need for safety measures. As smaller telcos came in to the mix via deregulation, that understanding changed - but it was hard to retroactively fit controls.
The more modern reason is outsourced call centres. You want outbound calls from your Philippines based staff to show as if they were calling from a local number. When large and reputable entities were doing this it was fine. Just like showing a different reply-to address on an email.
If you were designing a modern network, it wouldn't be like this. But international telephony is over a hundred years old and has a huge amount of legacy technology and legal agreements.
> You want outbound calls from your Philippines based staff to show as if they were calling from a local number.
The company that has offshored it's support to the Philippines might want that, but I doubt any consumers want that. That shouldn't have happened, but regulation comes (20+ years?) after harmful business profit decisions have been made and implemented.
But, thank you for the explanation. I have heard similar explanations before, and it has always sounded to me like a situation where the telcos are able to offer a service for a profit for the customers to hide the origin of their offshore call centres (that mostly nobody wants to speak to anyway).
The consumers 'want' it because if they get disconnected and try to recall, by spoofing a local number it costs them nothing/little since it's a local number (maybe toll-free?) instead of a lot for an international call. Of course, they might want a local call centre even more, but spoofing a local number for overseas call centres does have a purpose.
> I've never seen an hotline where you can call back and resume the call you were doing.
Assuming they even accept inbound calls to the CLI number in the first place.
I frequently encounter companies where I miss a call due to $reason, I then try to call back the CLI number and it just says "This was $megacorp trying to call you, we will try again later".
Or, if you're really lucky, the CLI will just dump you into IVR-hell which, of course, is "AI powered" today, so you have to spend 30 minutes telling the stupid robot they mis-intepreted your voice.
My electric company gave me a number (UID, not phone number) to resume a call if the issue wasn't fixed within 24 hours, and I'm pretty sure internet operators have the same protocol (at least used to).
Can literally be a "Desk ID" basically, so using that would reach the phone next to the agent. Used to work both with outgoing cold calls and incoming customer support, had a setup that worked like that for the latter.
> My electric company gave me a number (UID, not phone number) to resume a call if the issue wasn't fixed within 24 hours
What planet do you live on ?
Seriously. Where I am it is guaranteed that a utility company would never even consider such a concept let alone have the technical competence to actually implement it.
Enedis is basically a state owned company (to be clear, they aren't the one selling electricity, they are the one in charge of the network and the distribution, so I'm not sure if it counts as utility).
The call centre for my Australian bank's KYC is seemingly backed by a single person. I've spoken to her a few times now... so calling them back more or less does work, though you might have to wait on hold again.
A legitimate company registering an local number, routing its Philippines call centre through it and accountable for outbound calls is not really comparable with a random scammer faking whatever number.
Just looking at my incoming call list on my phone for yesterday: "Suspected Spam", "Suspected Spam", "Suspected Spam", "Potential Fraud", "Suspected Spam", "Suspected Spam", a real call, "Suspected Spam", "Suspected Spam"...
Phone is set to only notify me for numbers for known contacts - does mean that I occasionally miss calls from other people, but I can live with that.
Yes, was just relating my experience - it's just go the the point where I personally opt to play safe. Like everyone I do get calls from people who aren't in my contact list but it was getting silly so I've defaulted to ignoring them and it works for me. Anyone serious is going to be happy leaving a message - which suits me anyway as I spend a large part of my work day in Teams calls.
In the last 3 months I received 700 spam/scam calls to my phone, my wife received about 400. We can't turn off ringing for unknown callers and we're getting mad. A few days ago I vented to one of those call-center people trying to sell me a cheaper power utility for the Nth time, and told her to find another job or something like that; she actually called me back yelling at me that "any job is worth", and yelled at her that I cannot fucking receive sometimes up to 20 calls in a day, sometimes at quite annoying times of the day! It's getting ridiculous.
EDIT: I know not everybody is having the same experience in my country. Some people are only getting a few calls per week; I registered our phones in https://registrodelleopposizioni.it/ and also I'm using android's spam filter which filters out additional hundreds of calls automatically.
EDIT 2: I sometimes wonder if we're being harassed by somebody ; I cannot tell. The voices are often quite similar, but it might be the albanian accent that makes them sound similar.
> I vented to one of those call-center people trying to sell me a cheaper power utility for the Nth time, and told her to find another job or something like that
I threaten to kill and rape them all the time, but that usually doesn't do much.
I've found that politely asking them to kill themselves elicits much more engagement, and I hope it at least implants some lasting memory.
> You want outbound calls from your Philippines based staff to show as if they were calling from a local number.
This is a valid use case, but I’m a bit surprised that the mechanism isn’t better controlled. Surely a better design would be for an actual local entity to forward the call, possibly with an optimization to allow the voice data to bypass the local entity once the call is connected.
Just whitelist the caller ID and have the originating network guarantor
The second part is the hard part and requires coordination
It wouldn’t be expensive or especially hard to do but there is no payoff for the network. Remember they make money off scam calls too
Since as long as I can remember these organisations have been optimised for profit, not for GAF and that’s why they’re being savaged by regulation and OTT competitors now
There has been no market forces compelling them to do this and until recently when it got really bad, no political or regulatory forces
> The more modern reason is outsourced call centres. You want outbound calls from your Philippines based staff to show as if they were calling from a local number. When large and reputable entities were doing this it was fine. Just like showing a different reply-to address on an email.
For this particular case, do they really spoof the caller ID on an (expensive) international phone call, or do they actually just re-route via a local phone number?
It's been a while since I did telecoms related stuff but also you might want a different CLI and ANI for forwarded calls so you can preserve the original line being used.
Obviously the whole scam call centre has changed how it has to work but we actually had a working system that had quite a few useful features.
It's a solved problem. VoIP plus leased trunk lines by the a telco in the market you want to work at. You are limited to fixed set of numbers and you are "local" in the market you want to work at.
I've basically stopped buying any portable electronics unless they take USB-C.
Currently travelling with a laptop, watch, toothbrush, eReader, camera, bug-bite treater, and phone - all charging from the same power brick.
I'm guaranteed of getting a replacement cable / charger wherever I am in the world if I need it.
The only slight snag is some cheaper itema refuse to use PD and insist on plain 5V/2A - buy most decent travel chargers have NON-PD ports.
Amusingly, most of the buses I've taken recently also have USB-C ports on them for ad hoc charging. Perhaps one day EVs will use USB-PD-Max rather than CCS :-)
I've also returned a few USB devices that ship with a USB-A to USB-C cable and ONLY charge in that mode, they also MUST charge with USB-C PD.
The two so far were a therapy light and some Zippo hand warmers. Like, who in the hell would design a device that has a USB-C port on it where only a fraction of chargers will work on it. It feels even worse than proprietary charges, because you see a USB-C port on it and think, oh I have a plug that fits it, and then it doesn't F**ing work. Idiot engineering/product teams, making the world suck with their falsely advertised USB-C ports. If anyone of you are on a team that ever makes this decision, just know that it is a stupid decision, and jump ship when you can.
The thing is, making a 5v-only device PD-compliant is literally one resistor. It costs well under a penny.
It's pure ignorance, not a decision, but the lack of one. Lack of caring, lack of having an actual engineer involved, just slapping an oval-shaped port into a product where a trapezoidal port had been, and blindly thinking that magically makes it spec-compliant.
Or not thinking about the spec at all.
I return these devices too. Lots of them. My e-commerce returns over the last year are probably 50% PD non-compliance, 50% all other defects combined.
It's two resistors, actually. But they cost $0.0003 each (that's 0.03¢, or just around 3,333 of them for US$1) from distributors. Though there appears to be a bit of a stock crunch right now.
So... yeah.
The bigger issue is not really the parts cost, it's the fact that it adds an extra part to the design that has to be purchased and tracked and assembled and blah blah blah. This is the real reason it often gets left off on the bottom-of-the-barrel products. Many times there is no other use for a 5.1kΩ resistor. And it might not even fit well at the cheap sizes (0603 or 0402), and going down to 0201-capable assembly factory flow just for these two resistors is not going to happen.
These companies are not manufacturing the device PCBAs, that is done by dedicated companies such as Flex. The PCBA manufacturing companies have warehouses of different resistors, and 5.1kΩ is extremely common. In fact, most PCB resistor values are quite flexible, to save on SKUs (in practice, to save on loading another carrier on the PnP machine) often if a specific resistor needs a specific value then all (or most of) the other resistors will use that value.
I was speaking a little more towards the AliExpress end of things, which is a sadly high proportion of the devices out there. For the midsize CMs and up, you're right, they've got piles and piles of stuff and don't charge by the reel loaded.
5.1k is a surprising resistor value, a lot of modern designs don't really have anything else in that area. I'm often not able to combine anything with it when I'm cost reducing. 4.7k, sure, but there aren't a lot of those either... 2.2k is just not close enough a lot of the time (or ends up as 1k), and same for 10k. So, sadly, it often does stand alone.
5.1k is about the middle of the generic "some kind of pullup" range of 1k-10k, so it's a perfectly fine option for strapping resistors or for a non-critical I2C bus.
4.7k would of course have been better because it's an E6 value (+-20 via the spec) rather than E24, but it's still a value I would expect any PCBA house to have in stock at all times.
But I agree, 1k or 10k would be the obvious no-brainer. I reckon there's probably a technical reason for it, as it does act as a voltage divider together with the Sink pullup, so perhaps there are some restrictions there with the multiple values it needs to distinguish.
The 4.7k "default pullup" is an old-school 5V TTL thing. It works really well for TTL inputs. But CMOS inputs don't really care very much, especially if they aren't toggling or if there's a bit of hysteresis on the input stage (which there often, but not always, is). There seem to be 10k resistors in every design so CMOS pullups often end up at 10k. If power savings are a concern, especially if you need a tie-off more so than a pull resistor, 10k-100k is a perfectly valid range, and I've even used 1M in extreme circumstances.
Usually 5k is a little too weak for I²C. Rule of thumb is that you want to be around 1mA, so for a 3.3V system you start at 3.3k. Generally 1.8k to 3.3k ends up being a pretty common range. More current is usually better than less current, so even at 5V where 4.7k might be OK (if you're even at 5V Vdd these days), going stronger is often a good idea. If power savings is a concern, or if timing's somehow important (did you find another touchy badly behaved I²C device? say it isn't so!) then it might be time to break out the active pullup structures (mostly current source type things). Once this is done and tested it tends to get fossilized, for good reason, so this one won't usually get swept up in a standard-effort cost reduction pass.
There's an otherwise decent shortwave radio out there that was originally charged with a micro-usb, then they released a "new" USB-C model...except it will only charge with a 5V brick because they literally just swapped out the ports. Really annoying.
You mean the CountyComm? If so, I'm 99% certain that radio is a rebranded Tecsun PL-360, which is in fact a 5V. I love Tecsun, but why they would cheap out on the USB-C refresh is beyond me.
Is there not enough room for a through-hole resistor to just hang out in the air? Most devices I've opened seem to have more than enough room, so long as one is skilled enough with the small chisel tip.
Yeah, it's a significantly trickier proposition when the pads aren't there.
The contacts are in the connector, you just need to bring them out and get the resistor on them, which is frankly a pain I shouldn't have to endure when USB-C has been out for 12 years. None of this is rocket science, the manufacturers just aren't feeling the pain.
Only if the device's consumption is < 2.5W, which is what a USB 2.0 computer USB-A's data port limit is. Anything above that, compliance gets a bit more involved and complicated.
It's certainly not easier. Type-c power sink can advertise USB default, 1.5A or 3A easily. USB default is not necessarily underpowered. You still have to use BC1.2 to see if the source is actually underpowered.
If you're just a microUSB device, you'll also check based on BC1.2. And you can ignore CC/Rp check. It's actually simpler.
I guess you can assume anything advertising itself as USB default is underpowered, but then you'd be wrong.
It sure is. You can just spec it to require a USB-C 7.5W/15W source and then you can gate the operation behind a simple analog circuit and Bob's your uncle. No such way with microUSB until you implement BC1.2, which you don't have to support with USB-C (though it's certainly nice when you do).
> but then you'd be wrong
Not at all, it would just miss signaling it's not compatible with, just like with all sorts of proprietary signaling protocols out there. The point is that with microUSB you have no other way, you have to implement BC1.2 (or some proprietary spec) which is often more complex than a comparator on CC line.
Yes, that way your type-c device will also be refusing to work with many sources that can provide enough power, that is with anything advertising USB default power.
For proper detection of actually underpowered source without awful lot of false negative results, you always need BC1.2. You're just adding type-c CC pins circuitry on top maybe to detect what power is availabe in non-default-usb-power scenarios. If you just use CC pins for detection, a lot of your users will not like you, and will not understand why they can't charge your type-c port featuring smartphone or whatever with a perfectly capable 2.1A/5V charger connected via USB A-C cable.
Yes, that's all true. It's also irrelevant, as USB-C devices aren't required to support BC1.2, and the same concern applies to any proprietary signaling method you won't handle. "This thing requires 15W USB-C power source" is easily understood, regardless of existence of >=15W USB-A power bricks using QC3.0 or whatever else.
Supporting BC1.2 in a smartphone won't make it any more complex than it already is (been there done that). We're talking about simple equipment here, where handling USB-C power correctly can be easily done without any ICs.
> I've also returned a few USB devices that ship with a USB-A to USB-C cable and ONLY charge in that mode...
By "that mode", do you mean "1.5A @ 5V" permitted by BC, or do you mean "3A @ 20V" permitted by non-type-C PD?
> Like, who in the hell would design a device that has a USB-C port on it where only a fraction of chargers will work on it.
Who in the hell would design a charger that can do Type-C PD but can't do either pre-Type-C PD or BC? Does the charger in question also shit the bed when a USB 1.0 device attempts to draw 100mA @ 5V? I hope not! Were it me, I'd return that crappy thing for a refund.
> By "that mode", do you mean "1.5A @ 5V" permitted by BC
Neither - OP means devices with missing CC resistors which will fail to charge with a compliant PD source. (The A-to-C cable works because it provides 5V Vbus unconditionally.)
That's close, but it's not quite complete. There seems to be lots of confusion here, and that's natural: It is confusing.
For just-getting-power from a USB A port into a USB C peripheral: There are supposed to be 2 resistors in the peripheral device [always], and also 1 resistor within the cable for USB-to-legacy cables[1]. That's 3 resistors, total, to get a relatively dumb USB-C equipped peripheral device to reliably charge from both USB A and USB C hosts/chargers/whatevers:
The cable itself: It gets an internal 56k pullup resistor between Vbus and USB C pin A5 -- which is the CC line [yes singular]). This resistor signifies the capabilities of the host/charger/whatever for devices that care (some do care, some do not care).
The peripheral: This minimally needs two pulldown resistors [commonly 5.1k], between each of CC1 and CC2 [yes a plurality] and ground[2]. This tells a compliant USB C host/charger/whatever "It's OK! Send the juice juice!" regardless of connector orientation.
[bleh]: Again, it is a confusing thing. Nobody said that dealing with such flexible, ambidextrous connections would be simple. CC performs a lot of different tasks: It can be a bidirectional serial bus for active PD negotiations, and/or a resistor network for passively dealing with power, and it's the bit that performs detection of cable orientation for applications where that matters, and it probably does other stuff too.
That single little wire is clever AF. It'd be simpler to use multiple wires instead of just one, but that would take more copper. Copper is expensive, and we each save a tiny bit of money (or a large pile of money globally) by using less copper instead of more of it.
My point, which matches what you've written out in more detail, is that there's supposed to be stuff (resistors) in the cable, stuff which is often not there. There are plenty of these abhorrent cables in the wild. And when you come across one, things get weird, because some sources and sinks deviate from the standard in ways that make them work with these bad cables. Others don't do that. (I believe there were a lot more abhorrent cables in the early days, and thus began the chain of accommodation....)
So unless your cable is known-good, if you are having trouble, trying a different cable should be the first thing you do. It really does often get things working.
Contrarily, if you have identified a naughty cable, it should be immediately widlarized.
Resistors don't go in the cable. They go in the device. They indicate that the device can't negotiate voltages above 5V, so just send 5V.
USB-A has no ability to provide voltages other than 5V, so there's no need for indicating it's the max.
Not all chargers have USB-A ports. Many laptops don't have USB-A ports, so if you want to charge a noncompliant device from a laptop it won't work. Or a laptop charger, which is dedicated USB-C.
I gathered that you knew that. I'm mostly just trying to complete the picture for those following along at home, who might find some of this resistor business to be a bit weird compared to the USBs of yore.
Except the old ways were weird in unseen ways, too. Some combinations of cable, phone, and charger worked well and some barely worked at all.
We're in much better shape with USB C and PD. It's generally a good, forward-looking way of doing all kinds of things.
I just wish the cables and ports were better-marked, and that manufacturers stopped fucking around by making non-compliant stuff, and that there were a clear way with two battery-equipped USB C devices to unequivocally declare that a particular one will charge the other (and not the other way 'round).
And yes: The non-compliant widgets should ideally be named, shamed, and Widlarized -- not simply tolerated or worked around.
A-C cable assembly always works, CC signal is connected within the cable to Vbus via 56kOhm resistor, but that's only relevant to the downstream port, not to the upstream USB-A power sourcing port which does not have access to the CC signal. Upstream port provides power unconditionally within some limits depending on port type (CDP/DCP/USB3.0/2.0 data port/...).
> Usually the best place to fix it is by getting rid of the bad cables. Usually.
No. There is no USB-C to C cable that will charge a badly implemented device with a standards compliant charger. That is the entire point.
An USB A to C cable is completely standards-compliant and safe, even if it always supplies 5V on the C end - any standards compliant USB-C device should not activate the MOSFET on its Vbus line unless it successfully negotiates via CC.
You may wish to re-read the type-c specification, especially 4.5.2.2.3.2:
"A USB 2.0 only Sink that doesn’t support accessories and is self-powered or requires only default power and does not support USB PD may transition directly to Attached.SNK when V BUS is detected."
or 4.5.2.2.5:
"A port that entered this state directly from Unattached.SNK due to detecting V BUS shall not determine orientation or availability of higher than Default USB Power and shall not use USB PD."
or 4.5.2.2.11.2:
"The port shall transition to Attached.SNK after tCCDebounce if or when V BUS is detected."
CC detection, let alone PD negotiation is not needed. You can draw up to 2.5W right away from Vbus and be standard compliant without wiring anything to CC signals.
Of course if you try this with a DRP device like a smartphone, you'll get no power. But that's not really an issue for type-c chargers or USB A-C cable assemblies.
They mean bad USB-A to C cables with no resistor on CC line. Of course this is broken junk which will work with some devices and won't with others. I've also seen cables with resistors on both CC lines, which is also broken but in a slightly subtler way.
But it’s not what anyone was talking about. Such a cable should be really quite rare because it’s unlikely to work at all in most situations, whereas devices with USB-C ports that don’t work with PD chargers (due to a cent’s worth of missing Rd resistors) are irritatingly common, because they do work with USB-C to A cables!
Huh? It seems clear to me that this is what exmadscientist was talking about, any other interpretation just doesn't make sense.
And no, such cables would still work in plenty of cases. You usually get them by having them bundled with devices they do work well with. In fact, they always work fine with the kind of devices you mention. These cables aren't as common as USB-C-shaped junk that's missing resistors on the receptacle, but I stumbled upon them anyway and I didn't really try to.
Right. That phrase "standards-compliant" in the above comments is doing a lot of heavy lifting.
A lot of devices are not actually standards-compliant. Some are close. (This may actually be worse.)
My experience has been that if the source and sink are broken, they are often hilariously badly broken and it is pretty easy to figure out that they are the problem, if not quite exactly what they've done wrong. But if things are flaky and weird and don't really make sense, it's probably the cable. Try a known-really-seriously-actually-standards-compliantly-good cable and many problems go away, even if the source and sink aren't perfect.
(Many sources and sinks aren't standards-compliant because, even though they easily could be, they're trying to work around the other end not being standards-compliant itself, because that's what you've got to do to sell a product. So they're close but not quite there. This is not always ideal.)
I'm hoping we'll see most e-bikes at least use 240W usb-c pd charging (I figure I have about a decade until I will wish I had some assist and buy one, so probably by then, they'll have gotten there...)
I also have assorted products that won't charge c-to-c (some from respectable manufacturers even, like Philips), but I see you can get little adapters with 5.1K resistor you plug into said crappy devices to cover that, I will have to try some out.
> The only slight snag is some cheaper itema refuse to use PD and insist on plain 5V/2A - buy most decent travel chargers have NON-PD ports.
Every PD port will handle non-PD USB-C consumers correctly, so not sure why would you care about non-PD ports. There is no "plain 5V/2A" in USB-C though, it's either plain USB (100/150/500/900mA depending on enumeration state), 1.5A or 3A. If you want to advertise exactly 5V/2A, you need PD.
I think what they mean is not PD related at all, but the fact some cheap junk has a broken USB-C setup where it's missing the resistor that signals a device has been plugged in and to turn on the 5v power. While USB-A just have 5v live at all times.
If you use a USB-A to C cable the device works because it results in a USB-C cable with an always active 5V.
I think you are confusing the devices with USB-C that require USB-A, and devices that charge the standard USB-C 5V/3A/15W. The USB-A ones cheaped out in including the resistors that signal legacy USB mode, they work with the ones in the cable or adapter.
Lots of people assume that USB-C always uses USB-PD, but the basic signalling is done with resistors. Lots of devices only need 15W, and it is better than USB-A charging. If you want faster charging, buy more powerful chargers.
For travel I have a bunch of cables with adapters on the end (choose usb-c, lightning, micro-usb). Can use usb-c, but have the ability to use the others.
It has helped out in a bunch of unexpected situations (usually someone else's device)
No need for a magnetic dongle. I literally shove a USB-C cable in there, charge for a couple of hours, then get a week+ of use. Does step count, notifactions, calls, etc.
There's more to the world than Apple and Android watches.
I have one and it's such a fantastic design. When I need to travel I just throw a tiny puck in my bag and it charges off the same brick that charges everything else I bring.
> Amusingly, most of the buses I've taken recently also have USB-C ports on them for ad hoc charging.
I've been pleasantly surprised recently when I plugged in my OnePlus into the bus in a medium/small Belgian city and saw the supervooc animation. (And it was actually fast charging, a 8 minute ride gave about 15% battery.)
For anyone wondering about technical details, PPS chargers now show up as supervooc apparently.
What toothbrush do you have? I've been looking for a USB-C charger for mine (standard Oral-B toothbrush) but the only ones I've found were from no-name Chinese brands and didn't work at all.
Yeah it uses a tiny ceramic heating element to heat the bite area up to uncomfortable temperature. It's supposed to denature the toxin and/or counter inflammation. Either way it does reduce moskito itchiness with me.
we are talking about a lightweight charging cable. you can carry more than one. boom, redundancy. being ideological about a cable connector is the nerdy equivalent of jony ive obsessing over macbook thinness.
Nah, being able to reduce to a single cable type is great.
The thing, it's not just about what cables you have at home, or even which ones you bring on a trip. It means if you go out on a trip with a small bag and a battery, you only ever really need one cable. It means you don't have to think about "which cables do I bring?", completely removing a question. That's really nice!
The number of times I went on a week-long vacation as a kid only to find out I didn't have just the right cable to charge my whatever-portable-entertainment thing was way too high. Oops, not the right cable for the portable DVD player. Oops, not the proprietary Gameboy SP adapter. Oops, not the right cable for the camera. Oops, not the right cable for the Genesis Nomad.
Forget that noise. Now its all one cable. Laptop, game console, phone, wireless headphones, reading device, even things like flashlights and lanterns. All one cable, can all work with the same extra battery packs and the same power cords.
Assuming your comment is only about proprietary cables that have usb a/c on the charger side, I tend to agree. Sometimes the device's form factor or function simply cannot accommodate usb-c without trade-offs.
I did lose my shaver's cable whilst travelling once, so I had to go to the barber to look presentable before a meeting. Not a big deal, but it goes to show that it happens. Had it been USB of any description, I could have bought one anywhere.
But then again I could have just as easily lost/broken the device itself and be in the same situation, so shrugs.
QoS is designed to minimise these issues by prioritising real time protocols and other latency-sensitive traffic over other traffic. But that doesn’t mean that slowdown isn’t happening.
With 500Mb you’ll be fine 99% of the time. But you don’t have a whole lot of spare head room. And I’ve found that I have dipped into that headroom a surprising amount (eg when I’d need to pull large docker images as part of a new build process I’m testing locally)
The point of Gigabit isn’t that IPTV is better quality, because it isn’t going to be. It’s so that you can get more done concurrently without depending on QoS to save your arse.
Also you made a comment elsewhere that WiFi speed would be less than gigabit but that’s not true. WiFi 6 (which was released 5 years ago) supports up to 10Gb/s. And WiFi 5 (802.11ac) can do up to 1300Mb/s and was released in 2013 (more than a decade ago!).
The Oculus Quest (original) supports 5GHz 802.11ac and in fact requires it for wireless streaming. I have noticed that games will download very fast on my Quest 2 over Gigabit internet too.
The author (me) does play games. I'm on PC, Oculus, and console. The console downloads are limited by the upstream. The VR games are limited by WiFi. I've never noticed the PC games getting close to the max download speed I have.
But, to go to your edit. Is there a significant difference between waiting 90 minutes and 45 minutes? Either way, you set the download going, grab some food, have a bath, whatever, right?
Not everyone plays the same games, play games in the same way, or has the same lifestyle as yous.
Just one example: If I find two hours on a weekday evening to play games (when I am often occupied by other things on other days) and I want to play the latest games, I don't want to spend 90 minutes waiting. If that window is gone, I need to move on.
(You could argue I could plan ahead, look up how large the game is, download it a day before blahblah. You'll be absolutely correct, but I can also assure you almost nobody does that. Network speed can be also very unstable/unpredictable.)
And I'm sure people who are on Game Pass would like a word with you.
This is surprising to me: I've seen Steam peak around 1500 on my connection. Linux ISOs from cloud mirrors (like DO) can hit closer to 2gbps. Bittorrent downloads of Ubuntu ISOs sometimes hit 2gbps
I think that is more so due to overhead in writing files and most likely also doing some live decompression or some other stuff. After all it does not download single file like iso would be.
It actually isn't all that different. A lot of modern games are basically a smallish exe and a single giant Assets file that's many many GB, and is some sort of encrypyted (or not) filesystem image.
Exactly this. ISPs are tricky players when it comes to peering. A typical symptom: servers in local region/country can easily saturate the connection, when anything external gets cropped down to 20-50% of a declared full speed.
Supply and demand, why would they bother improving the infrastructure if people can't use it? Either be an early adopter, and help progress or sit at the back and wait.
Google Jam Board (and other digital whiteboards) had high upfront capex and lowish opex. Probably close to the price for how often they were used before being killed off.
Same with the MS surface(?) tables (not tablets). I saw load of companies buy into the hype and then discard.
reply