I guess it would contribute to the confusion too. Works on my computer.

Or an old one, maybe…

I saw a warning once a while ago on Firefox… and completely forgot this was a thing until I saw this post right now. I’ve had absolutely no issues. I guess I’m lucky…?

Sounds like the film studios are discussing crime 🔎.

Running Jellyfin off of a VPS provider seems needlessly expensive. I guess server hardware has an upfront cost, but having real hardware to host it on at home will be far more cost effective long term, especially for storage.

Yeah, that’s my main concern. I believe the Immich developers have said they have no desire to implement it, though… Which is fair enough, it doesn’t work for my desired use case though.

I want all data to be encrypted before it even reaches the server. Yes, I don’t want to trust even my own server for my image backups :), particularly since I would want to use something like Immich to provide photo backups for friends and family and I don’t even want to technically have access to their unencrypted photos unless they explicitly share them. I kind of want the attack surface for my photos to be as small as practical too. It’s almost certainly worse to have them available on my device unencrypted than a dedicated server, but it’s worse to have them unencrypted on both (and I want photos available on device so, thems the breaks).

I get that a lot of people won’t care about this and that they’d rather be able to run the image recognition features of Immich on the server and stuff, but I don’t think it’s entirely unreasonable to want encryption for this. If nothing else I’d love to be able to back up photos for friends and family and legitimately be able to tell them that it’s encrypted and I can’t see any of it. It’d be even sweeter if they could do image recognition on device and sync that metadata (encrypted) to the server as well.

I’m kind of disappointed by the lack of encryption. It sounds great, but I don’t want to trust the server.

There’s at least two animated versions that I’m aware of! Apologies for the URLs that contain dates…

• https://en.wikipedia.org/wiki/The_Lord_of_the_Rings_(1978_film)
• https://en.wikipedia.org/wiki/The_Return_of_the_King_(1980_film)

I’ve seen some companies make a valiant effort to make their AWS bill their largest expense, but you’re right.

On the flip side, this is one of the reasons open source projects can be really great. When a community of people can contribute to something to make it better over time and when people can fix their own problems with an app you can get something really great that can get updates sustainably without a subscription model… Everybody just kind of contributes what they can to get what they want. Of course, maintaining an open source project is work and has its own problems and volunteer contributions aren’t necessarily sustainable either and aren’t great for large chunks of work… But there is something nice about the model of “everybody contributes to this thing a little to make something better than we’d be able to make on our own,” even if that’s a bit idealistic in practice, haha.

Seems like it might be fine: https://nextcloud.com/blog/nextclouds-push-notifications-for-ios-and-android/

To be fair that might just be a poor implementation? XMPP can support push notifications just fine now:

https://xmpp.org/extensions/xep-0357.html https://modules.prosody.im/mod_cloud_notify

There are some remaining issues with push (mostly on iOS as far as I know), but it’s all to do with OMEMO. OMEMO is kind of like the signal protocol but in XMPP. This is kind of moot for corporate XMPP, though, as you probably aren’t using OMEMO.

The OMEMO issue is that the contents of the message are end-to-end encrypted so you can’t simply send the notification to devices. I believe conversations on Android may just keep a socket open (or maybe that’s just the fdroid version?) so it just manages it with background tasks. And on iOS monal does what signal does and will use push notifications as a trigger to pull messages from the server. Siskin on iOS just sends you a “you have a new message!” notification instead because they don’t want to spin up the radio to fetch messages in order to preserve battery life. So basically push works fine on monal, and Siskin also has working push but you don’t get message contents.

The particle collider also doesn’t need to ensure the safety of the particles. Frankly, if it did it would be a rather shitty collider.

I was kind of thinking that $22 billion really doesn’t seem like that much money for a project like this.

I consider marketing something as “for free thinkers” as a huge red flag.

For what it’s worth, this has not been my experience after self hosting my email for nearly a decade. It has not been a constant battle at all… it has just worked, and I get responses whenever mailing random people all the time and have not had delivery issues to my knowledge. That said, I have talked to people who have had issues and every time there has been something wrong with their configuration (usually DKIM or rDNS is not set up properly). There’s enough that can go wrong that I wouldn’t recommend people send important emails with it unless they’ve been doing it for a while and they’re sure it’s working, but in my experience this is all fear mongering. Self hosting your email is very doable and is generally not a constant battle against getting put in the spam slammer. There’s a lot of picky little things to set up at first, but once it’s set up it’s usually fine.

In my experience the problems with self hosting email mostly occur when something is misconfigured. I think it’s good for people to try to self host it, and if you pull it off it’s great (I love having mine self hosted, and it’s convenient to be able to have as many email addresses, storage, and accounts as I want). It is difficult to get right and debug when something is going wrong, but it’s far from impossible. If you set up SPF, DKIM, and DMARC and have rDNS pointing to your mail server’s domain name you’ll likely find success. It’s possible I’ve just gotten lucky, but I have never had a problem with IP ranges getting banned.

Tunnel broker blocks port 25 by default, but you can ask nicely and they’ll open it for you. It’s a good option if you don’t have an IPv6 address otherwise.

Having an IPv6 only mail server is potentially risky, though… some other mail servers may only talk IPv4.

I’ve had good luck on a couple of cheap providers. I think a lot of them block port 25 by default, unless you ask, which maybe gives you a better chance. Plus DKIM and stuff are starting to help. There’s probably always some stupid mail server that will block huge swaths of IPv4 if somebody farts in the neighborhood, but I think the situation is improving.