I did not vote for this. Some of my neighbors voted for this because they were pushed over the edge by inflammatory social media algorithms, some stayed home for similar reasons.
Corporations absolutely have an effect on all of this, you can bet they'd save time and money by focusing their efforts elsewhere if they thought it was pointless.
Unfortunately, this [0] cancels out everything ten-fold. The owner of the website is boosting the content of himself and the people he supports. This did not happen in the old twitter - not even close.
The name of the company certainly does raise eyebrows. And from what I 'member from back in ye day, the Musk controversy actually helped them to raise users in the end because everyone and their dog was talking about Musk and him assuming getting hit by a "ligma" joke. That thing was all over the Internet.
Basic arithmetic plus iteration is Turing complete. CSS has basic arithmetic but not iteration.
Some people have already claimed it's Turing complete by making the user hit tab and space to copy data between iterations, but I wouldn't listen to them. That copying role is simple but it's not negligible.
If we can introduce delay in the circuit it would be trivial to build FFs from Boolean-complete gate sets, thus sequential elements with memory. But AFAIK CSS if() can't introduce delays.
It lacks a usable form of pure-CSS recursion (which was intentionally excluded in this implementation) but that's not as big a problem as one would expect for a lot of practical things.
I’m going to assume this is a joke. However, if it’s not a joke, no. We as a community have gone to great lengths to use responsive design over the past few years. There are still styling cases for complex elements that can’t be implemented without JavaScript. This is just an additional step of the journey to allow intermediate styling for complex cases.
If anything, it should enable (minor) expansion of noscript!
Id actually like to redact that prior message and think further, here. We already have information egress thru URIs, with some amount of “protection” via CSP. But I didn’t think of other types of attack vectors at length. Someone above remarked that this is just a general form of conditional, which perhaps unlocks new vectors. Im always surprised by CSS so i should slow down and keep an open mind :)
Looks good! Did you build your own text editor? The markup doesn't look familiar. (Would recommend grabbing one off-the-shelf that handles cross-paragraph selections and concurrent edits, will save you a world of pain)
I've thought about this problem myself a lot. I don't have a great answer.
The easiest thing I can think of is just grab https://ankiweb.net/shared/info/369908962 , and schedule everything you've already seen in WaniKani for immediate review, heavily relying on pressing easy to try to get things into a longer interval if you already feel you know them. This probably works best if you're relatively low-level on WaniKani. You might be able to use the WaniKani and Anki APIs to automate this to some extent.
