Whooping_Seal

joined 2 years ago
[–] Whooping_Seal@sh.itjust.works 5 points 5 months ago (2 children)

There is also last.fm. I would have suggested libre.fm but they are no longer open to registrations it seems

This would replace the "algorithmic" component of spotify, I would still suggest some other options (sharing stuff in your social circle, seeing who opens for your favourite groups etc.)

[–] Whooping_Seal@sh.itjust.works 30 points 8 months ago (1 children)

If you don't mind clarifying, what do you mean by DoD?

[–] Whooping_Seal@sh.itjust.works 3 points 8 months ago* (last edited 8 months ago)

Frankly the best solution i have seen is always a combination of things. At least in the city I live in, people can take bikes on buses and trains, many people walk, and for trips that require trunk space (e.g furniture, DIY supplies etc) there is a Car sharing service that is cheaper than owning a car, or using ride share / taxi.

I don't think waymo is a better option than a combination of what's above, I think it can perhaps compliment it but it should not be the sole last-kilometre solution.

I would like to see waymo-like tech provide better public transit for the disabled. As of now, people in my city with disabilities can book special routes which are serviced by specialized buses/ taxis, and existing lines are all wheelchair accessible as well.

Self driving cars give the opportunity for those people to have even more freedom in booking, since as of now they can't do last minute booking for the custom routes. It wouldn't really create a traffic problem and massively would increase quality of life for those who are sadly disadvantages in society

[–] Whooping_Seal@sh.itjust.works 8 points 8 months ago (1 children)

I'm pretty sure they still are a defence contractor in the US, they also are generally the option for biking computers. There are competitors but Garmin has a chokehold on that sector, with other options just feeling worse.

So while their smart watches are more niche than Apple, Samsung etc, they still have found a solid niche in the smart tracking sector.

[–] Whooping_Seal@sh.itjust.works 4 points 9 months ago (3 children)

Frankly I would like to not use Apple CarPlay / Android Auto — however, the built in software needs to actually usable and continuously updated.

I particularly want to see better non-touch input. Rotary dial + buttons à la Mazda, and much better voice input. I live in a multilingual region, and it consequently renders most in-built navigation voice commands useless, as it won't understand language switching. Even Google assitant has issues with this despite supporting multiple input languages, usually resulting in me saying the entire command in the same language as the address. (Or just giving up if the name and street are in two languages).

But with built in systems that only support one language at a time, I just can't say some of the addresses since I don't know how it wants me to mispronounce them in English.

I also have found media playback frustrating in any modern vehicle. This is likely a lot harder to solve, but the inability to switch playlists or change playback settings without my phone connected to Android Auto is frustrating when in vehicles without it.

I know this is very ranty and not that big of a deal, it's just frustrating seeing so little progress in the past decade on this front — and in some aspects like human interface design of vehicles, they have frankly regressed. If I look at the voice input systems on cars from 15-20 years ago there has been huge improvement, but even 10 years ago to now it doesn't feel that different. Maybe a few new commands, but the quality of recognition / utility of the system is lacking.

 

cross-posted from: https://sh.itjust.works/post/1163818

Update: The guide on github has been updated and has addopted a different method. Notably, it:

A) still accomplishing my goal of avoiding running the process inside as root.

B) uses the linuxserver.io image rather than the syncthing/syncthing one (my method does not allow for the linuxserver.io image to run), the linuxserver one is based on > alpine, I truly forget what the other one is based on.

An archived version of the guide I followed to create my setup has been placed bellow, the updated (and all subsequent version) can be found here

I saw this guide discussing how to run Syncthing in > a podman container on immutable OSes and decided to try and create a better solution that avoids running the process inside as root. I am new to podman and it's been > a few years since I used docker so I am a novice in this side of system administration and I guess I am writing this as a "sanity check" for what I have done.

Below is the podman run arguments I used in place of the ones found in the article, I also manage it with systemd as shown in the article.


podman run -d \
 --name=syncthing \
 --hostname=syncpod \
 --label io.containers.autoupdate=registry \
 --userns keep-id \
 -p 127.0.0.1:8384:8384 \
 -p 22000:22000/tcp \
 -p 22000:22000/udp \
 -p 21027:21027/udp \
 -v ~/.config/syncthing:/var/syncthing/config:Z \
 -v ~/SyncedDirs/:/SyncedDirs:Z \
-v ~/SyncedDirs2/:/var/syncthing/SyncedDirs2:Z \
 docker.io/syncthing/syncthing:latest

Note: I feel the original guide does not explain what the :Z flag does very well, it should at least emphasize unknowing users that it is telling podman to change the SELinux label of a dir to match that of the container.

The notable changes in my arguments is the --userns keep-id option and switching from the linuxserver.io version to the syncthing image. The keep-id option from my understanding tells Podman to create a user namespace where the user and container map to the same UID:GID values. Allowing all files the container touches to still be used by me, the user. I had to switch from the linuxserver.io version to the syncthing official one because the former did not allow the --userns keep-id option to work (perhaps because it is based on Alpine Linux? I have to investigate more. It failed on running an add-user command if I recall)

Below is an excerpt from a RedHat article describing the --userns keep-id option, square brackets are mine:

User namespace modes

I can change this default mapping using the –userns option, which is described in the podman run man page. This list shows the different modes you can pass to the –userns option.

  • Key: "" (Unset) [Effectively what the original guide did]
    >Host user: $UID
    >Container user: 0 (Default User account mapped to root user in container.) (Default)
  • Key: keep-id [What I am doing]
    >Host user: $UID
    >Container user: $UID (Map user account to the same UID within the container.)

(Source)

So far this method seems to work quite well, and has replaced the syncthing package I had layered for a while. Is this the best way to run it on an OS like Silverblue / Kinoite, or is there a more sensible route to go? Any feedback is appreciated!

Edit: Clarity and grammar, and some more detail in a few spots.