Nicolás Alvarez

530 Followers
210 Following
3.1K Posts
Currently hacking and documenting Apple stuff for fun and no profit.
Twitterhttps://twitter.com/nicolas09F9
LocationBuenos Aires, Argentina
Liberapayhttps://liberapay.com/nicolas17

Drink more water or you'll regret it when you get a kidney stone.

I am in pain ☠️

happy mailing list memberships reminder day!
What Is a Dickover?

dickover — a modal panel, popover, or curtain presented by a website or app, deliberately obscuring its own content to frustrate the user with an unwanted, unnecessary, mandatory interaction; e.g. asking the user to accept “cookies”, subscribe to a newsletter, install the website’s mobile app, agree to terms of service, or anything else that the user couldn’t give two shits about.

Daring Fireball

So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.

Revert to 3.4.1 and it works.

So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.

Since 3.4.1, 36 commits by "tridge and claude"

Oh for fuck's sakes.

“sure kagi is an extremely unethical company that sends part of everyone’s subscription fees to Russia for search indexing and Musk so grok can enable the AI horseshit nobody but kagi’s CEO wants, but what alternative do you recommend” I recommend not being part of the problem for once in your life, you fucking shithead
I'm struggling to find real Rust code using rusqlite and not simply collecting all rows into a Vec before returning. Does nobody make iterators getting rows from the DB incrementally? :/
I'm struggling to find real Rust code using rusqlite and not simply collecting all rows into a Vec before returning. Does nobody make iterators getting rows from the DB incrementally? :/

RE: https://tldr.nettime.org/@tante/116605858023186072

Google Search rests on a social contract: their bots can crawl our sites, they can index our sites, and they can show excerpts of our sites because

and •only because•

they send people to our sites. •Our• sites, our words, with our design, with our links, with our context and our aesthetics, shared the way we want to share them.

Google is announcing — unambiguously and with great fanfare — that they are now fully breaking that already-ragged contract. We should reciprocate.

1/2

AI-powered Apple Wallet "receipt linking", huh... wonder what that will be about.

I see people taking the part of the Rust RFC thread about LLM use saying "no discussing about envoronment, social consequences, deskilling, copyright, etc" out of context and criticizing the #Rust team for that, like "there's no place for ethics in Rust" when if you read the fucking thing they say it's because they discussed all of that over on Zulip with more than 3000 messages and they consider everything has already been said and the decision already been done, so the Github RFC should stay focused on the writing itself and they are obviously tired.

Decision being, in a nutshell : no LLM ouptut in rust core but you may use it to review or make suggestions because they can't detect that anyway, which doesn't feel like they "don't care".

If you can stop people from using LLMs by the sheer force of your will, please go ahead. If you can't, don't expect it from OSS maintainers and don't drag them in the mud because you consider they're the ones responsible for a shitty world. They're not.