Parallel Desktop

There are several FOSS alternatives. All of them are more popular that Parallels.

Nobody likes Adobe, nobody wants to work with Adobe. Nobody can avoid Photoshop. That’s just the world we live in and I don’t like it.

This sounds like Stockholm syndrome. You are just too familiar with Photoshop, so using anything else is hard and less efficient.

In photography there is this mantra about “the most important part is right behind the camera”. A good photographer is not a good Nikon user, or good Canon user. A good photographer can deliver decent pictures with a potato camera if needed.

Sure, a potato camera is less efficient for any work that an actual good one. So it’s good to invest in a good brand. But the point is: if you are not capable to make average results with a potato software, the problem is not in the software.

I also assume it’s an expired certificate.

See, this is what happens when certificates are not renewed automatically.

The article says the projectos are discontinued. That’s probably the reason no one is monitoring these certs.

Another glorious benefit of DRM.

There are two kind of programming languages:

1. The ones everyone complaints about
2. The ones nobody uses.

Excelent example as it implies the damage to sovereignty it takes.

You know. Pros and cons…

Ecuador and Puerto Rico already did it. Panamá did something similar.

I totally understand the initiative. Corruption can be so damn high, that you trust gringo central bank more than any institution of your own country.

edit: typos

In Chile I recall Microsoft sending a notification to my former worplace because someone used torrent to download a game from inside the company network. That person didn’t notice that all traffic was being routed to company’s VPN hosted in MS Azure.

ISPs don’t give a shit. The goverment has laws against piracy that are never applied (you know: Southamerica, the lawlessness). But gringo companies do care.

My advice is to avoid Google, MS and the big tech to follow your pirates activities. They may suspend services to you, or notifiy some local authority.

Use a different browser or machine for your big tech interactions, and you’ll be fine.

Edit: typos.

more than 10. that’s a lot of softwares!

OP: posts about any modern problem

tankies:

chinese proverb: everything is tasty if you fry it enough.

beehaw admins: we need to defederate some instances to protect our users from trolls and bigots.

beehaw users:

I didn’t understand the DRM part neither.

Sorry, folks. Using cmalw-lib is now deprecated.

Cool kids are using systemd-malwd

Deny Reason: ok

lol

Companies need to conduct cyber risk assessments before a product is put on the market and throughout its lifecycle effectively manage its vulnerabilities, regularly test it, and so on. Products assessed as ‘critical’ will need to undergo external audits.

I have not read the proposal. Legal language makes me want to rip my own eyes off.

The only winners I see are those security auditors and similar providers.

Privative corpos from USA and China will arrive with all “security assesments” and “auditions” in place, and still have backdoors lol

The mighty kingdom of Biscayland.

we are the best country of Chile.

I legit took a few seconds to figure it out. I was like: what those gringo politicians are doing? measuring temperature?

On a completely unrelated side note: I like to see paralellisms of SOLID principles of OOP development and system administration.

A container may have one responsability. Or a service config (like nginx) may be closed to modifications but open to extensions, to avoid some automated client breaking elsewhere, etc, etc.

Sometimes I like to thing about system administration like some kind of very high level development.

• For kuberentes stuff, I use external-secrets-operator. It can be paired with selfhosted stuff, like Hashicorp Vault.
• For machines, disk encryption LUKS, and then files in plain text, with minimal permissions: mode 400.
• For my laptop, keepass.

In my opinion, for home selfhosted stuff you don’t have to go for complex solutions. In the industry, the problem is that secrets needs to be served to different systems, by different people, with some kind of audit logs. Unless you are working with lots of people, environment variables are OK. You github/gitlab may have all scripts with variables, and your disk may have a .env file with mode 400. If you make any machine or container with a single responsibility, there should be no secret leaks among them.

For example, let say your wordpress instance gets pwned. It should only have its needed secrets (like its db credentials), so your wikimedia instance is still fine.