Well, this version is going to be in the Ubuntu repos eventually, but might take a while. Ubuntu 26.04 is already in feature-freeze, so it’ll be in 26.10 at the earliest (or 28.04, if you follow the LTS releases).

I guess, it would probably also show up in the “backports” repo before that, if you enable that, but might be easiest to use the Flatpak or AppImage instead…

These machines used to require you to put the barcode into the right position. Maybe they’re still used to those machines and therefore look for the barcode on each container?

Obsidian is not open-source…

I just saw this on F-Droid, will need to test it, but sounds like it could be really good: https://f-droid.org/packages/lu.knaff.alain.saf_sftp

I’m hoping, it works like mounting or FUSE on proper Linux, where you can just use normal applications to transparently access network files. Then you’d be able to use any old file manager app to actually work with the files…

You probably just misread, but just to note that SFTP is different from SMB. They’re similar in purpose, but basically competing protocols…

its a corp it cant just make claims and not follow on them

I don’t see why you think that. They can’t wrongly advertise a product, but this is far away from product advertisement.

Personally, I assume that there will be some flow, because you strictly need that for app development, but that they will try to make that as painful as possible for non-development use, because it helps to eliminate their competition.

Ultimately, this should even fall under anti-competition laws, but people have no trust in that actually being enforced, at the very least not in a timely manner before the competition is dead. The only instrument we have is shitstorms, so as long as there is any doubt, it is safer to keep the shitstorm brewing.

Yeah, I always found it really valuable to know a person on the other side. Obviously, they’re not immune to propaganda either, but even just seeing the differences in propaganda can teach you a lot, both about which parts may be untrue, but also how propaganda works.

For example, I once saw a guy on Mastodon, who posted a populist Indian news article and expressed his agreement. The article was about some policy the EU was discussing, following Putins attack on the Ukraine, which would’ve affected India.
That policy was controversial here in the EU. I don’t remember what policy it was, but I didn’t feel good about it, my country (Germany) didn’t support it, but the EU as a whole did agree to it.

Meanwhile, that article framed it as “Europe is doing a bad thing” and “the West is blah”.
Like, man, I doubt, I would agree with my neighbor about this policy, but somehow I’m being generalized into an amorphous blob, the size of half the fucking planet.
It dehumanizes. It makes it seem like we’re not open for discussion, despite us internally leading extremely heated discussions.

But of course, we do the exact fucking same. We talk about India collectively all the time, even though it is much larger than the EU, with 1.4 billion different opinions. You don’t hear “the East” as often these days, but you do hear “Asia”, which is effectively just as meaningless of a word.

And yeah, just seeing the inverse happen to me, made it instantly clear why this is shit, which I would not have even thought about, if I only ever read our news outlets.

Oh man, I don’t want to get deep into all the politics involved, but man, this reads like complete non-sense:

The outage comes following Iranian attacks on the UAE as retaliation for US and Israeli strikes on Iran.

If they did specifically target US corporations in UAE, that would make some amount of sense as direct retaliation.
I guess, you can also attack UAE and hope that they pressure the US to stop invading.
But in any case, this seems like a really good way to drag more nations into the conflict, or at least to force them to become active, which is not in the interest of Iran.

Oh man, seeing folks suggest it as a Discord alternative always had me uninterested, because I don’t even use Discord and it just seemed like yet-another-standard.
Now I’m reading this really technical title for a talk which mentions XMPP and I’m instantly sold.

Well, to be honest, “Movim” also sounded like a VC-funded startup. Looks like it’s a bus-factor-of-1 open-source project instead, which I have significantly more trust in.

I can understand the sentiment and would 100% agree for programming languages.
But personally I actually like that it encourages a flat structure, because you do not want to be yakshaving the structure of your config file. Too much nesting means you will sooner or later run into configuration keys being nested under the wrong category, because your project context changed over time.

And well, as I’ve argued in a few other comments already, I think non-techie users have a disproportionally simpler time when no nesting is used. They understand the concept of a heading and then just adding a line underneath the appropriate heading is really intuitive.
You can just tell them to add the line certificate="/tmp/cert.crt" under [network.tls] and they will find a line in their config file which actually reads [network.tls] and they can just paste that line as-is.

