The provider can upgrade their network from GPON to XGS-PON; in fact KPN (a large Dutch provider) does this regularly, especially in areas with new housing developments.
> The provider can upgrade their network from GPON to XGS-PON
The provider can transparently run GPON and XGS-PON simultaniously because they run on different wavelengths. However unless the provider can tell all existing GPON customers to replace their infrastructure they cannot stop providing GPON. GPON -> XGS-PON is not an upgrade, it's double the infrastructure where the splitter is.
So my question is quite specifically if there is a contractual way for KPN to turn off GPON and force customers to migrate, or if they are required to service both until the last GPON customer goes away on a splitter.
This has been an issue with DOCSIS for in many places of the world where we are already running out of available frequency spectrum.
KPN and other Dutch ISPs don't really care about custom customer hardware, on a practical level and on a contractual level. The Dutch standard is that you use the rented hardware your ISP provides, unless you want something special, then you get specs and settings and you're on your own. Even if you use your own hardware, you often still get a modem delivered to your doorstep.
If anything breaks on the network side, the troubleshooting procedure is "connect the hardware we sent you and see if it works". If it does, it's up to you to fix your side. If that requires new hardware, you're kind of screwed. KPN has the obligation to permit you to run your own hardware and to provide you with the information necessary, but not to keep any kind of backwards compatibility.
(Euro)DOCSIS should be backwards compatible, but things like radio channels and unencrypted video signals have already been replaced by their digital equivalents to add more upstream capacity by Ziggo (the last remaining large Dutch cable company). This broke functionality for a whole bunch of devices, but these changes were announced months in advance so customers had to choose between ending their contract and taking it.
The trouble with dealing with KPN is that KPN is also the company operating the POPs in most places, with many other ISPs leasing their lines. So even if you switch to a different ISP in protest of the XGS-PON switch, you're very likely to still end up with a XGS-PON signal from KPN.
You're almost certain to end up with the exact same line just a different provider on it. Very few areas have multiple fiber networks, although it's getting more common.
I still believe that the original move, forcing KPN and other network owners to allow competitors on their network, was a better option than digging up the streets twice to get two fiber networks in place.
Consumer contracts don't guarantee GPON support in any way. So if KPN wants to upgrade they can just send the customer a letter telling them to get an XGS-PON compatible ONT by some date.
They'll probably take a bit more customer friendly approach and at least send you a free provider owned XGS-PON compatible one and a new modem. But for your own equipment you have to manage everything and make sure it complies with their published specifications.
That sounds like a somewhat pragmatic approach. Curious to see how that plays out in practice. I presume the total number of consumers that are interested in running their own ONT is limited. In Germany the situation seems a bit different. There customer owned Fritzbox devices with integrated ONTs are very widespread making the situation for an ISP quite different when it comes to upgrades.
Sure, but even with the fritzbox situation all ISPs also offer dedicated ONTs as free rental or for 40€ as purchase. Some, e.g. Telekom, also offer SFP ONTs (Digitalisierungsbox Glasfasermodem)
We're using Gotenberg[1] to convert a rendered web page (with Elixir/Phoenix, in our case) to PDF. Works like a charm and we can use our existing frontend code/styling (including SVG graph generators) which is a huge bonus.
We actually experimented with Gotenberg! Ultimately it is a layer on top of Chromium for conversion and we were dissatisfied with the results. I am curious so as to how are you handling assets and other static media / attachments: do you embed everything in a single HTML file or do you use some kind of bucketing system to resolve URLs?
Great question! We actually just use the static assets (stylesheets, images) from our public asset CDN. The generated HTML points to the latest version of those assets, which means we can always use all the latest styling/assets in our generated PDF files.
It's due to the narcotic effects of nitrogen that GUE (Global Underwater Explorers, a diving association rooted in tech/cave diving) uses EAN32 (32% oxygen) as their standard breathing gas.
They're also more conservative in their recreational diving depths: 30m (100ft) is the recreational limit, beyond that technical certification and a helium-based breathing gas (e.g. Trimix) are required.
I think you misunderstood the GUE standards. Nitrox isn't significant less narcotic than air. They set a 100 ft equivalent narcotic depth maximum limit somewhat arbitrarily because empirically that seems to be pretty safe. Below that depth we add progressively more helium to the mix to limit narcosis as well as gas density (work of breathing).
That was an amazing set. The first one I bought from my own hard-saved cash as a kid. Really fun to build and amazing (and informative) to see the working steering, differential, suspension, and gear train assemblies.
I have this set laying around, mostly complete. Should really rebuild it someday!
While most monitors these days have some protection built in to combat burn in, I believe it's still an issue, yes. It's why Monitors Unboxed (a brilliant YouTube channel, by the way) doesn't recommend[1] using an OLED monitor like the Asus ROG Swift PG42UQ for productivity work.
Ha, this bit me a few weeks ago. Almost went back to the store with the Duracell batteries, thinking they were empty on arrival because none of them worked in any of my AirTags, until I found out the bittering agent was the problem.
reply