Whooping_Seal

Bonjour à tous, j'espère que vous passez un bon vendredi. En tant que francophile, je me demandais où vous trouviez vos recommandations de livres? Pour les livres en anglais, je consulte principalement des sites comme Goodreads, des recommandations d'amis (qui semblent beaucoup provenir de TikTok), ou je navigue simplement, car je sais en quelque sorte ce que je cherche

Pour la littérature française, c'est un peu plus difficile pour moi, en dehors d'aller dans une des libraires et de feuilleter, où trouvez-vous vos prochaines lectures?

Merci d'avance pour les suggestions! :3

Hello everyone! I was wondering what advice people have in acquiring PS2 memory cards. I recently acquired a PS2 slim for my birthday, and frankly my only experience with memory card based consoles is a backwards compatible Wii (where I have a memory card + virtual memory cards on the SD / backups of the memory card)

What is the safest route (in terms of longevity / corruption) to go (with or without homebrew).

Thank you for your feedback, looking forward to trying some classics I missed out when I was younger :)

This is a great alternative to Apple / Google maps for public transit takers. Generally speaking their data is a lot better for service issues, rerouted lines, and the actual time of arrival for transit vehicles. Many transit authorities in Canada actually offer the premium subscription for this app, for free, to frequent riders AND the app is developed locally (in Québec)

If you're just looking for general maps however I highly suggest Open Street Map, or the Organic Maps app on Android (which uses OSM data). While they aren't explicitly Canadian, they get you away from American tech conglomerates and give back ownership of data to you, the user!

Hello everyone!

I was wondering what solutions people have for Calendar syncing that are not Proton / Tuta.

Specifically, I was wondering what E2EE options are available that are ideally cross-platform as well.

The main reason why I ask is I am frankly frustrated with how both Tuta and Proton rely on their own apps, and don't necessarily integrate well with all operating systems. Especially with Proton's growing suite of apps, it feels like they are in some ways creating their own walled garden. While it is at this time a better privacy option than the conventional options, it is still a situation that feels like a vendor lock-in situation.

Any suggestions would be greatly appreciated, including those that require a self-hosted server :)

I have thought about this on and off for quite a few years now, and I was just wondering what people here have done while maintaining account / device security.

I hope people don't mind this rather morbid conversation, but how have people here planned for what will happen with their accounts, computers, self hosted things etc. in the event of their deaths? I am particularly interested in what people have planned for if they are the person in their household who is self hosting things for the household. I'm not in a living situation that allows me to self host much but it is one of the questions I've had for myself when I decide to move in with my significant other and self host more things. I don't think they could manage much of the self hosted stuff and I also don't think they can remember all of the credentials for accounts etc., is the best way of going about it sharing a keepass database or bitwarden account with them?

In regards to my accounts, I am not expecting most of my accounts to transfer, if anything I'd much rather them be deleted (and I have enabled this feature where possible). There are a few however, that I wouldn't mind leaving to someone after my passing. Is there a privacy and security preserving way of setting this up?

I guess I have just been struggling with how to do this, ideally I would want a way for accounts to transfer to someone listed in my will, but I don't think it's a good idea to give ~2-3 people a copy of my keepass databse while I am still living.

I am looking forward to hearing what people's thoughts are on this matter, and I apologize again for such a morbid topic.

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.

Lovely website to test what armour trims look like in various combinations!