With nesting, they’d need to add it under here:

network: {
    tls: {
        certificate: "/tmp/cert.crt"
    }
}

Which means:

• You need some awkward explanation where they should nest it, or an explanation that e.g. “network.tls” translates to nesting.
• They will ask whether they should indent the line you sent them.
• Well, and it’s also surprisingly difficult to explain between which braces they should put the text, and that’s at the end of the braces, but not after the braces etc., if you’re talking to them on a call.

It’s not even that I’m completely enamored with TOML, but this aspect is certainly growing on me…

I’m always surprised to hear people believe in ghosts, not because I consider it particularly ridiculous, but rather because ghosts have no relevance in my life. I don’t need them to exist to explain what’s happening around me.

Every few years or so, I might hear a noise where I don’t have an explanation, but that always feels adequately explained by me not knowing things. I’m constantly surrounded by living beings as well as materials that are subject to gravity, temperature, humidity etc.. Occasionally, they’ll make noises quite naturally.

Their point is that one could come up with a billion hypotheticals for what might theoretically exist, because we cannot disprove it. If we spent as much time humming and hawing whether each one actually does exist as we do for ghosts, souls, gods, Big Foot etc., then you won’t be doing anything else in life.
That’s why it’s a typical position to just say that they don’t exist until proven otherwise.

Or in the more general sense, this is Occam’s Razor: If there’s multiple possible explanations for something, then one should assume the simplest explanation until proven otherwise.
And if you hear a door slamming shut in your house, then wind is a much simpler explanation than ghosts.

VSCode is Electron, i.e. a webpage, so it’s not hugely surprising that they opted for the natively supported JavaScript Object Notation. And also shows that they don’t care for using the right tool for the job to begin with.

Personally, I much prefer TOML over YAML, because it does not have significant whitespace, and because you can read the spec in a reasonable amount of time. It just has so much less complexity, while still covering the vast majority of use-cases perfectly well.

We just document that this is how you write the config file:

[network]
bind.host = "127.0.0.1"
bind.port = 1234

# etc.

And that seems straightforward enough. Yeah, technically users can opt to use inline tables or raw strings or whatever, but they don’t have to.

Well, you can still decide how much of the TOML features you actually use in your specific application. For example, I’m currently involved in two projects at $DAYJOB where we read TOML configurations and we don’t make use of the inline tables that OP memes about in either of them.

Ultimately, the big advantage of TOML over INI is that it standardizes all kinds of small INI extensions that folks have come up with over the decades. As such, it has a formal specification and in particular only one specification.
You can assume that you can read the same TOML file from two different programming languages, which you cannot just assume for INI.

Counterpoints:

• TOML is intended for configuration, not for data serialization, so you shouldn’t be sending it over the wire in all too crazy ways anyways.
• Most protocols will have a built-in way of knowing when the whole content has been transferred, typically by putting a content length into the header.
• Having to wait until the closing } or ] can also be a disadvantage of JSON, since you cannot stream it, i.e. start processing the fields/elements before the whole thing has arrived. (You probably still don’t want to use TOML for that, though. JSONL, CSV or such are a better idea.)

Well, TOML is essentially just an extension of the INI format (which helped its adoption quite a bit, since you could just fork INI parsers for all kinds of programming languages).

And then, yeah, flattening everything is kind of baked into INI, where it arguably made more sense.
Although, I do also feel like non-techies fare better with flat files, since they don’t have to understand where into the structure they have to insert the value. They just need find the right “heading” to put the line under, which is something they’re familiar with.

They serve largely different use-cases. JSON is good for serializing data. TOML is good for configuration.

Yeah, I was gonna specifically pick out biology. Feels like the more you know about it, the cooler it gets to just head outside and look at critters. Kind of like Pokémon, but real.

I would guess that the units used in smoke alarms and microwaves generally have integrated drivers that only operate at a single frequency.

Yeah, you could more easily create a rhythm than a full melody. If you get a few devices, which beep at different frequencies each, you could do a lot more by having them beep in succession and in intervals.

Of course, this requires that they’re roughly in tune, which may not be the case at all. 🥴