Gioni06

Published my first AUR package this week. It's called bleep, a simple interval timer that beeps.

The idea came from cooking bolognese. I needed something to remind me when to stir. So I wrote a small Go tool that just beeps at whatever interval(s) you set.

Then I kept adding stuff. Verbose mode with a live countdown, pause/resume with signals, and a JSON output mode that works with Waybar. That last one is actually my favorite part. I get a little timer in my status bar that changes color when it's counting, paused, or beeping. Click to pause. Works great for pomodoro or just keeping track of things while working.

I switched from Mac to Arch and wanted to try the whole AUR thing. Used GoReleaser to automate the build and publish. Took some fiddling but it works now.

https://github.com/Gioni06/bleep

AUR: yay -S bleep-bin

I created a GPT-2/3 tokenizer to encode and decode text. Might be helpful when working with the OpenAI API. Contributions are welcome!

That is 100% true. It's a regulatory issue that politics could address. Having no proper age verification is not illegal.

I mixed two points here. Contracts that contradict the law and my wish for better regulations.

I agree. That can also be called "common law" in Germany. Contracts with people who are not entitled to sign contracts on their behalf are not considered legally binding.

In that sense, it shall be treated as if there hasn't been a contract at all. The process is purposefully designed to get a signed contract as fast as possible. The technology to make proper ID (Age) verification is available, but my understanding is, that it is not used by facebook and its partners.

I'm not a law expert, but IMO FB should seriously lawyer up. I can say that this kind of misconduct would almost certainly end up in court in Germany. A 13 years old consent with a cryptic data protection policy is not legally binding and luring kids in need of protection with money to give up fundamental rights can be viewed as an act of non-physical abuse.

Hm..not really. For Terminal CSS I decided to @font-face Fira Code for precisely that reason. Font rendering is a never-ending story when it comes to web design. Not only that browsers render fonts differently, but the operating system also influences it. Font rendering on Windows looks terrible IMO compared to Mac or Linux. So "no" I don't have a solution to that problem. My personal view is that a system font stack is an excellent choice regarding UX. As a user, I expect a certain kind of user experience from my device/OS and a website that respects that tends to offer a better experience than others. To conclude: I should remove Fira Code in favor of a system stack :)

[EDIT] Github is a great example. Uses a system font stack and looks great on all devices and operating systems:

"-apple-system,BlinkMacSystemFont,Segoe UI,Helvetica,Arial,sans-serif,Apple Color Emoji,Segoe UI Emoji,Segoe UI Symbol;"

Thanks! You are right, and it's not for everyone. I created that framework for my website because I was unhappy with other solutions out there. Besides the bare bone, monospace style, I added a "sans serif" variant to make it a bit more "mainstream". My vision for 1.0 is to have a markdown friendly, no fuzz CSS boilerplate for text-content creators.

Uh... I feel like having a lemonade now. https://www.youtube.com/watch?v=rLKwGCtfoq4