I somehow couldn’t bear the “self-scratch self-praise” top part of the post, but starting with
"But the balance is crucial" it was really interesting to read! Contrary to my initial fears, it’s not a self-praise post, but actually useful and talks about problems too.

Grok this grok that…
I’m sorry, but ***k grok. Stop posting about it.

disroot is quite decent. I like their (privacy) vibe and the set of semi-independent services they provide.

Yeah that’s a great idea! I use that too. An encrypted USB drive makes sure you can trust the data not leaking, and spaced repetition can (should) be practiced to memoize the password. Then you’re good I’d say.

Technically KeePass can “merge” and has some sort of conflict resolution, but you’re right that forgotten and unaddressed conflicts can lay around for unlimited time without you noticing. It’s the main problem with keepass + syncthing.

It’s a bit sad that you’re downvoted so hard. You obviously have good intentions, just not having a good grasp yet if I may be frank. The solutions in this post are what you should follow IMO. In short, USB thumb/hdd drives with your important data. Encrypt the whole USB if your devices are under Linux if you wish. Use a proper password manager like KeePass to secure it additionally, with a strong master password of course.

Mike: rachel and i are no longer dating

rachel: mike that’s a horrible way of telling people we’re married

TL&DR: Rust is officially adopted, and thus no longer experimental.

It’s actually a mistake done in a hurry, according to a comment by the author of the post below.

That’s bizarre. Did you try clearing up the hidden folders .stfolder and .stversions and starting from scratch? I’m not doubting that you experience what you experience, I just never had it and I’m curious how you can even get to such a state. Using “syncthing fork” from F-Droid and Syncthing-v2.0.12 on desktop.

Hey, welcome to the concept of self-hosting! This is where I was 15+ years ago.

Realistically, I’d just recommend installing something and trying it out. You’ll iterate many time before you’ll slowly start to align somewhere I suspect, in terms of software/approaches etc.

If you want the very first steps, then why not simply connect your old PC to a monitor and install a Desktop version of Mint? It’s super-“wrong”, but it’ll get you started. Once you reach a stage of not wanting to waste memory/CPU on a graphical system, you’ll be able to do something like systemctl disable lightdm.service and voila, graphics don’t load on start anymore. Once you get even more confident, apt remove gdm3 xfce4 xfdesktop will remove any extra disk space (I’m dropping DE names that I approximately remember off the top of my head). With the packages for graphics gone, your system is indistinguishable from a server now.

Overall it’s a nice path to walk, or at least it was fun and somewhat educative and very frustrating and giving a sense of control for me personally. Do you have any specific questions?

Or bubblewrap. Though that requires more effort than “a bit of time” to do comprehensive isilation…

I get that you are feeling slint is not GPL, but I do not understand where that feeling comes from.

I think it’s because the for-profit nature of the company may not create an actual community of FOSS enthusiasts around it. So if something were to happen to the business side of Slint-the-company, there would not be a strong community with known leaders and vision to save the situation. It’s not like this is guaranteed for FOSS projects, but it’s much more likely there. Single-person FOSS projects are scary to me for this reason as well.

That is the biggest factor for me. (There are other important factors, too.)

Why should we care about an AI tailored to that one person whom many consider a fascist?

Negative publicity is also publicity. Please let’s rather ignore this stupidity.

Nice project!

Only somewhat related, but for myself personally, I’ve realized that the default UI for YouTube at least, promotes doom scrolling as much as it possibly can. It seems to have a negative effect on my mental health and habits. So I live mostly without YouTube now, with only some occasional (once every few weeks), externally linked videos, that I usually download via yt-dlp or just quickly watch online. For the online watch, I broke the page so bad with uBO that the page barely works, and there are no recommendations or after-you-finished-viewing transitions.

This approach seems to work well. I find YT to be a really dangerous place. In one phrase, “sweet death”.

Some projects managed to pull off a license change before

I think you’re right, the reality is not actually so black-and-white. With the GNU project indeed being a notable “exception” of sorts. And, while I can’t think of any single project that would change from GPL and still be alive, I think I’ve heard about at least attempts of doing so once, more than a decade ago, not too successful IIRC.

So to be a GPL project

But to answer the question… I’m not trying to say what is a GPL project. But sometimes I can tell when something isn’t [a GPL project], and Slint isn’t. It doesn’t revolve around copyleft and its ideology. Neither is MySQL. MariaDB is. MariaDB is easier to fork off MySQL than it would be off Slint though. Slint has much broader API, more evolving too I’d assume (but I don’t know).

So my recommendation on when to use or not use Slint would still hold. And I still insist that it’s factually correct to say that Slint is not a GPL project.

I think we can’t find an agreement on our angles on the topic so much that it’s simply not constructive to push the conversation further. I’m afraid that if I’ll try to say anything now, it’ll be a repetition of what was already written earlier.

In short, I see Slint as a not GPL project (but rather as a commercial project that happens for now to triple-license the code and includes GPL). I see GPL projects as fundamentally different to Slint, in a sense that, once you have enough external contributors, you simply cannot revert back and stop being a GPL project, whereas in Slint I see it as possible. I trust GPL projects and I know I can “lean” on them, whereas I’d advise to rely on Slint only if you have commercial entanglement that you want to keep.

I’d propose to agree to disagree.

I’m not sure if you’re reading my message well?

I’m saying that GPL-licensed *projects* protect themselves well. If you lean on a GPL project, it’s likely going to hold. Not disappear because of a commercial incentive. Non-copyleft projects tend to disappear if they become valuable to companies, such as IntelliJ’s Rust plugin, or BSD => MacOS.

Again if you’re developing a non-open-source project, Slint is fine. You’ll be bound to each other with mutual commercial interests.

Please check when posting if it’s a duplicate (it is).

Sorry for the late reply.

The royalty free license tries to get as close to MIT as we can while limiting the use on embedded…

I think I understand that perspective. But please also understand the other perspective: how a user has the right to see it, when they are not connected to the company.

If you are such a user, then you need open-source software for your daily life. And you use it. At the same time, you see:

• IntelliJ Idea taking its MIT-licensed Rust plugin and deciding that it’ll be more profitable for them to close-source it, so you won’t have it anymore. And of course nobody forked the plugin. The idea is clear, the company wants you to use Rust Rover.

• Apple’s OS, being historically based on 4.4BSD-Lite2 and FreeBSD, and being the second-highest valued company in the world (!), is happily living with all and any of that MIT-licensed code, while BSD itself is stagnating. It’s not Apple’s fault of course, Apple is not a bad actor here. It’s just not very smart or future-proof to spend a lot of time binding yourself to a system that can easily turn into stagnation.

On the other hand, GPL-licensed projects protect themselves very well. When things don’t go well, you see successful foks (such as Forjeo, LibreOffice, MariaDB). When things go well, you just see it thriving (such as Linux, most userland software).

We try to make all of the terms as clear as possible. We rewrote the Slint licensing page several times,…

To answer this and to conclude, for me personally, it’s not about how to write something. It’s about what is written. The fact that Slint aims to be good for a for-profit company, does not and will never nullify that MIT contributions are re-licensed as GPL or proprietary. It will come up, and it’s fair when it does… as I see it, at least.