LinuxSBC

joined 1 year ago
[–] LinuxSBC@lemm.ee 5 points 3 months ago (5 children)

It would be largely fine, but be careful. Being immutable, a lot of things that you would expect will work differently or not at all. I would not recommend it, but if you're in for a challenge, it's not bad.

[–] LinuxSBC@lemm.ee 14 points 9 months ago (5 children)

Open source is a license. What you're referring to is "source-available." You can't legally fork, redistribute, or contribute to it.

[–] LinuxSBC@lemm.ee 8 points 9 months ago (1 children)

When you press a button on this revolutionary machine, it will automatically left click for you!

[–] LinuxSBC@lemm.ee 4 points 9 months ago

On GNOME, I like BlackBox, though Prompt looks promising once it's stable.

[–] LinuxSBC@lemm.ee 2 points 9 months ago

A combination of heaters and being mostly deployed in warmer environments, I'd assume.

[–] LinuxSBC@lemm.ee 18 points 10 months ago

They have an "Office Key" on some official keyboards. Pressing Office+L opens LinkedIn. The Office key is actually mapped to that long modifier shortcut.

[–] LinuxSBC@lemm.ee 3 points 10 months ago (1 children)

Actually, the primary dev is no longer active. The other developers have moved to a fork called Input Leap that has Wayland support.

[–] LinuxSBC@lemm.ee 5 points 10 months ago (1 children)

Maybe try Input Leap. It's an actively maintained fork of Barrier (Barrier isn't maintained), and it has Wayland support.

[–] LinuxSBC@lemm.ee 2 points 10 months ago

Maybe try Input Leap. It's an actively maintained fork of Barrier (Barrier isn't maintained), and it has Wayland support.

[–] LinuxSBC@lemm.ee 14 points 10 months ago

Most of what you said applies to the Linux kernel too. It's good to have other options, but being popular does not mean something is bad.

[–] LinuxSBC@lemm.ee 1 points 10 months ago (1 children)

That should work, though you may want to look into Framework instead.

[–] LinuxSBC@lemm.ee 1 points 10 months ago

.ovh domains are like $2/year, if that helps.

view more: next ›