Not until it’s a mandatory popup or recommendation any time you want to watch. Or maybe mandatory ads and popups on “new releases”. With Plex, nothing surprises me now.
Sorry that’s on me. That’s one thing I removed from the pastebin file on purpose, it’s here in the real one. I copy paste my path to be sure it’s correct.
I was aware of forgejo back when I first started hosting Gitea. Didn’t see much of a diff back then so I just went with arguably more popular option at that time.
About few months after it’s mostly just because I’m too lazy of a person.
Forgejo is a fork of Gitea. As of now I don’t think they have diverged much. So they’re (still) about the same. It was mainly created because of the takeover of the domain and trademark by a for profit company. Not because of different functionality.
As explained in this discussion this seems to be a problem with the web interface only, caused by the framework used by the interface (Svelte). It seems that getting subpaths to work with Svelte is not supported, and the Immich devs are probably right to think it should be fixed by Svelte, not by Immich.
I was trying to think how Plex thinks this is going to play out, knowing that this move will piss off their customer base. Then I realized, this isn’t a play for Plex’s existing customer base. This is a play for their customer’s “friends and family” that are enjoying shared libraries already.
Their ‘customer’ base has for many many years been developing a large user base of technologically naive people with Plex apps installed who could never run their own server. If Plex knows, for example, that for every paying customer there’s three other users pulling from someone’s library, that’s a huge opportunity for them to convert those users to paying customers.
Everyone that set up a Plex server and then shared it with your tech-phobic parents, cousins, friends, etc… We made this possible.
I don’t like it but I can’t argue with the logic from Plex here.
Well maybe not. Without the shared libraries I doubt the tech-phobic users will stick around for movies they can likely find other places, especially since I doubt Plex gets very good deals for content.
I wouldn’t be so sure if that. It’s possible, yeah, but if my theory is right they see the library sharing as the carrot to get normies to download the plex app onto their roku or apple TV.
Pivoting to a streaming only app would close off that avenue for user acquisition permanently.
Is that bad though? I don’t mind renting a movie I really like even if my friend has it on their Plex. Especially if it’s from a small studio. Currently I do that via Google TV. Plex Inc being a small private company might use the money better than a publicly traded giant. I wouldn’t mind my friends and family spending a few bucks on it either.
Of course if Plex starts enshitifying existing private streaming features to push this, that’ll be another matter altogether. Which would not be unexpected.
It’s worth donating if you have the means to. I paid for a lifetime Plex subscription. So, I felt uncomfortable not donating to Jellyfin. They take donations on open collective.
Now you seems to get MySQL permission issue (or wrong database password, but your issue is probably not that). When using docker compose, MySQL won’t see access coming from linguacafe’s container as coming from localhost, but instead it’s coming from a different IP address inside docker subnet. So make sure your MySQL user has proper privilege, e.g. by granting all permissions to ‘user’@‘%’.
I definitely do not count it against them as long as they know how to human at the interview. I just review the code as I would any repo.
The only thing is that with regular projects I tend to go “I noticed on your GitHub you have project X that uses technology Y, etc etc”. With H projects I just go “do you have experience with Y” and let him choose how much he wants to share about the project. So far they remain vague on the non technical details and I let them leave with their dignity intact.
So, ranked, way ahead of candidates without visible projects, but slightly behind people with projects we can discuss in detail in front of the people from HR ;)
I’ve been using it for about a month, and love it.
My one complaint: self-signed certs on reverse proxies seem to break the android app backup. I’m not sure why, but internal CA seems to make things angry. Its more likely to be a local setup issue than anything in immich, but frustrating to pin down.
My current backup strategy is BTSync, which while super easy to get going is a pain in the ass to look up old images. Using direct IP on the app works perfectly, and the DNS lookup only works internally anyways.
All that to say that I’m probably going to use it and remove the btsync approach in a couple months.
I also have internal only traffic, but I still use let’s encrypt. I self signed for a couple of years, but switching to proper certificates made things much simpler and better. Especially on mobile.
I use a combination of my own domain and caddy. and duckdns, since my domain registrar does not have an api caddy can use, but I can point my domain to my duckdns domain and it works 👍
selfhosted
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.