koffiezet

No Belgium either, which I would have expected since tax rates here...

It however shifts a lot of the complexity of building the application to the distro maintainer, or a software maintainer has to prioritize for which distribution they choose to build and maintain a package, because supporting them all is a nightmare and an ever shifting moving target. And it's not just a distribution problem, it's even a distribution version/release problem.

Look at the hoops you sometimes have to jump through or hacks you have to apply to make something work on Nix, just because there is no standardization or build processes assume library locations etc. And if you then raise an issue with the software maintainer - the response is often "but we don't support Nix". And if they're not Nix/Nixos users, can you blame them?

If you've ever had to compile a modern/recent software package for an old distro (I've had to do this for old RH distro's on servers which due to regulations could not be upgraded) - you're in a world of pain. And both distro and software maintainers will say "not my problem, we don't support this" - and I fully understand their stance on that, because it is far from straight forward, and only serves a limited audience.

When interviewers use LLM gargbage to filter out participants, expect candidates to do the same.

> Just curious. In Sweden the average devops salary is around 60k.

Well there's salary, and total employee cost. Now sure how it works in Sweden, but here in Belgium it's a good rule of thumb that an employer pays +- 2,5 times what an employee nets at the end after taxes etc. So say you get a net wage of €3300/month or about €40k/year ends up costing the employer about €100k.

I'm a freelance devops/sre/platform engineer, and all I can tell you is that even for long-term projects, my yearly invoice is considerably higher than that.

I used vagrant in the past for this, but that's years ago.

This is something I was actually looking for a while ago and settled for a linuxserver's docker image running vnc and sqlitebrowser to inspect some databases on my homelab, which felt like an unsatisfying solution - this looks a like a much nicer, better and more lightweight solution.

Not if they require a certificate containing the serial number/imei/... + a nonce provided by Apple, signed with a private key/certificate stored in the secured enclave, loaded into the device when it's manufactured.

> Somehow I think this one is not Sony's fault entirely.

Sorry but if you allow your platform to sell 3rd party content, you better have some consumer protections built-in in your contract with that 3rd party in case of such a scenario.

Sure, but the communication channel between the attester and the client which it needs to verify/attest is pretty much undefined?

What unclear to me is how the actual verification by this attester would happen. Somehow the attester, which is also a remote service, verifies your device? Are there any details on how that would happen specifically?

I think their main problem is that regarding the i3 design, they are pretty much the only-ones contributing to improvements, I mean - when was the last time the community (or another manufacturer) actually contributed anything useful to the core HW and electronics design? The 3d printing space has massively changed in the last 10 years, where initially a lot of the HW improvements came from the hobbyist RepRap community. Now they come from a single company which stems from that community, and which is spending money on R&D.

On top of that, people still building an i3-design printer from scratch is rare, the hobbyist design community has moved on to the Vorons, which means pretty much all printers with this design are from companies with zero community interaction, profiting from the Prusa investments. So I get why they're not happy.

The only real comparison you have with Prusa is the much less popular RatRig - which is still an opensource design afaik, but I'm not aware of any clones of those.

> beyond allowing others to send/receive messages

Just publishing the specs will not allow anyone to send/receive iMessages. It's built on a closed loop CA / certificate system.

Remember that Steve Jobs actually announced on-stage it would be an open protocol without actually discussing that with his engineers? The architecture is designed to be closed from the get-go, and opening up the iMessage ecosystem in it's current design is simply not possible without giving 3rd parties considerable access to Apple internals, affecting a ton of stuff beyond iMessage, and pose serious security risks.

Could Apple re-design a messaging system which would allow this and roll it out transparently to all it's users? Absolutely, but that would require a ton of engineering work, and won't be there tomorrow.

> They were using CentOS for no cost previously and have switched to another no cost RHEL rebuild (Rocky).

Since they involved CIQ, I'm pretty sure they are now paying support for Rocky, which, if you read the article, was clear they didn't mind paying for. It was the per-cpu subscription that was not realistic in their business model.

> doesn't know that his core infra team just wrote something in Rust

Sorry but that is something he should know. That directly affects technology radar and roadmap, HR and a bunch of other stuff.

While it might suck for some people, the 10k message limit was always there, so if you wanted to keep history - why the hell would you be on slack?

And the people here shouting matrix and "don't go to discord" have never tried to push more non-technical people onto it. It starts with differently named apps on desktop and mobile (sure there are a few multi-platform clients). But then the naming? Back in the old days, IRC for a lot of people was not IRC, but mIRC. Why? Because the icon they had to click had that name. Thank goodness it at least resembled the name of the actual thing they were connecting to, where they could go "IRC? you mean mIRC?".

If I now tell someone to go on matrix - they don't have a matrix app on their phone, Mac or pc, and I have no idea which-one it'll be. Branding and name recognition is important here.