It’s been a long time since I kept up with Bungie and had to look back because the name Luke Smith rang a bell.

It led me back to this and he indeed is who I thought he was, the lead of this old song

https://youtube.com/watch?v=MRRlauFtDO8

I’ve been trying to find some good examples of how to structure the files, and whether to combine the photos from everyone or to keep them separate. Obviously there’s different systems for everyone, but your method of syncing, tagging, and displaying/sharing photos is almost identical to how I’ve been wanting to go about it.

Do you mind sharing how you structure the photo files and naming in your Gallery directory?

I was thinking of implementing the Copyright tag to keep the data of the original phototaker, and then combine all the photos into a Gallery/YYYY/MM structure, with the filenames being YYYYMMDD-CameraModel. There aren’t many events we go to, so albums aren’t a big priority, but on the occasion, I was thinking if using a folder like MM-Event in the respective year folder.

I’m just putting my thoughts down because I don’t often see this part of people’s photo organizing.

Sometimes automated updates are not desirable. I also prefer the simplicity of a bash script over a full container.

If you decide to use docker-compose.yml files, which I do recommend, then I’d also highly recommend this script for updating the docker containers.

It checks each container for updates and then let’s you select the containers you would like to update. I just keep it in the main directory with all the other docker container directories.

https://github.com/mag37/dockcheck/blob/main/dockcheck.sh

I just used Hue Thief a month ago to reset my Hue bulbs that I bought about 7 years ago with the gen. 1 bridge.

I did run into a few errors but eventually got it to run. I was finally able to reset the bulbs and get them paired with my be Zigbee adapter.

I used to use FreeNAS but found it was to “heavy” for just home and personal use. I felt like it took a lot more steps to just do some simple things.

During my last upgrade, I switched to using OpenMediaVault and have been really enjoying it. I started using Docker with it and that has been an amazing breakthrough in the way I use services like Jellyfin.

I’ve been using SnapRaid for the data redundancy together with MergerFS so all the drives appear and operate as a single big drive. I have SnapRaid sync once a week which sort of acts like a backup in case I accidentally delete something.

There’s this but I’m not sure if it’s directly relevant

https://github.com/LemmyNet/lemmy/pull/3208

PS: I can still read your parent comment 5 hours later.

Link for easy subscribing

!selfhosting@slrpnk.net

There’s a number of issues open for this.

More directly, the pull request that implents this has already been merged. Just waiting for it to be released

So far, in the time between Elder Scrolls V and and VI, I have:

• graduated high school
• graduated college
• gotten 3 jobs
• started and advanced in my career
• gotten married
• had 2 kids

Meanwhile, Elder Scrolls V: Skyrim Re-release-master-vamped 3 Toaster edition is likely six-plus months away

When you’re writing a message on the web version, typing ! and the name of the community will bring up a suggestion box.

Typing !main and selecting the rblind.com instance autocompletes to [!main@rblind.com](https://rblind.com/c/main) but that links directly to the instance itself. It needs a bit of formatting though to get it to be instance-agnostic.

There’s a big discussion on Github on how to handle links, because as mentioned, the /c/ won’t work for kbin users.

I personally think it should link the instance directly, as it already does, and have a second link in the formatting we mentioned for the local instance link.

Often, a quick way to link communities is by formatting a hyperlink like this [Visible-text-to-click](/c/community@instance.tld)

For a this example, formatting the text like [this link](/c/main@rblind.com) would create this link that most* people can click on that will bring them to that community.

*Kbin users will need to replace the /c/ with/m/

It was just a matter of time before something like this showed up.

I’m sure there will be a number of people that won’t be a fan of this but I think it’s a pretty innovative way to help the chicken-and-egg problem of early adoption. (No users because there’s no content, no content because there’s no users).

Very smart to have it limited to one bot on one instance to make it easy to block (or de-federate) for those that don’t like it, but I do.

It mostly comes down to personal preference honestly.

Jellyfin is open-source and more focused on your own selfhosted media. I, too, bought a Plex pass years ago and have enjoyed Plex but they’ve been adding a bunch of crap to their interface.

I’m big on free open-source software but I won’t be biased to say that Jellyfin has some rough edges, but it works well enough for me to watch movies with my wife. Plex is a bit smoother and more production-ready for those power users that host Plex for several others.

I’d encourage you to try it out if for nothing more than exposing yourself to alternatives.