I was in the same place as you a few years ago - I liked swarm, and was a bit intimidated by kubernetes - so I’d encourage you to take a stab at kubernetes. Everything you like about swam kubernetes does better, and tools like k3s make it super simple to get set up. There _is& a learning curve, but I’d say it’s worth it. Swarm is more or less a dead end tech at this point, and there are a lot more resources about kubernetes out there.

The early twenties intermediate dev on my team was explaining the other week that if you remember a time before smartphones and broadband, you are old

I personally am familiar with 2 organisations with millions of dollars in annual revenue that deploy critical line of business applications like this in 2024

!bertstrips@feddit.de

Very NSFW

They are, but I think the question was more “does the increased speed of an SSD make a practical difference in user experience for immich specifically”

I suspect that the biggest difference would be running the Postgres DB on an SSD where the fast random access is going to make queries significantly faster (unless you have enough ram that Postgres can keep the entire DB in memory where it makes less of a difference).

Putting the actual image storage on SSD might improve latency slightly, but your hard drive is probably already faster than your internet connection so unless you’ve got lots of concurrent users or other things accessing the hard drive a bunch it’ll probably be fast enough.

These are all Reckons without data to back it up, so maybe do some testing

Weirdest episode of binging with babish

Neurosyphilis

Sounds like a great idea - I suspect the biggest obstacle will be finding someone at the home who is confident enough in what to do with it to be willing to accept it.

I’ve run into similar issues with schools where they are hesitant to accept donations of things like that because they don’t want to be saddled with equipment they don’t know how to use and maintain. Maybe worth seeing if you can raise a bit of money for a second hand Xbox or something?

Weren’t the shit balloons retaliation for the south sending balloons to drop propaganda leaflets?

Pretty much - I try and time it so the dumps happen ~an hour before restic runs, but it’s not super critical

pg_dumpall on a schedule, then restic to backup the dumps. I’m running Zalando Postgres in kubernetes so scheduled tasks and intercontainer networking is a bit simpler, but should be able to run a sidecar container in your compose file

If you figure it out, I know several companies that would be more than willing to drop 7 figures a year to license the tech from you

Dude wouldn’t know what to do with a condom.

My theory is it’s not dementia, it’s neurosyphilis. Party like it’s 1825!

git-annex maybe?

Yeah, they are mostly designed for classification and inference tasks; given a piece of input data, decide which of these categories it belongs to - the sort of things you are going to want to do in near real time, where it isn’t really practical to ship off to a data centre somewhere for processing.

Dealing with this at the moment - in an org that’s been pretty lax at writing anything down about what and why as far as internal software goes, trying (with support from C-suite) to get people to actually write up any amount of detail in their requests is like pulling teeth.

I tend to take that position as well; if it’s not defined, I get to define it. If I ask for feedback or review and get silence, that means you approve.

Because accountants mostly.

For large businesses, you essentially have two ways to spend money:

• OPEX: “operational expenditure” - this is money that you send on an ongoing basis, things like rent, wages, the 3rd party cleaning company, cloud services etc. The expectation is that when you use OPEX, the money disappears off the books and you don’t get a tangible thing back in return. Most departments will have an OPEX budget to spend for the year.
• CAPEX: “capital expenditure” - buying physical stuff, things like buildings, stock, machinery and servers. When you buy a physical thing, it gets listed as an asset on the company accounts, usually being “worth” whatever you paid for it. The problem is that things tend to lose value over time (with the exception of property), so when you buy a thing the accountants will want to know a depreciation rate - how much value it will lose per year. For computer equipment, this is typically ~20%, being “worthless” in 5 years. Departments typically don’t have a big CAPEX budget, and big purchases typically need to be approved by the company board.

This leaves companies in a slightly odd spot where from an accounting standpoint, it might look better on the books to spend $3 million/year on cloud stuff than $10 million every 5 years on servers

Seems pretty reasonable. At the end of the day people have to eat, so projects like this either trundle on as hobby-and-spare-time projects for a few years until people get bored and burnt out, or you find a way to make working on the project a paid gig for the core people

Yeah, directors should be getting charged with manslaughter. Their negligence caused a death, they should be getting charged with a crime, not given a bill

Yeah, traffic coming from an ASN that isn’t assigned to a residential ISP would be a pretty good sign of shenanigans