I would gladly pay a dollar in the official store to get this app, even knowing it can be downloaded for free from GitHub

I would like to know more, can you give me some insight?

Well if you use Tor somewhat regularly and check your exit node IP, it is about 50% possible that yours is in that subnet each time you renew the route. Which begs questions.

Maybe I'm wrong, but it would look more benign to have exit nodes distributed without this much bias towards that particular subnet.

It's only 185.220.100 [0] and 185.220.101 [1] that contain all those relays. Some of the bigger German families work together as "Stiftung Erneuerbare Freiheit" that's why you see a big cluster there. But Tor never uses relays in the same /16 for a circuit so it's not really an issue.

[0] https://metrics.torproject.org/rs.html#search/185.220.100 [1] https://metrics.torproject.org/rs.html#search/185.220.101

Correct. "Stiftung Erneuerbare Freiheit" acts as LIR in charge of the address space, handing out chunks of that space to exit relay operating non-profits for free, but does not operate any Tor infrastructure themselves and has no visibility into the traffic. The cost for us are the RIPE membership fees (approx 2000€/yr).

Source: I'm its director and founder of torservers.net. Usually using a different nick here.

https://nusenu.github.io/OrNetStats/ should give you a feel for the overall size & relative homogeneity of the current Tor network.

What's the difference with kuik? Spegel seems too complicated for my homelab, but could be a nice upgrade for my company

Kuik: https://github.com/enix/kube-image-keeper?tab=readme-ov-file...

It's been a while since I looked at kuik, but I would say the main difference is that Spegel doesn't do any of the pulling or storage of images. Instead it relies on Containerd to do it for you. This also means that Spegel does not have to manage garbage collection. The nice thing with this is that it doesn't change how images are initially pulled from upstream and is able to serve images that exist on the node before Spegel runs.

Also it looks kuik uses CRDs to store information about where images are cached, while Spegel uses its own p2p solution to do the routing of traffic between nodes.

If you are running k3s in your homelab you can enable Spegel with a flag as it is an embedded feature.

With the cancel action, that's 4 :p

I used "Now create a theater scenario in 1 act where Santa disclose his secret without realizing it. 2 persons (Santa and a reinder), humorous tone."

It was fun :p

Well I work with gitlab since ~10 years or so, and to be fair this seems wrong:

> These competitors don’t offer other, major code collaboration tools [...] They looked at the dominant player and did the same.

It really feels the opposite to me with gitlab:

- CICD were in gitlab before github action, and is still way more complete in gitlab

- gitpod was here before codespace

- infrastructure and dependency management was in gitlab before github, and still needs third party to be as complete as gitlab

- custom and licence compliance is still incomplete in github, still needs third party stuff ...

My 2 cents: GitHub profits from heavy projects and a better marketing team than Gitlab

But yes, GitLab is at it's full potential only when you pay ...

Gitlab is a worse user experience for people looking at your repo and code online. It doesn't even display a list of files without javascript. And even when it does it take 5 cores at 100% to do a directory listing of gtk3. It's really a terrible web interface no matter how nice the dev side git interface is.

GitLab is also open-core and publicly-traded. For now, I appreciate what they do and how the issue tracker is mostly public, but when the investors say “it’s time to turn this into a money printing machine so I can get my ROI”, I don’t know that I have a lot of confidence in it in the long run.

How to easily create a flow which allow people with litteracy difficulty to send professional emails.