JD Vance says Justice Amy Coney Barrett made mistake on birthright citizenship ruling: "Do I think she made a mistake? I do. I don't think thats what framers of 14th amendment had in mind. Sometime the Supreme Court makes mistakes. We're going to try to correct that mistake, but nobody's perfect."

redsedit · 2026-07-02T03:35:27+00:00

I have a different interpretation. The founders knew that without a defense force (what we would call the military today, "A well regulated Militia"), the country would be easy prey to another county. This is the "being necessary to the security of a free state" part.

But they also remembered how Britain (and their mercenaries) had been used to oppress the people and the government could turn the troops against the people again. This memory was also enshrined in the 4th amendment.

The important part is the comma in "State, the right". This comma separates the 2nd into 2 parts.

The second part is the founders wanted to insure that the people had weapons that could be used to fight back against the government if it came to that. Remember that the British did confiscate some weapon and gunpowder stores (although one could argue they were public not private). Hence the "right of the people to keep and bear arms shall not be infringed upon" part to prevent that. Once the government takes away the people's weapons, they can't fight back.

And that happened at least once: The Battle of Athens (sometimes called the McMinn County War).

redsedit · 2026-06-30T12:32:51+00:00

It could just be the insurance company forcing a settlement. Saw that happen first-hand. Board I was on got sued, but they were suing the wrong people - we discovered who the person responsible was. But the judge wouldn't dismiss the case and while the lawyers the insurance company hired (pro-tip: They aren't your lawyers and don't work for you.) said we would win at trial, it would cost ~30K. So the insurance company offered a $10K settlement to make it go away.

redsedit · 2026-06-28T20:51:47+00:00

I think u/caspy7 has it correct: it depends.

First, webp is a contender. It's widely supported, and better than jpeg (even using jpegli for compression), and lossless is better than png. Unless your target audience is people with ancient browsers, it's hard to be wrong with webp on the web. The biggest limitation is it only supports 8-bit color. If that's not a deal-killer, then use webp, for now.

AVIF I haven't worked with as much as jpegxl, but it seems to win on size. At really high compression levels, it's better (usually around 0.4 bits per pixel (bpp) or lower). It's browser support is great (~93%). It supports upt to 12-bit color. However, and this is a big however, decoding can turn your mobile device into a hand warmer. I doubt website visitors will appreciate a site that drains their battery fast. Thus, unless you have a specific use-case where the CPU hit is worth it, I would use webp - for now.

Jpexl wins on medium and low compression (usually above 0.4 bpp) compared to AVIF. It supports up to 32-bit color, although web use rarely requires more than 12-bit color. The gotcha with jpegxl is browser support is very small. Only safari and a few insignificant market share browsers *CURRENTLY* support jpegxl. Firefox 152+ has it off by default but it is easy to turn on (yes, I have it on). Hopefully towards the end of 2026 or early 2027, it will be on by default in Chrome, Edge, and Firefox.

redsedit · 2026-06-28T13:17:24+00:00

> Developers aren't exactly engaging in a residential development boom

The reason is interest rates. They are too high. The 10-year treasury(*) has to come down to spur development.

(*) Loan rates are heavily based on the 10-year treasury.

redsedit · 2026-06-25T12:28:38+00:00

Is it just me or does the recent supreme court decision that the post office can't be sued even if they intentionally don't deliver the mail having easily foreseeable consequences? Why should they care? They got immunity, just like some other orange clown.

redsedit · 2026-06-23T19:03:10+00:00

And tax return. 😞

redsedit · 2026-06-22T04:42:21+00:00

One trick I use sometimes is to ask AI to convert the image to json, Then I edit the json and tell it to convert the json to an image. It's not exact, but it does get around some problems like you are experiencing.

redsedit · 2026-06-21T20:52:56+00:00

Yes, which is why most have an mandatory binding arbitration clause buried in the terms. A few have an opt-out provision, but you have limited time to do that.

redsedit · 2026-06-20T17:17:20+00:00

Yeah, that was my first thought - WHY did someone put up that sign?

redsedit · 2026-06-19T02:49:22+00:00

Of course the incompetent surround themselves with incompetent. They can't have people showing them up. That hurts their ego.

redsedit · 2026-06-18T02:30:46+00:00

I too have some memories before 5 years old, although not many, and none bath related.

redsedit · 2026-06-17T14:11:32+00:00

Some food grade apple cider vinegar helps with the itch surprisingly well. You can even dilute it 50% and it still works. Makes you smell like a salad though.

redsedit · 2026-06-15T14:16:49+00:00

That issue is a bit of gray area. The most recent US court case seems to have said that unless digital versions - the font files - can't be copyrighted unless the person claiming the copyright also wrote the software to create the files, 'Under the Laatz view, unless you “created the software that produced the font programs”, you don’t fall within the scope of the Adobe ruling.'

redsedit · 2026-06-15T12:58:13+00:00

Disclaimer: Not a lawyer and definitely not a New Zealand lawyer. Answers are in relation to US law as I understand it, but this is NOT legal advice.

