Reminds me of the headphone company that got caught stuffing foam into one of their headphones and selling them for less.

It was cheaper that actually making two different models…

No, this is all happening in the browser, there are no other image manipulation tools being called.

I just tested the new release. Consider defaulting PNGs to convert to JPEGs unless they have a PNG-specific feature like transparency. Lots of screenshots are initially PNGs, but not because they need any PNG-specific features. Consider: In a test screenshot, it compressed 3.4% with the default 80% setting and PNG->PNG, but for PNG->JPG, it compressed 84.6%.

No, you can’t prevent open source software being mirrored, nor can you can compel citizens and companies of other countries to stop working on it.

Must be completely unrelated.

In 2004, Munich, Germany led the creation of LiMux and switched the city to that from Windows.

In 2017 they reverted to Windows.

In 2020 they re-asserted the intent to switch to open source.

What’s old is new again.

MCP sounds like a standardized way for AI clients to connect to data sources, the Model Context Protocol.

https://www.anthropic.com/news/model-context-protocol

It sounds like it may compete some with Google’s A2A protocol, which is for AI agent to agent communication.

Both share the same goal of making services easier for AI to consume.

I picture it shattering with force of going over a hard bump.

This was downvoted, but is a good question.

If your account is compromised, the shell init code could be modified to install a keylogger to discover the root password. That’s correct.

Still, that capture doesn’t happen instantly. On a personal server, it could be months until the owner logs in next. On a corporate machines, there may be daily scans for signs of intrusion, malware, etc. Either way, the attacker has been slowed down and there is a chance they won’t succeed in a timeframe that’s useful to them.

It’s perhaps like a locking a bike: with right tool and enough time, a thief can steal the bike. Sometimes slowing them down sufficiently is enough to win.

Do you have a source to cite for the literal 99%?

The top-rated answer to this question on the Security StackExhange is “not really”. https://security.stackexchange.com/questions/189726/does-it-improve-security-to-use-obscure-port-numbers

On Serverfault, the top answer is that random SSH ports provide “no serious defense” https://serverfault.com/questions/316516/does-changing-default-port-number-actually-increase-security

Or the answer here, highlighting that scanners check a whole range ports and all the pitfalls of changing the port. Concluding: “Often times it is simply easier to just configure your firewall to only allow access to 22 from specific hosts, as opposed to the whole Internet.” https://security.stackexchange.com/questions/32308/should-i-change-the-default-ssh-port-on-linux-servers

Yeah, that’s about my top speed on a bike, where I survived some rough road I didn’t have time to avoid. The same rough road on a skateboard would have turned me into street pizza.

For the same reason, I’d like to see shared electric scooters regulated to have a minimum wheel size.

People don’t realize that the smaller wheel sizes are stopped by even smaller things, leading to more crashes as people get pitched off.

I think the small wheel sizes are there for the convenience of the operators, not the safety and comfort of the riders.

Skateboarder here.

The smaller your wheels, the smaller pebble it takes to stop the board and pitch you off. And the smaller pebbles are, the harder they are to see. And the faster you go, the harder it is to see small pebbles.

So, yeah, dangerous. I was thrown off a skateboard hitting a pebble I didn’t see at <15 mph and cut my face open. I’d hate to same rock at 45 mph.

Using a nonstandard port doesn’t get you much, especially popular nonstandard ports like 2222.

I used that port once and just as much junk traffic and ultimately regretted bothering.

The quotes are specifically about early stage startup founders, not employees of huge established startups corporations.

I’m glad to have some competition for the Frost Oven Squoosh, which is being lightly maintained. I opened some issues in the Mazanoke issue tracker for some features to consider.

One feature I started on for that project but got stuck on was implementing a STDIN / STDOUT CLI workflow.

https://github.com/frostoven/Squoosh-with-CLI/issues/10

As I said there, the goal was a workflow where I take a screenshot, annotate it, optimize it, copy it and paste it into my blog… without creating any intermediate temp files.

At least on Linux, all the the steps of the pipeline are solved, except for a CLI image compressor that could accept an image STDIN and produce a compressed image on STDOUT.

Sounds like an oversight. Consider filing a bug with them.

https://github.com/frostoven/Squoosh-with-CLI

Nice. I use Squoosh for this, which is also free and runs in the browser.

https://squoosh.frostoven.com/

Https give you encryption in transit. The files you view will be accesible to the host.

Same idea with email.