Biason::Julio::new(); @juliobiason@functional.cafe

That moment when your CPU is not over 50% (overall) but its fans are all "FOR FRODO!"

Yes, I do check Twitter sometimes (it moves faster than Fedi, sorry).

Yes, I do report aggressive/violent/insulting tweets.

Yes, I do check the results for said reports.

Only on Twitter an account can break three rules at once and not get blocked.

"This is a really Plusser Tuck!"

I'm seeing a sad relationship, on Telegram groups, of people not using their real photos on their profiles and an attitude of "I don't want to understand, I just want it to work!"

I wonder if there is a way to identify that the browser accessing a site understands FLoC -- the solutions I saw so far are basically adding a header sent by the server telling the browser to not FLoC it.

Identifying it would be a lot better, 'cause you could put a HUGE alert to your users.

I do understand the power of "standing your ground" -- I use Firefox, so I do stand mine -- but sadly the internet is "controlled" by a single entity.

I do like how many projects are jumping forward and saying they will block FLoC and all...

... but when 80% of the internet runs on a single stupid browser, by people that don't even understand (and don't care) what's going on behind it, I have the feeling that it will be all for nothing.

I can slowly feel my brain failing...

Podcasts with no transcript are not worth it.

"Someone knows a FREE tool to make browseable manual for a web system?"

HTML?

Github seems a bit too chat recently in their blog, isn't it?

(I still need to figure out the proper way of doing this, but when you think threads and such, all the annoying things the Rust compiler complains make total sense.)

One thing that broke me (today) when coding Rust in a toy project:

I wanted to access only a member of a struct as mutable -- a File object --, so I wouldn't need to change the trait and the rest of the code.

So I thought I was really clever and tried to use a RefCell, which has external immutability but internal mutability. Didn't work.

And then, thinking about it, looking at the code, I thought "What if I was using async/threads? How would they all write in the same File?"

And that's where I realized where my line of thought was wrong.

"Open source alternative to X."

Awesome.

"You will also need Google API credentials."

Then no. You failed. Sorry, not sorry.