Let me make a possibly unpleasant question: why is Tildes only on Gitlab? Do you self-host? Is it because of Microsoft? Or idealistic reasons (that I would totally 100% respect)?

Github and Microsoft may be "evil", but that's where everybody is. I'm 99% more prone to post an issue on Github than on Gitlab. I know it's "wrong", but that's also true and not just for me. Couldn't Tildes have at least some presence on Github? Is it possible for a mirror to get issues? (I really don't know, honest question). And why not just move to Github, mirror to Gitlab and have some super-reliable backup?

This would give Tildes more exposure (maybe Tildes doesn't want more exposure right now. That's entirely understandable). But Github is where things happen, and I really want Tildes to happen. And, even if Github ever turns evil (or already is), couldn't we just fork/transfer/whatever to someplace else? Or just use the backup? What's the downside?

1. The Idea

Counting overall time would be awesome already. In order to avoid overloading the servers, you could just count every 5, 10 hours or something like that.

As a plus (I have no idea how hard this is, please forgive me), there could be graphs showing how much time you spent by day, week, month, year, etc.

This would be a good way to help Tilders prevent Tildes addiction (on the other hand, there would have to be some mechanic to prevent people from gamyfying this...).

This time count would be entirely private to each user by default, but there would the option to display it.

2. The Reason

I find that knowing how much time I spent on something helps me be more productive. It's the entire reason for the existence of tools such Rescue Time, Waka Time and Toggl. If I know how much I spend on a platform, it's easier to control my addiction to it. These other tools are heavy and focused on billing hours. That's not my use case. I know this might seem silly, but it makes a lot of difference for some people. 7.2% of the world's population has ADHD. I happen to be one of them.

In such a fashion that all my threads will open either collapsed and expanded. Ideally, there should be a setting for that. Some people might prefer to always open expanded regardless of their last choice.

Introduction

I wanna say that I made several corrections, additions, and improvements just because I love you guys way more than I love the people at Reddit

• Please note that I'm merely a dedicated Linux user, I'm speaking from that point of view. I'm not a developer and not a programmer. These are just my opinions of 10+ years using Linux

• These are just some commentaries from a dude who happen to love the concept of STABILITY in general (autism represent) and would like to discuss how it works when it comes to Linux distributions. This is all based on my use-cases and on what I think is common sense. I have no knowledge of how open-source projects really work, and make no claims regarding how they should work.

• Only distributions that claim to be stable are under my scope. So Arch and Debian Unstable are clearly out the scope, but Slackware, CentOS, Debian Buster, and MX-Linux are clearly under the scope.

• All considerations are void if the malfunctioning is SOLELY a product of hardware, extremely rare conditions or your own lack of knowledge.

• Except when otherwise noted, non-compliance means the distribution is deemed not stable.

1 Deal Breakers

After a correct installation by the user on hardware that is expressly supported by the developers, a stable distribution should, in the period of 1 year (counted from the first boot):

1. Remains bootable, manageable and fully accessible.
2. Work with almost no maintenance or intervention (updates excluded)
3. Present no decrease in performance
4. Freeze at most once every two weeks
5. Have no package issue that cannot be solved by a simple command from its own package manager

2 Major Issues

Because of the complex nature of major issues, I'm not going to establish any criteria about them. Both stable and unstable distributions have critical problems that cannot have a fixed time-frame.

3 Minor Issues/Bugs/Annoyances/etc

Small issues are the ones that do not impede the usage of the machine, but provoke significant annoyances:

Examples:

1. Window switching is not working properly
2. The mouse stops working for 3 seconds every 15 minutes
3. For some reason, the letter "c" is sending "h" on the terminal
4. My configurations are not saved after reboot
5. My configurations are not being saved at all
6. I must change video output manually every time I switch monitors
7. I must change audio output manually every time I switch monitors
8. Some essential configuration is ridiculously hard to find
9. Configurations have no undo button
10. Configurations have no reset button
11. A certain package cannot be installed
12. A certain dependence cannot be installed (dependency hell)
13. There's a ridiculously accessible keyboard shortcut that makes your keyboard change layouts all the fucking time

3.1 Places for Research

Such minor issues must be solved within 30 days, as long as the user does their part and seek some of the following resources:

1. Google
2. Official websites
3. Official forums
4. Official warnings, newsletters, etc
5. Semi-official communities
6. FAQs
7. Manuals
8. Github Issues
9. Gitlab Issues
10. Other Venues to post issues

If the minor issue is not solved in 45+ days, the distribution will be deemed not stable, regardless of the behavior of the user.

4. Conclusion

It is my opinion that, if any of the major and minor requirements are not fulfilled according to their particular rules, the distribution in question should not be deemed not Stable.

I currently use MX-Linux, which is a great distribution but does require me to reinstall it from time to time. It also comes with all the good/bad Debian legacy, and sometimes things can get really fucked up (okay, I admit it: MX IS NOT PERFECT. But nothing is, okay? Settle down.)

My new Linux Distribution doesn't need to have all the new bells and whistles, but it needs to be able to stay reasonably current with new packages and innovations. I don't mind some manual work, but I also don't wanna spend my days maintaining the system.

This distro is supposed to be a tool to work with, not a hobby to be pimped, riced or whatever. I will occasionally play and edit videos on it (don't worry, it's all AMD, thank you advice for the Tildes ;)

I use the i3wm window manager (not the gaps fork), so native support is a must and current versions are preferable (MX's version is from 2016. 2016!). If there's not a current version of Emacs, I'll compile my own. The same is true for Neovim, dmenu, rofi and the suckless terminal.

Configurations on text files do not scare me, but I don't wanna spend all my time scripting stuff. I don't mind compiling stuff either so Gentoo and other source-based distributions are valid options (as long as they allow me to work on stuff instead of working on the distribution...). That said, I have no preference whatsoever between binary and source-based.

Unstable distributions like Arch and even Manjaro are a no-no. I need my computer to work 99.99% of the time, like a fucking refrigerator. That said, I would like some newer packages and tools such as Gimp, Inkscape and a video editor like Kdenlive. Maybe flatpak is an option? I was never able to get it to work properly.

I'm also open to crazy things like Nix, but only if it'll make my life easier: I have no philosophies on the mater.

Any suggestions?

This is obviously a thought-experiment, but maybe an interesting one. Let's say we get a super-efficient, eco-friendly alternative fuel that can do whatever rocket fuel does now with 1/100 of the cost, 1/100 of volume and 100% more efficiency. What does it change in the short term?

General Programming Q&A thread! Ask any questions about programming, answer the questions of other users, or post suggestions for future threads.

Don't forget to format your code using the triple backticks or tildes:

Here is my schema:

```sql
CREATE TABLE article_to_warehouse (
  article_id   INTEGER
, warehouse_id INTEGER
)
;
```

How do I add a `UNIQUE` constraint?