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.
Memories and Gallery (actually deprecated by photos) are not the same thing, just to clarify. I’m not in a position to agree or disagree with any of the statements here since I’ve never used immich, but I don’t want people to think that the default photo viewer in nextcloud is what was being discussed here.
Ah, I didn’t want to make any negative assumptions about your disability. Yeah if you can get an off the shelf one that would be much easier. I have no experience with the CSL series (or any commercial wheel, I went from the t300 to a 15nm peak ffboard+odrive wheel), but I hear they are pretty good. What you will get from the more powerful and expensive models is increased detail at low power in addition to the obvious higher output as far as I understand.
Have you considered building one of the open source wheel projects like openFFBoard (github page)?
You get direct drive power with open source software and can source a motor and parts more easily. OpenFFBoard has a custom controller and driver which you can buy but you can also make it work with dev boards and odrive/vesc if your ability to order parts is limited. The ffboard does make it easier if you can buy just that one part though elecrow.com/open-ffboard-stm32f407-usb-interface-…
That said, and to answer your question as best I can, I used a T300rs for a while and it was fine, but both thrustmaster and fanatec suffered (and still do a bit) from some reliability issues. But no belt drive wheel is ever going to compare to a direct drive wheel.
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.
So, I’m not sure if the process has changed in the last decade or so but in a long-ago computer forensics class step 0, before all else, was to never operate data recovery on the original disk. Create a block level image of the entire device, then work on that.
My go to steps for recovery have been the following in the years since:
create an image of the entire disk (not a partition) using ddrescue ddrescue -d /dev/sdX <path_to_image>.img
Run test disk on it selecting the partitions as necessary testdisk <path_to_image>.img
If the disk has a complicated partition layout, or more effort is required to find the correct partition you can also mount parts of the disk.
create an image of the entire disk (not a partition) using ddrescue
ddrescue -d /dev/sdX <path_to_image>.img
Mount the image as a loopback device with the appropriate offset
losetup --offset <some_offset_like_8192> --show -v -r -f -P <path_to_image>.imgthis will mount individual partitions:
<span style="color:#323232;">loop58 7:58 0 465.8G 1 loop
</span><span style="color:#323232;">├─loop58p1 259:7 0 1.5G 1 part
</span><span style="color:#323232;">├─loop58p2 259:8 0 450.6G 1 part
</span><span style="color:#323232;">└─loop58p3 259:9 0 13.7G 1 part
</span>
Then operate testdisk on whatever partition you want.
All that said there are a lot of variables here and things don’t always work perfectly. I hope you do find a way to recover them.
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 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.
Sway for a little over a year now (on an AMD gpu). I switched for mixed refresh rate support and VRR. VRR requires a workaround in sway but works better in others, like hyprland, however I like sway’s tiling better so I stuck with it. Also the absence of tearing in anything, ever, is worth it to me. I have two vertical displays and it was really hit or miss on X11. Sometimes GPU acceleration would just decide not to work in browsers and I’d have to restart them because smooth scrolling would turn into a stop-motion film. That’s never happened since switching to sway.
I use sway and run zoom in my browser (because zoom is shady and I don’t trust them). Screen sharing works fine in the browser. The application never worked very well to being with anyway for me, even on X11.
I also use git.dec05eba.com/gpu-screen-recorder/about/ for individual output screen recording such as gaming which works amazingly well. You can not select a section of a single output though, only the whole output. That’s a deal breaker for some, and a non-issue for others, just depends on what you need.
But can it sneekily destroy the cables under my desk? And does it sometimes just stop and look at you to think “I could destroy you… if only I was a little bit bigger”.