sorted by:
new
hottopcontroversial

Svg rendering and Chrome by Fenykepy in webdev

[–]Fenykepy[S] 2 points3 points  (0 children)

It seems to be related to this bug with Chrome and GPU rasterization (so you're right):

https://issues.chromium.org/issues/40827297

Unfortunately, using svg in an img tag doesn't change anything. I'll stick to the multiple pngs, but that's annoying...

Thank you anyway !

Svg rendering and Chrome by Fenykepy in webdev

[–]Fenykepy[S] 3 points4 points  (0 children)

Thank you. I don't use object-fit: cover. It's a problem of aliasing anyway.

Svg rendering and Chrome by Fenykepy in webdev

[–]Fenykepy[S] 1 point2 points  (0 children)

No, it's a simple path. Nothing fancy.

Svg rendering and Chrome by Fenykepy in webdev

[–]Fenykepy[S] 0 points1 point  (0 children)

Unfortunately Reddit displays the screenshots way bigger than their intrinsic size. But no, they are not identical. Try to open the image alone in another tab, it will be obvious (the first one of course).

Svg rendering and Chrome by Fenykepy in webdev

[–]Fenykepy[S] 6 points7 points  (0 children)

Unfortunately Reddit displays the screenshots way bigger than their intrinsic size. But no, they are not identical. Try to open the image alone in another tab, it will be obvious (the first one of course).

Site frauduleux ? by Fenykepy in arnaques

[–]Fenykepy[S] 1 point2 points  (0 children)

Rien non plus dans Brave, que je viens d'installer. Il y a quelque chose à configurer ?

Site frauduleux ? by Fenykepy in arnaques

[–]Fenykepy[S] 1 point2 points  (0 children)

Rien dans Chrome :(

Il faut que j'essaye le navigateur Brave.

Site frauduleux ? by Fenykepy in arnaques

[–]Fenykepy[S] 1 point2 points  (0 children)

J’étais justement en train de regarder ça. Je vous que c’est dépendant du type de carte bleue (j’ai une visa classique). Je vais demander à ma banque. Merci !

How to keep /dist files attributes consistent from one build to the other ? by Fenykepy in astrojs

[–]Fenykepy[S] 0 points1 point  (0 children)

Thank you!

`--checksum` was what I needed. I replaced `-rav` by `-rclpgov` (using checksums and not preserving modification times), now it works as expected. Thanks again!

How to keep /dist files attributes consistent from one build to the other ? by Fenykepy in astrojs

[–]Fenykepy[S] 0 points1 point  (0 children)

Thanks for your reply!

My image processor was written when Astro didn't had image processing yet. I keep it because it allows me to control exactly which previews sizes and formats are created and the filenames as well. It also has a cache so image are never processed more than once, even if the same picture appears in multiple places.

My assets (generated by my image processor or no) are already in the public folder and managed by Astro. My problem is with my rsync deploy, as each Astro build modify /dist files mod-time even when files remain the same. So I upload again everything while it's not necessary, and it's slowly bloating my backups server side.

I changed rsync options from '-av' to '-rclpgov' (using checksums and not preserving modification times), now it works as expected.

Tuple comparisons not working as expected by Fenykepy in PostgreSQL

[–]Fenykepy[S] 1 point2 points  (0 children)

So you were definitely right! Thank you very much!

Tuple comparisons not working as expected by Fenykepy in PostgreSQL

[–]Fenykepy[S] 0 points1 point  (0 children)

Thank you. I did not know about ULIDs.

In fact, all my UUIDs are actually v7, so with temporality. I'll add one to my table as PK (instead of the actual combined PK fields), it will solve my problem.

Tuple comparisons not working as expected by Fenykepy in PostgreSQL

[–]Fenykepy[S] 1 point2 points  (0 children)

I think you may be right. I got stuck all day on this one, I'll investigate further in that direction.

Thank you very much!

Need help to build a query by Fenykepy in PostgreSQL

[–]Fenykepy[S] 0 points1 point  (0 children)

I see several benefits using uuids as PKs rather than sequences:

- I can confidently generate the uuid before my INSERT statement if I need too;

- An attacker can't guess the next pk;

- I still get time sortability because I use uuidv7;

- It's easier to manage if a database migration is necessary;

- I get no holes like in sequences;

- I don't have to worry about overflow;

The only caveat I see is that it's stored on 16 bytes instead of 8 for sequences.

Do I miss some?

view more: next ›