Oh, I'm there chief.

Edit: I have more

"It's the year of the Matrix desktop" 😂

Glad you liked it!

As a person who just switched to it (I've been daily driving it on my phone/PC for the past couple weeks) I'm also really enjoying it. The devs are very active, definitely worth following their space.

The person I was responding to was basically complaining about the complexity of enabling and working with crypto for non technical folk.

It's always going to be hard if you're trying to move people to a new platform and teach them e2ee best practices. .

If you disagree, then that means you've had more success with convincing your non technical friends and family to verify devices, e2ee passwords, and back them up! Great.

But for those who can't seem to do so, seeing as how their friends and family are already offering up their data to the highest bidder by default, bringing them over to a homeserver you own and manage - without the use of e2ee locally - is absolutely a step up compared the alternative of just giving it all to WhatsApp.

Try Sable, a new matrix client. Its voice features made me start using Matrix for gaming, recently.

I've just telling my normie friends who join to disable end to end encryption. If they're on my homeserver it doesn't matter, as we're all communicating internally, and if their account is on m.org... Well... Just mind what you say? No different than chatting on Discord or WhatsApp, IMO.

People get annoyed about the setting up of devices, but that's literally tied to a new type of feature you probably don't need. And e2e shouldn't be by default for most people who can't even remember passwords - I still remember losing all my signal messages because I didn't backup my recovery key and my one phone with it installed decided to, helpfully, clear out my data :)

Tl;DR being unintentionally forced to engage in e2ee is always going to be a bad experience. Our non-technical friends are coming from platforms without it, just forego it for the time being. (yes, I don't care if WhatsApp or whatever claim to have it, if they own your keys it ain't e2ee)

As a person who recently switched to using Unreal for a project... Oh god Tim Sweeney please just give me another year before you start pulling shit like this goddamn

It means one of two likely pivots if you ask me: the resurgence of highly locked down consoles with hardware protecting the data, or - and this is the most likely path - devs will just resort to making online only games, where lots of the content is streamed in while playing (I mean assets, not the display output - though don't doubt the latter, if it ever becomes feasible enough I'd posit that devs would migrate to that as well).

Think a "live-events" driven game where every pre-determined period of time you download the assets for that period.

Fortnite-ification of gaming, basically. :(

That was a coordinated attack that happened for a brief period. As a guy who runs his own home server, trust me when I say it was a nightmare for all involved.

That's over, now that there are strong protections in place to prevent those sorts of attacks.

Also, if you're trying to just use something between friends and family you can always turn off federation (E.g. Have matrix act just like the alternatives where you have one network and are only communicating with local accounts).

So glad I don't have to wake up every morning and purge all remote media from the prior evening 😂

Wish they'd say what was shit about it. Been using Element X as a backup client for years, now - while I'm annoyed at how barebones it is, I always felt it worked quite well for people just trying to get communications going in a basic fashion (E.g. To replace WhatsApp).

Finishing a game helps surprisingly well with morale.

Switching engines is a very big task for a game (of that scale) deep in development, and it's very tedious.

All of its install steps other than docker compose are still containers, or relate to hosting services, or specific managed platforms.

I'm a simple admin who likes to compile, copy to /usr/bin, prep my system user, populate a directory in /etc with all necessary configs, and write my own .service files.

If you like running single binaries in their own Docker instances, more power to you, but it rubs me the wrong way when people try to force that on me.

NB: I'm not above reading a Dockerfile and executing the steps manually, case in point: that's how I build lemmy_server for my current instance... but the Immich steps are waay too involved, with too much of the software expecting some less than sane defaults for me. I went through it once, left a bad taste in my mouth, so I stopped using Immich.

Edit: Just to be clear, here's the installation steps for Photofield. That's what I like to see. "Download a binary, run, config lives at xxx" - delicious. I also don't mind doing a ./configure and make if they want me to - just don't bloat my system with an entire duplicate OS.