There's a spectrum of how automatic things get in different languages but there's the issue of making it an unobservable optimisation, and also making it not over parallelise. There are lots of interesting approaches in academia but nothing really in mainstream languages and nothing that definitively solves the problem. That being said, I also do not solve the problem lol, I just offer a potential direction that could.
Fun fact: you can email authors of papers and ask for a PDF. Authors don't get paid when you buy a paper (in fact it usually costs money to publish) and they'll generally be happy to send out their work to anyone interested.
Thanks. The type system of the language has some interesting novelty but my key research area is automatic parallelisation of code written in that language.
Currently working on my PhD thesis which is due at the end of the month. I'm cutting it quite close but if everything goes according to plan I should have it all done on time.
Our restrictions were basically lifted after four weeks in 2020 because that was enough to eliminate the virus. I think going a bit authoritarian with the lockdown maximised our freedom in the long run that year.
We had a four week (incredibly strict) lockdown in 2020 and then life returned to normal because we eliminated the virus. In late 2021 the delta variant ruined all that and the government attempted a half-assed lockdown which didn't do much and that's where a lot of the anger came from.
It uses other signals too, like what other sites you've visited with that checkbox on it, what CloudFlare has seen your IP address doing in the past, etc.
The google one is able to see if you're logged into a google account and take that into account.
There's even a new variant of the Google captcha that is invisible and doesn't even bother to show a checkbox.
The modlog page can break if anyone has been banned with an expiry too far into the future, I grabbed this query to fix it from the github issue a while back and refined it a little if it's useful to anyone:
sql
BEGIN;
-- The modlog UI breaks for bans too far in the future
SELECT * FROM mod_ban WHERE expires > now() + INTERVAL '10 years';
-- Lets just make them permanent as an easy fix lol
UPDATE mod_ban SET expires = NULL WHERE expires > now() + INTERVAL '10 years';
-- See our changes
SELECT * FROM mod_ban WHERE expires > now() + INTERVAL '10 years';
ROLLBACK;
-- replace ROLBACK; with COMMIT; if you're happy
This will make any ban with an expiry >10 years into the future permanent and fix your modlog. If this happens a lot it might be worth making this a trigger in your lemmy db.
Do you often find yourself wondering about the true nature of Ogrim nipple-piercings? Does the mythology of Space Pirate Captain Harlock make your head spin? Do you want to learn more about the metaphysics of Sword Art Online, your favorite Cambodian Silent Film? Do you find your questions, concerns, and philosophical quandaries unaddressed by Final Fantasy: Online?
Worry not. [email protected] is a place that encourages discussion on any and all facets of CHIM, Dragon Breaks and the Hist, the greater bodies of Elder Scrolls fiction, without judgement or prejudice.
Here at [email protected], every Muatra is big enough to achieve CHIM.
#3799 has a bug, so I fixed it up alongside simplifying the logic slightly and adding a config flag to opt in to this new behaviour.
Currently live on https://campfyre.nickwebster.dev
Link Actions
I was getting close to hitting the end of my free object storage so there was time pressure involved haha.
Seems to work but I haven't tested it too much. Currently running on my instance.