• 2 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • 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.


  • What version of kde? I haven’t tried it, or read about it beyond the changelog, however the latest beta release says that it supports RDP to connect to plasma desktops which is quite an interesting development if it works the way it sounds like it does:

    Remote Desktop system integration to allow RDP clients to connect to Plasma desktops, plus a new page in System Settings for configuring this

    For the “from anywhere” component you could use a vpn, but if you’re looking for a simple solution with zero configuration than nomachine or rustdesk seem more appropriate. Just thought the RDP support was worth sharing.



  • If you want to monitor sleep with it charging at night isn’t possible, and remembering to charge every single day during the day is annoying in my opinion. Not everyone wants sleep monitoring though, or likes to sleep with a watch on, so I get why there’s some division on the subject.

    My pebble 2 hr lasts about 5 days and I’m very happy with that frequency of charging. I think it was a bit better when new but that was a long time ago.




  • I mentioned the client in there (4th paragraph), but mine was more of a general rant on the overall low effort that seems to have been put in to figuring out what the actual problem was. And that it is relatively common among people in the self hosting community to assume that Nextcloud is a lot simpler than it is. It’s a huge cloud suite consisting of many applications, clients, plugins, proxies, caching, database, etc. You need to have a pretty good understanding of how it all works, and how to investigate a problem, and ideally you should be testing before upgrades. Large organizations often even test endpoint applications like the desktop client and push out only tested versions to users via policy or some kind of endpoint management.

    I can’t really draw many conclusions from the very little information provided in this post, but I suspect OPs windows machine is not in an entirely stable state, which is what is causing some of these update issues.

    And, I put some of the blame for Nextcloud under-representing it’s complexity on Nextcloud’s marketing and AIO. You absolutely can install it without understanding anything, and that’s a little dangerous in my opinion because it is actually quite complex and you will probably end up breaking it at some point and need to dig in to fix it.



  • 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.






  • AFAIK openSCAD is a code driven mesh format. So if you want to import openSCAD models into any other CAD software you have to convert the mesh to STEP or some other actual 3d object format during which there can be lots of error if the model is complex. I don’t have a lot of experience doing this but I just tried a model I had lying around from the dactyl keyboard project and converting it resulted in a lot of really broken surfaces.

    This is a cool alternative that makes 3d objects instead of meshes (at least it says it does). https://zalo.github.io/CascadeStudio/ . Also open source but web based.

    EDIT: I should mention that CascadeStudio seems to be abandoned, just a cool concept of a different way of doing code driven CAD.


  • 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:

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

    2. Switch to part design workbench

    3. create body

    4. 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.

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

    6. 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.

    7. 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.