Or add EA anti-cheat 6 months after release like they did for EA WRC.

Gatgetbridge (your link) has a breakdown of devices they support https://gadgetbridge.org/gadgets/ . You can click through the vendors to find devices which are both "highly supported" and "no vendor-pair". Meaning most/all the features work without any reliance on the vendor app.

As for the similarity you are asking about with pixel->GrapheneOS, there are very few watches that can run an alternative open source firmware or operating systems apart from the ones that are already open source, like bangle.js, pinetime, etc. Wearables are even more specialized than phones, they require specialized code designed specifically for them and would likely require pretty extreme effort to reverse-engineer.

I use a pebble 2 HR with gadgetbridge but the watch it self runs the old pebble firmware which gadgetbridge talks to. This is fine for me, but if you are looking for a more modern watch you may have to make some compromises.

Nextcloud AIO is not the only way to run Nextcloud in docker. For example you can use the Nextcloud docker repository and docker-compose for which there are many examples. I've been running Nextcloud this way for many years now without any un-recoverable issues, and no issues at all that weren't caused by me. Upgrading is also very easy since you simply increment the version in docker-compose.yml and restart the service.

That said the NixOS suggestion from @StrawberryPigtails@lemmy.sdf.org looks really neat and I may try that out soon my self since I've never played with NixOS before and it seems like a good excuse to do so.

Ok, I'm prepared to be downvoted today so here goes.

Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn't have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

So, while there is legitimate criticism of some of Nextcloud's design choices, this isn't it. And at the risk of sounding a little gatekeepy, if you post "nextcloud updates break everything" with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I'm sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.

https://lemmy.ml/comment/8576827

It requires a login to use it...

“An attacker would need to be able to coerce a system into booting from HTTP if it's not already doing so, and either be in a position to run the HTTP server in question or MITM traffic to it,” - Matthew Garrett

Summary left out a quite important bit.

Mosh hasn't had a release in quite a while (Oct 2022). While that's not that old, and there does appear to be somewhat active development, it's a little slow moving for something that might be open to the internet directly. I used to use it but ssh with tmux is mostly fine and makes me feel a little safer because of their wider use.

I use FreeCAD and Assembly3 for everything and have for many years now. I sometimes use realthunder's fork of FreeCAD but right now it's quite a bit behind upstream and there are some cool new features in sketcher so I use upstream for those.

Some people get confused about workflow in FreeCAD because there are so many options and every youtube video has different opinions or tries to feature a particular workbench like curves or something. My opinion.... Pretty much your workflow starting out should be to ignore everything else and use part design and sketches, it's the simplest way:

0. enable autosave with a short interval, like 2min

1. Switch to part design workbench

2. create body

3. create sketches as the base of the features of your part attached to the xy, xz, yz planes, offset them to create a "wire frame" that resembles your project

   a. Your sketches should be fully constrained

   b. Your sketches should have as little geometry in them as possible, if you need more complex stuff make more sketches

   c. Your sketches should have closed wires, you can't pad something that doesn't create a face.

4. use pad, pocket, revolution, loft, and hole operations on those sketches to form a 3d solid

5. if you need to create additional sketches which import geometry from the previous operations (using the external geometry tool), import SKETCH geometry from the previous ops, not edges of solids, whenever possible. Hide your solid, unhide your sketch, select that with the external geometry tool.

   a. Use sketch on face sparingly.

6. Do fillets and chamfers last, if you need to change something, delete them and recreate them once you've made your changes.

To make multiple parts make multiple bodies with the same workflow as above.

Once you get pretty good at making static parts with constrained geometry, holes, threads (with the hole function), etc, which you can do with only the stuff above, then you can branch out into other workbenches like assemblies or curves, but all of those things build on the concepts above, so it's easy to get overwhelmed if you try to do it all right from the start. Learning how to recover from a mistake is just part of CAD in general, though I admit that it's a bit more effort to find what's wrong in FC vs commercial platforms, but we aren't here, on lemmy, in a linux community, to use commercial platforms.

AFAIK that's pretty much the same workflow as F360 uses for single-solid parts though things have different names. pad=extrude for example.

It's obviously far from perfect but in my opinion it's the best solution that runs natively on Linux and is actually open source. Also assembly3 uses solvespace as it's backend solver so if you make assemblies using that you are kindof using solvespace too.

Also, I hear/read a lot of complaining about instability but I've honestly never had a crash that wasn't on an experimental branch like RT or the edge release of upstream. However step 0 above should help if you're worried about that.

Cura is open source and has linux builds on their github https://github.com/Ultimaker/Cura/releases. Prusaslicer and basically all it's forks also have Linux builds. I personally use FreeCAD for modelling but it's not very popular amongst people who use Fusion360.

I recently switched to sway and I use xeyes to "look" for applications that are not running natively. The eyes only look at applications running in xwayland when you mouse over them since they can only track the cursor there.

I use the unigine benchmarks sometimes. unigine-heaven and unigine-superposition (which btw is just cool to watch in my opinion). They provide linux packages here https://benchmark.unigine.com/ , check your distributions repos too though, some include these too though it's rare. They are not open source, but games usually aren't either.

The phoronix one that someone else posted also looks cool, I'll have to try that one out next time I need something like this.

Because I don't like things to be behind other things. And I feel like moving windows around is a waste of effort and time, and also requires using the mouse where I wouldn't normally have to. Tiling windows and using workspaces to organize my work/play/attention works very well for me and helps keep my focus where I want it.

Also sway in particular, but other tiling window managers too, have better output management than standard DEs. If I'm on output 3 workspace 12 and I want to do something new, any new window I open stays on output 3 workspace 12. I have a lot of displays and not being surprised about where windows open is extremely helpful.