I'd recommend everyone to familiarize how these forests were formed in the first place. They are not some natural thing, nor any ecologic sanctuaries. They are the result of immense postwar hubris and greed, draining ecologically precious and fragile wetlands to create poor (semi-)monoculture plantation forests whose only destiny ever was to get clearcut later.
Of course Google is (likely) still at fault here and should have managed this better, but it is important to understand the context also.
Tbh the .bg situation seems rather internal problem in Bulgaria rather than problem in the system. As the article mentions, governments definitely can get control of their tld if they want to, so the problem here seems to be that Bulgaria isn't interested.
Sure, but the final destination of the money flow is the same ICANN, which apparently need to give "Accreditations"/affiliation to the franchise. I remind you that the infrastructure is 100% European, this is purely idiotic from the European side.
That´s is not the point. The monopoly is the whole point. Would you pay tax to India or China because the sunlight shines in your country every day? Who owns the sun!
This whole case seems to hinge on the argument that .com domains somehow constitute their own market, instead of being just part of wider domain name market with plenty of competing registrys. That might prove difficult argument in court.
Afaik all pro audio standards more or less require ptp for timing, and that might add requirements for nics and switches? otoh the i210 nic, that is mentioned in the post, does have full (g)ptp/phc/tsn/etc support
That is sort of true, although it should be possible to take advantage of the resampler in PipeWire or JACK (zalsa_in/zalsa_out) to effectively get multiple interfaces in the same graph. I would expect some hit to the audio latency when going through the resampler.
I'm starting to lean in the opposite direction and feel like we should have probably stopped at ecma-48. piling up extension after extension is just straying further from the light.
Of course Google is (likely) still at fault here and should have managed this better, but it is important to understand the context also.
reply