How‘s that possible? JPEG-XL stores image files, right? But RAW files are not images in the same sense. They haven‘t even been demosaiced. Or are Apple RAWs different?
Edit: I should have googled. apple‘s ProRAW does this, which isn‘t a RAW file in the classic sense.
I had a hard time understanding what the author is trying to accomplish. The necessary context apparently is spread across the intro and outro:
> Because of that, later PalmOS versions offered two different encodings for storing color bitmaps: 8 bits palette bitmaps, capable of using up to 256 simultaneous colors
> to perform complex bitmap rendering using multiple, incompatible color palettes
It seems the palette is not per-bitmap but rather per-device, hence the need to convert.
I think the RAW philosophy is starting to show its age. RAWs were only ever intended for the manufacturer‘s first party software (AFAIK). But that software is usually junk and supports few platforms (none support mobile).
I think the sweet spot for both the camera manufacturers and photographers are JPEG XL and other newer, standardized formats. They allow the camera to „bake in“ the secret-sauce color science while retaining headroom for editing thanks to 16-bit channels and such.
What I would like, but haven’t found yet, is a cheat sheet on what up to date encryption method or algorithm one should use for whatever need. A kind of requirement -> algorithm dictionary.
Like, I need to authenticate that a client is a known identity. What algo? How to use it? What to avoid? I need to sign a message or document. How? I need to verify said message. How? I need to store passwords. How?
I know some crypto, but discovering and learning about them is a bit of a pain. For how important crypto is, you‘d think someone would have bothered to teach developers how to choose and deploy these algorithms properly.
It's not new, and some people would disagree on some minor elements -- but a good place to start was regularly this blog from approximately Matasano/NCC Group members, called Cryptographic Right Answers [1]. It's very clear, gives straight forward answers in clear fashion -- and with multiple opinions often aligning.
It was updated a few times, I wonder if the equivalent exists for PQ?
Edit/Update: Found the PQ one @ [2], definitely check it out!
Maybe I'm mis-remembering, but perhaps the most controversial element was the regular recommendation of AES-GCM. It certainly has excellent security properties, but also a certain brittleness re: nonces.
I think this is a primary reason why there is no real "cheatsheet" for this stuff. The application of a given algo (and even what types of inputs you provide) are heavily dependent on the detailed specifics of your use case and how you apply them
> Like, I need to authenticate that a client is a known identity. What algo?
In this case, you're asking the wrong question.
When people say "what algo?" in such a context, the answers will be flavored as "Ed25519 vs secp256k1 vs RSA-PKCS1v1.5" when you should first be asking "what level of abstraction am I dealing with?" and "what are the constraints?"
Like, maybe "algo" isn't even a relevant concern.
If I were designing a simple token-based auth scheme today, I'd reach for PASETO. Unless I need interop with a third-party provider, who almost universally use JWTs and prevent me from having any say or choice in the matter.
With PASETO, you don't need to know, or even care, about "what algo?" You only need to consider mode, which is more of a use-case question.
I cannot imagine proactively writing a cheat sheet for every possible use case. You might be tempted to use AI to solve this problem on demand, but the cost of a hallucination here is pretty high.
If you find yourself regularly asking this question, I'd recommend just hiring a cryptography consultant.
If your needs are this simple, you may be better served by an opinionated crypto library like Monocypher [0] or libsodium [1]. Just look at the latter's FAQ page and you'll see they're taking your approach targeting developers, not cryptographers.
They'll provide you one blessed algorithm for every primitive with secure alternatives if your use-case demands them. XChaCha20-Poly1305 for encryption, EdDSA for signatures, X25519 for key exchange, BLAKE2b for a hash, Argon2i for a KDF.
I remember using those pre-cloud versions. I loved them. Sketchup was so intuitive (as a 3D modelling noob) it was ridiculous. My tool of choice for making 3D levels for my various OpenGL projects.
I tried to do some rudimentary modelling with modern day Blender and failed. It‘s quite the juggernaut to learn.
What software today do people recommend as an alternative to Sketchup? Is the cloud version any good?
> What software today do people recommend as an alternative to Sketchup?
onshape (web; free to use unless you want to protect your designs) and fusion (autodesk; free license available) are both really popular right now. they work differently than sketchup. i never really made friends with sketchup but the parametric modeling system used in fusion and onshape clicked with me and i really enjoy using them.
I remember running Sketchup for the first time. I had zero experience but in less than 20 minutes I was drawing large complicated machinery, tractors, buildings.
They made a 3d drawing application without a learning curve O_O
This unlocked memories I forgot I had. Not only playing these games, but Flash introduced me to gamedev. I can clearly remember struggling in Actionscript, trying to get collision detection and resolution working. I never got it to work properly lol.
By the way, if anyone wants to relive some old flash games/movies, there is https://ruffle.rs/, an open source Flash implementation. It's great!
Man the Flash era, and the overall vibe of creativity on the internet back then (hey it was only 20 years ago), was the kind where you could feel a limitless potential for the future, where everyone would be awesome.
Then it all congealed into the tentacles of 4-5 corporations and now we're forever stuck in their "How do you do fellow kids" cringefest..
AI also ha[s/d] potential, but it's already getting crippled at birth by corporate idiocy and lawsuit fever.
This reminds me of my own struggles in locating my country in various dropdowns. Sometimes it‘s the trivial to find Austria, but sometimes Österreich under O and other times Österreich under Ö (sorted to the very bottom). Collation is fun!
I’ve noticed that South Koreans often use the term “Korea” to refer to their country, and I’ve always been curious: are they referring to all of Korea, or only the south?
For example, which of these statements would you be more likely to use colloquially?
(a) Korea’s population is about 80 million, or
(b) Korea’s population is about 50 million.
The term could refer to either South Korea or Korea as a whole, depending on the context. As for your example, I think people would agree with (b) because when you're talking about populations people implicitly assume we're talking about a country.
On the other hand, people say "Korea's history reaches back thousands of years," and obviously here "Korea" means Korea as a whole (the country of South Korea wasn't founded until 1948!).
It gets extra confusing for Koreans because North Koreans use a different Korean word for "Korea" (either North Korea or Korea as a whole) - they are from two different historical names. So we can't even agree on how to call ourselves. ¯\_(ツ)_/¯
> I think people would agree with (b) because when you're talking about populations people implicitly assume we're talking about a country.
Yeah, that makes sense, but the confusing part for me is that, at least if my understanding is correct, the South Korean government doesn’t legally recognize the partition of Korea. So they think all those 80 million people are rightfully citizens of their country (that is, the Republic of Korea), even though 30 million are temporarily subject to an illegitimate regime. But I’m not sure if people actually think like this in practice.
Well, yeah, constitutionally speaking, Republic of Korea is the only rightful government with sovereignty over the whole Korean peninsula (and if you go across the border, you will here the same in reverse, except they recently decided to change their stance to "there are two countries and we're not related at all!").
But everyone understands that this is a legal fiction. Despite mutual hostility, the two Koreas are somewhat relaxed about interpretation: for example SK doesn't object to other nations establishing diplomatic relations with NK, and vice versa.
Depending on who you ask, you'll hear different views on how to reconcile the law with reality, ranging from "there is only one rightful government, and a group of commie rebels we should destroy" to "we should accept that there are two different nations" to "South Korea is but a colony of American Imperialists!" But anyway, everyone accepts that practically there are two countries, so when we're talking about any contemporary matters, we're usually just talking about South Korea. (Unless we're specifically interested in North Korea.)
Edit: I should have googled. apple‘s ProRAW does this, which isn‘t a RAW file in the classic sense.
reply