"To the male Julodimorpha bakewelli beetle, a beer bottle lying on the ground looks like the biggest, most beautiful female he has ever seen.

He doesn't waste any time when he sees her. The male immediately mounts the object of his affection."

https://www.thoughtco.com/the-giant-jewel-beetle-1968152

"Nothing will dissuade him from his lovemaking, not even the opportunistic Iridomyrmex discors ants that will consume him bit by bit as he tries to impregnate the beer bottle. Should an actual Julodimorpha bakewelli female wander by, he will ignore her, remaining faithful to his true love"

@b0rk app developers, typically after being nudged by ops or a security audit.

@GossiTheDog

@markwalker looks like ruff calls it "extraneous": https://docs.astral.sh/ruff/rules/extraneous-parentheses/

@b0rk I know what you mean, but I always assumed `checkout` restores from HEAD, not index. Thanks for pointing that out!

@moanos it seems you have a 1:1 relationship between adoption status and adoption notice. I think you should have a static list of adoption substatuses (maybe even without a table?), and an adoption_substatus field on the adoption notice pointing to the current status.

This way you wouldn't need a big join to query for notices with specific substatus. You could still query for notices with a given status with `.filter(adoption_substatus__in=...)`.

if you use git rebase, have you ever used the `--onto` flag? (like `git rebase main --onto otherbranch`)

(2/?)

@xlenka moje Ubuntu (GNOME + instalowanie co popadnie) ma teraz z 60GB, więc może to 20 to nie tak dużo >_>

@xlenka 20GB powinno starczyć na dystrybucję, ale na /home to już będzie mało.

Tutaj piszą że 15 to minimum: https://endeavouros.com/, pod "Minimum system requirements".

@tay @bovaz well... problem for whom?
For the regulator, sure. They wouldn't be achieving their goals.

If a specific user or site tends to leak a lot: maybe for them, *if* they can be charged for subverting this system or for negligence.

Certificates in this system should be short-lived (examples show a few days validity, if memory serves), and in a case of a huge leak the whole AP (certificate provider) can be untrusted.

It feels strict enough, considering its questionable purpose ;-)

@EUCommission how will those checks help with illegal content? Isn't it, by definition, served with no respect to the law?

On a more serious note: adding a speed bump for accessing gambling, gacha, or other content designed to induce addiction might make sense. But how can we know furry artists won't get thrown into the same basket?

@Huubje @Azarilh they seem to depend on a custom protocol (`av://...`), so I'm not sure about a webapp :-(

@bovaz @tay my reading is: there will be a central list of "age certificate providers" ("APs" in the documentation). The site you are accessing ("RP") would know who provided your certificate, but the certificate provider won't know what sites you are accessing.

A bit like a government ID but just saying "as of [date], and until [date], the person carrying this ID is considered over 18".

@y2k38 @EUCommission "User Journey" seems to be a good summary: https://ageverification.dev/Technical%20Specification/architecture-and-technical-specifications/#23-user-journey

@Azarilh @Huubje the spec doesn't seem to place restrictions on the user's device (from a quick glance, at least).

@tay @hook @bovaz are you sure about the list? For me it sounds more like short-lived certificates. You will want multiple, to avoid tracking across sites.

The "User Journey" describes it well, it's a pity it got buried deep in the docs: https://ageverification.dev/Technical%20Specification/architecture-and-technical-specifications/#23-user-journey

I scored 9/28 on https://jsdate.wtf and all I got was this lousy text to share on social media.

@cadey it's bright red, and not at all similar to the docusaurus thumbnail I was shown under your post.

Days since I've been confused between django.template.base.Template and django.template.backends.django.Template: 0 #Django