Libre___

I dislike CFs role in the modern Internet as much as the next person, but this is a bunch of speculation trying to connect dots with no basis other than that a Canonical cert renewal happened on the same day as a company transfer.

There might be somewhat of a tangential story, however, in that Njalla seems to have reorganized or changed ownership fairly recently[1], and that Njalla and immateriali.sm seem to be related entities[2]

https://xn--gckvb8fzb.com/njalla-has-silently-changed-a-word... https://www.wipo.int/amc/en/domains/decisions/pdf/2026/dio20...

I was a bit curious about the MAC address since it isn't locally administered which indicates to me that someone likely deliberately chose this range of addresses.

https://www.google.com/search?q=%2290%253Ade%253A01%22+linod...

Googling for '"90:de:01" linode' and '"90:de:00" linode' indicates that addresses from these blocks have been assigned to other linode VMs recently. I sadly don't have a linode VM of my own to compare with right now but it would seem like the traffic has been routed to another VM on linode infrastructure

Similar: https://github.com/cilium/tetragon

Sounds like what is also called Bayesian inference. Julia Galef did a nice series of videos on this: https://www.youtube.com/watch?v=BrK7X_XlGB8

It might have been a Diavox(https://www.ericsson.com/en/about-us/history/products/the-te...) clone actually, but it was mainly the Cyrillic markings on the back of it...

This pic looks like the real deal although I've seen Soviet Dialog clones traveling in eastern Europe.

It does seem to be an export variant however, as the Swedish pulse dial system had the number 0 first: https://upload.wikimedia.org/wikipedia/commons/c/cb/Dialog_1...

As an anecdote this is why the emergency number in Sweden used to be 90 000, in the dark or in a smoke-filled room you'd be able to feel your way to the last number(9), and then pull four short times from 0 to the finger stop to get emergency service.

My TV is completely airgapped now for privacy reasons, but I really wish there was a way to replace the OS running on it.

I used to be(and still am) a big fan of the Smart TV concept, seeing as there's a whole quad core ARM SoC built into my TV that might as well take the streaming duty instead of having an extra HTPC or Chromecast lying outside of it.

If you get carpal tunnel in your twenties your career will likely be affected as well

You need to make the distinction between PA(provider allocated) and PI(provider independent) objects, as well as the distinction between LIRs(members of the RIPE NCC) and end-users.

PA can only be held for further assignment in their networks by a LIR that is a member of the RIPE NCC, received in two ways: maximum of one IPv4 allocation /22 with proper justification, or acquisition through merger with another LIR. The membership fees are as you mentioned.

PI resources are assigned to end-users in the region, that do not need to be members of the NCC. They do however need a valid end-user agreement with a LIR, and each(unless they are allocated on the same date) object entails a 50€/yr fee, billed to the LIR. PI IPv4 is no longer being assigned from RIPE, but existing ones are openly traded.

My guess would be that the nets you were looking at were PI networks, so no, you do not need to pay the membership fee.

The document ripe-680 covers basically everything you need to know: https://www.ripe.net/publications/docs/ripe-680

Don't get me wrong - it's in no way illegal to use A/AAAA-pointers in your zone root.

RFC 1034[0] however, argues for a tree-based structure and lays emphasis on the value of branching. It being 'wrong' might have been too strong a description, how about it being 'improper'?

When I've seen SSH access being offered as a network service and not as a means to administrate other services on a network it's often been under names such as 'shell.example.com' - not exactly your 'ssh' label but an approximation.

0. https://tools.ietf.org/html/rfc1034

The main thing that I dislike with the no-www trend is that it is hierarchically wrong:

. is ICANN root

.com is VeriSign

example.com is Example Company LLC

www.example.com, subdivision.example.com, www2.example.com are all services, subdelegations and individual hosts within example.com

I realize this is a rapidly declining way to view the DNS but it is nevertheless the way it was designed.

First thing that came to mind here too. Wikipedia has some fascinating reading about the GE and AEG networks in Japan: https://en.wikipedia.org/wiki/Electricity_sector_in_Japan

That's not how Google GGC and their LB works, the authoritative NSes looks at the IP of the querying resolver and hands out a response depending on that

I would encourage fairly tech-savvy users to set up their own DNS resolvers - fast, more private and a way of bypassing your ISPs censorship.

Just make sure to configure ACLs so recursive queries are limited to you and not part of a botnet. Also BIND9 might not be a good idea for a low-maintenance solution.