ulrikrasmussen

You should consider scrapping him also.

I think you mean MitID, but yes. I have tried going through the process of getting a new MitID at the citizen service desk, and the questions I am asked to verify that it is me are almost all family related. If the leaked data reveals things like parent/child and spouse relationships then that process is cooked.

Only If you attribute every accident to "because they were on drugs"

Agreed. It's a major pain in the butt, and I wish I could just ship an int64 back and forth and not have to deal with mapping it to a calendar.

Really fun idea. Some immediate feedback:

* Moon is moving too fast, has too much influence.

* Movement breaks the game as you can just move up to the opponent.

* The timeout is frustrating. I can line up a shot that actually looks like it is going to be a direct hit just to have the game remove it as it starts descending towards the target.

Ah, yes, you are right! Forgot about those two details

The SQL standard is unfortunately really horrible when it comes to handling of time. The type `timestamp` is not a timestamp at all because it doesn't encode a unique point in time, it just stores a date and a time which has to be interpreted relative to a timezone. It should be called "datetime".

Moving a Java Instant back and forth between a database is also a surprisingly difficult task to do right, and it doesn't help that JDBC is just handling it completely wrong if you use its setTimestamp/getTimestamp methods. Not because it is a bad design with footguns, but because the implementation is just plain wrong and will corrupt your data if you deal with instants whose calendar date is far enough in the past due to it using the legacy date/time API which switches to the Gregorian calendar for dates in the past.

The name `timestamp with time zone` is also misleading because it doesn't actually store a time zone, it stores the number of seconds since epoch like a java.time.Instant (although at a different resolution). The "with time zone" part just refers to the textual format you denote the values in which includes the time zone after the date/time part to uniquely identify a timestamp, but the time zone is thrown away and not stored after the value has been parsed. This is different from e.g. `ZonedDateTime` in Java which will actually store the offset and therefore corresponds to a pair of (Instant, TimeZone).

A combination of different ones, sometimes close to what you know from the clearnet, i.e. click pictures that match a description. For the proxy defeating one, the server can send you a picture of the real .onion address where some letters are blanked out, and with noise added to it to prevent it from being solved by the proxy. You then have to enter the blanked out letters from the browser URL.

This can of course still be defeated if the proxy URL receives very few requests and just have a human in the middle to solve the CAPTCHAs. But it does make the attack non-automated.

This is a good question. Off the top of my head:

* Less crime because people who are addicted to drugs do not have to raise instant money for their next fix,

* Getting open, visible drug use off the streets and into a controlled supervised setting (this is not strictly part of safe supply though, but an orthogonal related service),

* Making drug use safer for the users by ensuring quality and consistent strength. Fentanyl, orphines and nitazenes are killing lots of people, and they exist on the market not because of demand from the users but because they are easier and cheaper to manufacture and smuggle than heroin.

* Making it easier to help the drug user by removing the burden and stress of obtaining the drugs. This is often an endless cycle of stress which leaves no room for getting help.

* Making it possible for drug users to be functional members of society. Not all people who are addicted to drugs need to stop, for some the safer choice is to accept that they are dependent and work around it. Taking opioids to prevent withdrawal is not incompatible with holding a job and contributing to society, committing crimes to get money for the next fix is. For many people who are addicted to opioids, abstinence programs are not the best option because the rate of falling back to using is very high, and once that happens the risk of fatal overdose is also very high due to decreased tolerance. I won't quote concrete numbers because I cannot remember them right now, but last I heard the rate of failure in abstinence programs was well above 70%.

* By supplying the drugs from sources that have no financial incentive in keeping the drug users on the drugs, you can ensure that users are exposed to all public offers to get help with their addiction or any underlying socioeconomic factors that are probably contributing to why they have become addicted in the first place.

Most criminologists will tell you that punishment is a very poor method of reducing the crime rate. I believe that to be true, and I think that a much better way is to address the underlying desperation and inequality that drives people towards crime. It doesn't mean that we should stop at the safe supply, because that would indeed be the cynical approach, we of course also have to help people overcome all the problems that are probably keeping them in their drug addiction, such as mental health issues and homelessness.

Exactly, noone decides to become an addict, it's a long sequence of lines that are crossed until you find you crossed one that would seem unthinkable before. You also don't become obese from one day to the other, and I genuinely also don't think that it's peoples own fault.

I am frankly appalled by the absence of compassion towards other people in this thread.

So is drug addiction, and that's my point.

No differentiation here, alcohol is widely available from legal sources and very affordable compared to illegal drugs.

I come from a country with social healthcare, and here we also heavily subsidize drugs for people who need them because of their own lifestyle choices, e.g. diabetes medicine due to obesity. Why do people who have become addicted to psychoactive drugs not deserve the same compassion?

