codingjoe

Beautiful README badges to honor your GitHub sponsors.

I created this to show some respect and figured others might like it too :)

It's runny on a Raspberry Pi 5, so no expensive Vercel invoice, no worries. :P

... and I'd still be very happy for them. Some money, is better than none.

Besides, supply chain payments are already a thing and help maintainers like myself already while providing security benefits for corporations.

Empty words. Without changes to anti-circumvention laws, safe harbor commitments for security researchers and serious funding for foss projects nothing is going to change.

I think any notation is use case specific and should be adapted to beat serve its domain.

However, actually writing a good commit message is an art form few have mastered.

I wrote a small natural language linter to teach my teams meaningful technical writing: https://github.com/codingjoe/word-weasel

If you're looking for a Twillio and Elevenlabs replacement, I am working on that too: https://github.com/codingjoe/VoIP

Ok, then for everyone. Don't save tokens in a database. Selects are vulnerable to timing attacks. You want a token to include a id and a signature. The ID is used to look up the scope or user attached to the token, while the signature is recreated from the ID, the server secret and some salt. The resulting signature is double checked with the provided signature with a time constant comparison.

An attacker will be able to identify valid keys, but won't be able to sign them.

You can either split the values like aws or join them with a separator.

Good idea with the slug though, makes it easier to report leaked tokens to the issuer.

Is this running in a production environment yet? If so, do you have an email address to disclose a vulnerability?

Does it show ICEy conditions too?

#di_day #ccc ;)

Finally, I hope that trend catches on. God knows how many messages are missed thanks to toasts.