![](https://lemmy.ananace.dev/pictrs/image/49af6b34-655f-42a6-9854-e2cb3ae15fd6.png)
![](https://lemmy.ml/pictrs/image/zXqqvadAXQ.png)
Factorio is great, I’m also a fan of X4.
Just another Swedish programming sysadmin person.
Coffee is always the answer.
And beware my spaghet.
Factorio is great, I’m also a fan of X4.
It’s somewhat amusing how Itanium managed to completely miss the mark, and just how short its heyday was.
It’s also somewhat amusing that I’m still today helping host a pair of HPE Itanium blades - and two two-node DEC Alpha servers - for OpenVMS development.
Go has a heavy focus on simplicity and ease-of-use by hiding away complexity through abstractions, something that makes it an excellent language for getting to the minimum-viable-product point. Which I definitely applaud it for, it can be a true joy to code an initial implementation in it.
The issue with hiding complexity like such is when you reach the limit of the provided abstractions, something that will inevitably happen when your project reaches a certain size. For many languages (like C/C++, Ruby, Python, etc) there’s an option to - at that point - skip the abstractions and instead code directly against the underlying layers, but Go doesn’t actually have that option.
One result of this is that many enterprise-sized Go projects have had to - in pure desperation - hire the people who designed Go in the first place, just to get the necessary expertice to be able to continue development.
Here’s one example in the form of a blog - with some examples of where hidden complexity can cause issues in the longer term; https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride
Go really does do well in the zero-to-hero case, that’s for certain. Unfortunately it doesn’t fare nearly as well in terms of ease when it comes to continued development.
Well, things like the fact that snap is supposed to be a distro-agnostic packaging method despite being only truly supported on Ubuntu is annoying. The fact that its locked to the Canonical store is annoying. The fact that it requires a system daemon to function is annoying.
My main gripes with it stem from my job though, since at the university where I work snap has been an absolute travesty;
It overflows the mount table on multi-user systems.
It slows down startup a ridiculous amount even if barely any snaps are installed.
It can’t run user applications if your home drive is mounted over NFS with safe mount options.
It has no way to disable automatic updates during change critical times - like exams.
There’s plenty more issues we’ve had with it, but those are the main ones that keep causing us issues.
Notably Flatpak doesn’t have any of the listed issues, and it also supports both shared installations as well as internal repos, where we can put licensed or bulky software for courses - something which snap can’t support due to the centralized store design.
To be fair, having to interact with MS Teams with any part of your body is painful.
I’m currently sitting with an Aura 15 Gen 2, and I’m definitely happy with it.
I do wish they’d get their firmware onto LVFS, but that’s about my main complaint.
Been using the KeyDB fork for ages anyway, mainly because it supports running in a multi-master / active-active setup, so it scales and clusters without the ridiculousness that is HA Redis.
I feel like this could go really well together with Piet.
Just imagine; an album consisting of a bunch of Velato programs with Piet code as the artwork.
This looks really odd in relation to other fediverse software; Why /magic
and required to be on the root of the domain? Why hard-require routing the domain part of the user ID when .well-known/webfinger
exists? Why is there a X-Open-Web-Auth
header which the spec only describes as “its purpose is unclear from the code”?
So many questions.
I definitely like the idea of distributed sign-in, Solid did a decent work of that many years ago after all. This particular proposal just looks rather odd.
Apparently the new OLED screen will be available through iFixit
If you’re taking part in transmitting a torrent over Yggdrasil, then people you’ve peered with in the swarm will definitely see your Yggdrasil IP - which is based off of the encryption key you generate (and you can change whenever you wish) for the connection to the mesh.
Regarding obfuscation of what you’re accessing inside something like the bittorrent DHT, that could likely be done with multiple Yggdrasil connections and torrent clients - so each address only associates with one torrent, it’s just not a core feature of the network itself.
The Yggdrasil network really isn’t meant to provide perfect internal anonymity between two directly communicating peers, it’s instead built to be an easy-to-use, end-to-end encrypted, mesh network - with great performance.
It’s there to protect the content and target of your communications from anyone beside you and said target, without adversely affecting the delivery of said content. Not to protect you from your communication target, though it can do a passable job at that too.
My main use of Yggdrasil has actually been as an easily setup alternative route into NATed systems, seeing as I can easily hit 600Mbit and get below 15ms of latency over it, which I quite often use to run VNC or SSH (and SCP/rsync) over. And since the mesh can be established as long as you can reach a node, it becomes ridiculously easy to get a functional link over it.
Transmitting DC++ traffic without my ISP being able to detect any of that is just a bonus.
I should note that I’m not relying on Yggdrasil for anonymity inside the network, rather more for anonymity towards observations from outside the network. And also mostly anonymity towards what I’m communicating when observed from outside the network.
Been doing some DC++ over Yggdrasil with good success
To me it sounds a lot like “We don’t really want to answer that question, so here’s a bit of technobabble to ease your mind.”
I mean, writing your own linked list in C and then summing its values could be considered as having “a proprietary data model that calculates”, but it has basically nothing to do with the question on how they track such things, just hints that they’re not using an existing - and proven - tracking method.
To clarify; they took the question “How are you tracking installs” to mean “With your tracking data, how are you counting installs”, and then basically answered “We add the numbers together”
This is a complete non-answer, and it seems to suggest that their actual tracking method is likely unreliable.
I love their response to (paraphrasing) “Are you going to do another Darth Vader and alter the deal on us in the future?” - “Oh yes, potentially every year.”
If you search for https://beehaw.org/c/programming instead - a.k.a. the URL instead of the Lemmy-syntax of !programming@beehaw.org
- then you should find it as a “person” on Mastodon. Messaging to that “person” is the same as creating a new post in the community, replying to one of its boosts is the same as commenting - or replying to a comment.
Seems to work with my personal setup at least, with two libraries - the default on
~/.local/share/steam
, and one on/mnt/storage/steam
- and Stardew Valley installed in the secondary storage library