Or, you view them as human beings who are desperate and try to help them instead, and probably save money in the process? People who find themselves addicted to opioids or other drugs would not have to steal copper in the first place if they had a safe and affordable/free supply of the drugs they crave.

Some are, but I'm Danish and I think they translated any of the games to that :)

Isn't ScummVM 2D only?

I have started playing Grim Fandango with my kids (7 and 9) after we played through Day of the Tentacle together. Playing old adventure games on the TV and letting people take turns playing is a great family activity!

They aren't native English speakers and the story in Grim Fandango is considerably harder to follow compared to DoTT, so they lost interest a bit after we completed year 1. But as soon as their English skills improve, we'll get back to it, it's one of my favorite adventure games!

Looks very useful, and I like the caching idea which I think makes it interesting for self-healing CI tests.

How does it determine when a cached act() fails and has to be re-evaluated by the LLM? And in particular, if the cache is saved in the cloud (Browserbase?), won't this lead to a lot of cache churn if used in CI pipelines where different versions of the site are running against the same cache?

Also, is there a technical reason why the cache couldn't just be a local file that's checked in along with the script but must be provided by Browserbase? If it was, devs could heal failing tests locally using LLM calls, while CI runs entirely deterministically.

Exactly. And LLMs will only accelerate your rate of understanding so far by helping you find and organize information, at the end of the day you are still limited by your own mental bandwidth.

Put even simpler: code is a liability, and understanding is an asset.

It's easy to add more code, but it also increases the risk, especially if you are the only one who understands how it works. As more people on the team understand it, the risk decreases. It becomes less likely that the code interacts in an unexpected way with other parts of the system, and it also becomes more likely that the existence of the code is justified because noone felt the need to replace it.

If you fire the team and replace it with another, you now have a lot of code and zero understanding. That understanding first has to be mined before you can close the asset/liability gap.

In the age of LLMs, it becomes easy to produce 10x as much code as before, but I don't think you can put the same multiplier on how fast you can increase the understanding. It may even be <1 if you are not being mindful about your LLM use.

What commercial interests and big businesses are driving climate change fear?

Almost exclusively Fable at xhigh. I sometimes run out of tokens, but most weeks it's not a problem. The limiting factor is by far how fast I can push understanding of what was made into my brain, and I find that I waste time using Opus. It makes annoying mistakes, and it makes assumptions that are often wrong instead of actually verifying. And it can't write so I can understand it.

The geometric nightmares! I had those as a kid whenever I was very tired or had a fever, and kept having them until my late teens. Never seen them described and didn't know it was a thing.

That will require a second pass though, because you have to free all your strings again.

Yes, you could allocate it on the stack. I think back then (still?) a filename could be at most 260 characters, each encoded with 16 bits, so about 52k of stack allocation.

But the naive way of doing this also wouldn't really require two passes, right? It would just require more memory because you would first save all file names in an array (stopping at 100), then pick a random one in constant time.

Yes, but there is no alternative other than giving up. Starting a new OS from scratch with zero apps is a much worse starting point compared to a platform where 99.9% of apps work (minus those relying on Play Integrity with strong integrity) which may have its rug pulled in the future. The race here is about getting to a big enough market share that GrapheneOS cannot just be ignored as completely niche but has to be treated as a small but not insignificant minority.

I remember that early image models couldn't generate a cyclops no matter how you prompted it, it would at best put a third eye in the forehead.

I think LLMs have some of the same risks and benefits of stimulant drugs. They can make you more productive if used effectively as a tool, but they can also delude you into thinking you are better than you are and create a dependence such that you aren't just less productive without the LLM/drug, you fail to be productive at all because you don't know how to function without it.

Well, that's at least a positive. I hope this means they are also forced to accept the weakest credential type, and that they can't require you to present the identity proof that the wallet also provides when verifying your age. Because if they are allowed to do that, then that is what will happen.

We also have a Danish wallet now, AltID, which implements an anonymized (assuming no collusion between issuer and eavesdropper or service provider) age verification protocol based on batches of single-use tokens which contain no personal information (except that they can be traced back to you by the issuer).

It's been released and in production since summer. Since then, several social networks have apparently started A/B testing age verification for their EU users, but how many of them actually integrate with the anonymous solution that is now available and in production? To my knowledge: 0. They all use Persona.

This highlights one of my main criticisms of EU's naive approach to regulation of tech companies. They fail to realize that any regulation that they impose will be complied with in the most malicious way possible, which is how we got cookie banners with dark patterns instead of a simple HTTP header saying no thanks to cookies.