📦release: `doctrine/orm` 3.4.1

Comes with a revert for something released in 3.4.0 (so… a breaking change, sorry 🙇)

Check out the release notes: https://github.com/doctrine/orm/releases/tag/3.4.1

OMG there's more!

New blog just dropped!

https://dev.to/manomano-tech-team/wiremock-testcontainers-algolia-go--3hn7

#algolia #testcontainers, #golang , #wiremock

📦release: `doctrine/doctrine-bundle` 2.15.0

Check out the release notes: https://github.com/doctrine/DoctrineBundle/releases/tag/2.15.0

#PHP Doctrine ORM 3.4.0 released and now support PHP Property hooks: https://github.com/doctrine/orm/releases/tag/3.4.0

oh shit! I tried to run a diff but nothing happened!

Permalink: https://wizardzines.com/comics/oh-shit-diff-nothing-happened/

Look what I just built this afternoon!

https://github.com/greg0ire/inject-git-hash

Made for #zsh and #git with #fzf

@greg0ire Also PHP 8.4 lazy objects 🥳

📦release: doctrine/orm 3.4.0 🎉

Most notably, this adds support for property hooks thanks @beberlei

Check out the release notes: https://github.com/doctrine/orm/releases/tag/3.4.0

📦release: doctrine/orm `3.3.4` with the changes from `2.20.4` as well as a documentation fix.

Check out the release notes: https://github.com/doctrine/orm/releases/tag/3.3.4

📦release: `doctrine/orm` 2.20.4 with a few bugfixes by https://github.com/dbannik and myself. Check out the release notes: https://github.com/doctrine/orm/releases/tag/2.20.4

Today, I've greatly improved the git shortcut described in https://phpc.social/@greg0ire/113798086104866740 by:

- showing a color preview of the commit;
- using the text *after* the cursor as an extra `git log` argument (so now you can pass e.g. `--all` or a branch name;
- extracting the 2 functions to their own files, they can be seen at https://github.com/greg0ire/dotfiles/tree/main/.config/zsh/functions .

#git #zsh

#linux meme for you

Sachez que si vous m'envoyez un vocal, je ne vais pas y répondre tout de suite. Je vais plutôt :

• attendre d'avoir le temps de l'écouter au calme
• oublier que j'ai reçu un message à écouter
• m'en rappeler quand il y aura un autre message dans la conversation
• l'écouter en urgence pour pas vous faire penser que je vous ignore
• et globalement ne pas répondre parce que vous faites des vocaux trop longs pour qu'on puisse répondre à un élément précis.

Signal Messenger is warning that Recall, the AI tool rolling out in Windows 11 that will screenshot, index, and store everything a user does every three seconds, poses a risk to its users. Effective immediately, the Windows Desktop version will by default block the ability of Windows to screenshot the app. Of course, Microsoft provides no API to disable Recall from screenshotting specific apps, so Signal is getting creative. They are invoking a digital rights management API that blocks the screenshotting of copyrighted material.

https://signal.org/blog/signal-doesnt-recall/

#vim protip: when using Treesitter, use `syntax off` to disable basic syntax highlighting, that way you will notice if you need to install a treesitter parser you don't already have.

@hypolite it's a big company, they probably have good reasons to do this... Probably.

The other day, while stranded at Lisbon's main airport due to the blackout, I frantically tried to book a return trip with Air France.
I used DuckDuckGo to find the website, and noticed something weird: the url started with `wwws`. In fact, trying this right now, you can see that it is the second result. If you click the first link, you will get 301 redirected to the `wwws` subdomain (301 is the same as 308, but slightly worse).
I tried booking a flight, and the payment failed several times.

I almost canceled my card via my banking app, but decided to call them instead, and they told me that everything seemed alright.

Meanwhile, my friends had looked and found an explanation: https://superuser.com/a/353250

TL;DR: A few organisations use `wwws.` to suggest that HTTPS is supported and arrange redirection so that users don't have to type the `https://` protocol specifier.

Frankly, WTF? This does not make me feel safe at all! For me, it achieves the opposite of the desired effect.

One of my friends then pointed a weird CSS issue that made the accent over "e" appear way thicker than it should be.
I was now convinced that hackers somehow managed to bump the `wwws` subdomain high enough and had no way to check if maybe some letter in the domain was not the letter it pretended to be, which would explain this. I mentally broke down, thinking I was now stranded without any payment means.