Recently I borrowed my partner's copy of Links Awakening for the Nintendo Switch. I understand that many people did not enjoy the remake due to the graphics but I am one of the weirdos who somewhat enjoys the cutesy round graphics with the intense depth of field / forced perspective look. From a pure graphical standpoint I think this is a really good way of remaking a top down GB / GBC game for a new platform. I similarly enjoyed Pokémon Alpha Sapphire's graphics despite many others not enjoying them.

I think this has to be one of the most frustrating remakes I have played in recent history, solely for the inability to use the dpad for 8 direction movement. I am not against the remake using the joystick for movement, for example the aforementioned Pokémon game alows for the circle pad and the dpad to be used (for 360 degree movement and 8 direction tile based movement). My frustration with the controls in link's awakening is the forced use of the joystick with 8 direction tile based movement. What could have otherwise been an enjoyable experience is made more difficult, and leaves me wondering why I am not playing the original on my 3ds instead.

I do really enjoy many of the QoL improvements in the remake, the graphics, and the music. I also appreciate having the X and Y buttons available unlike the original gameboy versions. I'm still going to power through it, but sadly the GBC version is going to be the definitive version for me despite this version coming so close for me.

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.

Good afternoon!

I was wondering if anyone had experience with using rechargeable AAs (specifically Panasonic Enloops / Enloop Pros). I have yet to try them, but hypothetically they should work as they don't exceed the maximum voltage of 1.5 per cell. (They're 1.2 per cell, closer to what a disposable battery is part way through its life cycle)

I also was wondering if anyone has ever found rechargeable batteries that would work in the main body. I have yet to find one that isn't 3.7v (exceeding the normal 3v of the disposable ones) which would likely render the camera inoperable.

Thank you for your time :)

The wallpaper is just a cropped image from the scans of the games manual found here, note these are spoilers!, Tunic is an absolutely lovely game I have been playing on my Switch and I highly recommend it to people who really enjoy the difficulty of older Nintendo games but want a more polished experience. The way the game integrates the "manual" is really intriguing

For a while I was experimenting with different plasma themes but I landed back on the good old reliable gruvbox dark theme.

Edit: my apologies for not perfectly aligning two of the images in Gimp, I forgot to press the button that aligns them horizontally and not just vertically :p

Here is the github page. The option for different « optics » is neat, and the inclusion of DDG bangs style syntax is also appreciated.

I just thought I would post what I am currently using! Right now I have a Lamy Safari with Sailor Irori red ink, and then I have my Pilot Prera with Pilot Ishroizuku Take Sumi. For the books, I have 2 Rhodia Composition Books that I am using for Uni and then I have my Hobonichi A6 Hon for planning. I am actually enjoying the new Tomoe River S paper found in the Hobo, but I do know some people think the old one is better (I don't particularly have a preference they both seem very great and very lightweight / thin)

I was wondering if anyone else has encountered the same issue as I have. I know how I would approach this if Akregator was installed on the system rather than as a flatpak, I would just change the command run by the app when opening in an external browser to flatpak run org.mozilla.firefox about:reader?url=%u which just appends the about:reader portion to automatically open it as such. This command does work from my terminal but naturally does not work with Akregator.

Any help would be greatly appreciated!

As the title states, I am just curious what peoples opinions are on secureblue, as well as the many other images that exist (notably Bazzite for the SteamDeck)

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.

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.

I am curious as to what are the best practices regarding blurring and / or pixelating a portion of a photo. I understand the reasons why the website suggests to put a black box over text one wishes to redact, but for other content that is not text what is the best choice. Should a combination of the two be used or just one? E.g. for blurring a face or something else within an image.

Thanks!

I am just curious if anyone here changes it from the default (disabled) state. Would you say the telemetry data is particularly useful to the developers & respectful to the user? I generally disable all telemetry even on open source software but I am happy to hear people's arguments for enabling some of it if it helps the developers in a privacy respecting way.

Enjoy your day!