The one that is labeled as “German” is similar to, but noticeably different from, the hardware display actually in use on Berlin underground trains. The real one has proper descenders, and also has narrow i/t/l and wider m/w (that is, it's not monospace). Alas, the provided link 404s as well.
> if you are constantly inserting and deleting individual rows, DELETE scales the same as INSERT
Technically correct, but for a small table with a high churn rate, the performance characteristics may be surprising in that the "n" in most big-O calculations includes all inserts since the last VACUUM, not the actual number of resident rows.
Maintaining the expected observable behaviours would get complicated if queries (especially other updates) against the same table are happening concurrently.
If the operators are liable, they will find a way, it's easy for the operators to infer a users age based on usage patterns. They must be required to close these accounts.
It doesn't need to be perfect, but in spite of that perfect is possible if people ask for it. Don't tempt them. Look at what happened in Spain with Cloudflare.
Methodology leaves a lot to be desired in terms of understanding the tasks you've used. Being detailed about why they're more meaningful tests than the long horizon and coding tests used by other rankings is important.
False positives and poorly defined tasks/acceptance criteria have let some models have insanely inflated scores on bad benchmarks.
And sure, you can say they're not disclosed to prevent gaming, but if you're the only one who can review them then the might as well be a random number generator display with an unreadable UI.
3. Tell everyone you know about 1 and 2, and remind them that if they ever actually "verify their age" or any other bullshit, they're likely to have their identity stolen and their details leaked. Never do this. Tell the government to suck a fat one.
4. Use https://www.writetothem.com/ to write to your MP and tell them to repeal the Online Safety Act. It's a censorship and surveillance regime, it makes nobody any safer.
Before making the first shot, turn around and face backwards. Shoot back and to the left toward the barrier. After the ball ricochets, it should hit the downward-angled barrier on the opposite side and hop over it to the end section, where it's not too hard to sink the ball with three or four more shots.
screenshot of finishing with 4 strokes / 6 par (tho my locked-in daily result was 14 strokes).
The video is bouncing the ball of a wall right at the start to make it jump over the wall, water, and corner behind the start, to skip most of the track.
reply