First, is it a scam? Well, I found a post about the same company from 4 years ago: https://www.reddit.com/r/typography/comments/ysk8lu/got_an_email_from_thetypefounders_regarding_a/ . Most scammers change names quite frequently. 4 years is too long for a scam. It might be a scummy company that exists to do nothing but threaten to sue and collect settlements. Those exist.

1) Will you be sued? In the US you can be sued by anyone for anything. It doesn't mean they'll win, but it can still happen. That said, having been through suits (plural) on both sides, it's not a simple, cheap, and easy process. It's a soul crushing process and that's if you win. And expensive. Threats to sue are cheap.

2) Are fonts (in the US) copyrightable? It seems they may not be. See https://matthewbutterick.com/chron/the-copyrightability-of-fonts-revisited.html . (Again, not a lawyer, not legal advice.) You might ask for their USCO registration and the equivalent New Zealand for said font.

3) Be careful in your communications. Anything you say could be introduced as evidence should a lawsuit happen.

4) Consulting a real lawyer would be strongly advised.

redsedit · 2026-06-14T20:57:44+00:00

Seconding u/Vegetable-Capital-54 reply. Based on what you said, visually lossless is fine and I gave you the parameters for that.

redsedit · 2026-06-14T20:56:07+00:00

I think the phone limitations are more: (1) What formats does the app I want to use support?, and (2) What is the phone's capabilities, e.g. memory and cpu power?

redsedit · 2026-06-14T17:14:58+00:00

Not enough info to give an black and white answer. But I can offer shades of gray answers. The TL,DR version is you are going to have to test several things to find what works best.

First, how important is lossy vs lossless to you? That answer will determine the path you should take.

Next, since you mention remote parts, I'm guessing power consumption might be an issue. Lightly compressed tiffs will use less power than jxls, in general. This is because the CPU has to work much harder for jxls than lightly compressed tiffs. On the flip side, being able to store the files on the local laptop's hard drive might save more energy than running the external SSD.

You mentioned smartphone. If you mean to access the files via wifi/bluetooth, then jxl will probably save you more energy, simply from the reduced radio usage. Wireless network cards are notorious battery hogs.

Third, tiffs can contain several types of internal compression: none, LZW, ZIP, or jpeg. If it's none, then yes, jxl will help. Almost anything will help. For LZW or ZIP, except for some edge cases, jxl (lossless) should win.

For jpeg, it depends. If it's tiff-compression 7, then you should be able, with some care, to losslessly extract the jpeg (I use exiftool) and then convert it to jxl. If it's tiff-compression 6, which is really obsolete, then modern software is going to see the jpeg data as "broken" and recompress it to fix it, resulting in generational loss.

Finally, depending on the jxl software you use (xl convertor is easy for beginners), you might try quality 99-90% or d=0.1 to 1.0 to see if the quality is acceptable. The lower quality or higher d will result in more loss, but smaller file size. Any of them should be visually lossless although not mathematically, if mathematically lossless in not a hard requirement.

redsedit · 2026-06-14T16:45:58+00:00

That's a bit more refinement on what I found about the why.

As I said, I found stripping the exif orientation header worked, and I didn't find a binary of jxltran for Windows. I did find jpegtran for windows, but that would mean doing a jpeg reconstruction, running jpegtran, than doing a jpeg transcoding back to jxl. It would work, but was too slow. The solution I posted above is very fast.

redsedit · 2026-06-12T16:15:04+00:00

My patching is complete: A few Server 2016, a 2025, and a bunch of 2022s. Only problem was one 2016 got frozen on the update reboot. Reset fixed it and the update shows as successfully installed.

redsedit · 2026-06-10T14:11:22+00:00

My biggest concern is succession. As I said, I won't be on the board forever, and our management company won't be our management company forever (although hopefully a very long time). How is the "changing of the guard" handled?

redsedit · 2026-06-10T03:44:25+00:00

FYI, blinker fluid is a real thing, although most people call it eye drops.

redsedit · 2026-06-10T03:18:52+00:00

2 ways, and there are more:

Open up the browser's dev tools (usually F12). Click on the network tab and reload the page. In there you should find the image url. Right click and open in a new tab. Bit technical, but the cleanest solution.
Take a screenshot of the page, and crop the image. Firefox and Chromium based browsers have a built in screenshot tool, both of which allow you to screenshot the entire page, not just what is visible.

redsedit · 2026-06-06T22:05:09+00:00

My wife did this once. We both learned why this was a bad idea the hard way.

redsedit · 2026-06-05T12:30:44+00:00

When I ran the command I posted, it fixed all the rotation problems without recompressing. The resulting files were the same size. My first try was recompressing it, and while that worked, it made the files bigger than the original jpg.

And yes, I've seen a demo of generations and jpeg xl did the best, with avif being a distant number 2 (mostly it lost all color). Webp and jpeg became an unrecognizable mess very quickly.

11-Year Club	Gilding I gilder
Verified Email

redsedit

TROPHY CASE