flaunf221

It's a resin 3d printer. It uses toxic resin, you really don't want it working near humans without proper ventilation setup, you need to wear gloves, will need alcohol for cleaning prints.

And then unless you plan only on printing already prepared models you will need to learn how to user slicer software and maybe learn to model things yourself.

It is a product for enthusiasts by nature of how it works.

More like they were not able to find a pretext to sell it for more.

I can open my local store and will see shitty 8/128 Android tablets for less than 150 euro. If memorypocalypse was the main reason for pricing new ipad mini as it is, the budget tablet segment would be completely dead because manufacturers just wouldn't be able to afford memory at all.

> The reality: RAM/Chip prices are way, way up. The starter iPad mini is $700.

This has tiny 128 GB of storage and unknown but obviously not too high amount of RAM. At best 16, but probably less.

That's just Apple beeing greedy as usual.

> even if that means capturing too much

People streaming things mights disagree.

I see now from another comment you thought about denial of service for service that leaked key. And I thought about mass leak resulting in DDOS onto API provider. Wrong guess from me.

Not any more than any other public endpoint service exposes. This revocation endpoint can be protected by auth too. Use API key that you're revoking in auth.

And I believe it is far less than what could be.

Too many OSS projects die because authors are too afraid to tell demanding users in which direction they could proceed and instead burn out.

> best response is to just communicate you are not fixing X

You mean the response that was already written in a previous message and the response user decided to ignore so they can pester more?

Tried it too, it still had judder as all other clients I've seen. I think it's either server software problem or maybe all clients fail to do this properly.

Reading this causes embarassment from author's helplessness.

> I first tried GPT-5.6 Sol with reasoning effort set to Extra High. It wrote code to connect to the Kindle but couldn't resolve an error that prevented it from storing data on the device. Then I tried Fable 5.1 and Opus 5.5, but Anthropic's cybersecurity safeguards blocked each attempt after two prompts. Finally, I tried GPT-6 Astra with reasoning effort set to High. We were able to jailbreak the Kindle.

"We were able to".

It takes a modern AI human and 4 LLMs to do something that could be done by googling "kindle jailbreak" and following instructions - they have to be performed on Kindle anyway.

Back in the day 1080 was top of the line. For couple of generations now it's xx90 lineup.

You could say that there was Titan but in practice they were not seriously considered. At least for gaming.

I've heard about it. I didn't try to look very deep it. They claim they started from scratch and they still made hjkl.

jkl; would get you movement over home row without moving hand/fingers at all. ijkl would get you movement without involving pinky and some people like that.

If you have (and I do) column-staggered ergonomic keyboard - meaning columns are shifted according for length of your fingers - hjkl makes you move fingers to columns that are slightly off.

I don't see a single objective benefit for choosing hjkl on its own. Yet it's still there and I don't take "they did in vi" as valid for new editor. They could make alternative scheme for vi-comers, but as main idea again?

What you mentioned - g-h and g-l - are definitely more consistent than what vi did.

> Everything else has a meaning-based mnemonic, and until I read your post I hadn't ever thought about their position

My point is that position is the primary thing that's important for an editor when used for a long time. Your hands and fingers move in physical space, not over alphabet. They get tired and maybe get repetitive strain injuries over real movement.

Mnemomics way of setting up keyboard layout (or rather typewriter) would be to put everything in alphabet order. But we quickly realized that it's not a good way. `d` is where it is because according to (imperfect) research it's a common letter and so in QWERTY layout this letter should be on your home row.

Putting A-something on `a` because the word starts with `a` is not a long term design. Considerations should be based on usage. How often is this used? Put it closer to home row. Is it designed to be often used with another command? If often, those two probably shouldn't be on single finger. And so on.

There is argument for easier start - except that I said already - modal editors are unusable without reading docs first, so that argument doesn't really hold.