fullsquare

ai is crypto 2 episode 373275

there was chrome (and firefox probably?) extension that went through your all fb liked pages and unsubscribed from them so that when it's done timeline is gone entirely. fb went after its dev, removed that extension and banned him forever because it kept people off fb https://www.businessinsider.com/facebook-bans-unfollow-everything-developer-delete-news-feed-2021-10 doing this all manually still worked back then, not sure about today

Facebook's letter took him by surprise, he said, adding that Unfollow Everything had only 2,500 weekly active users and 10,000 downloads.

"It was definitely growing, but it wasn't huge," he said.

"Apart from that I just very much saw it as something that improves the Facebook experience for Facebook users," he added, saying he got "amazing feedback" from people saying they "were using Facebook in a way that was much healthier for them."

slightly healthier relationship with attention devouring parasite in your pocket? not on zucc's watch, ALL contents of your skull are to be sourced from and licensed to meta platforms inc exclusively

i bet they have some preferences about contractor

a hellish vision has been revealed to me

https://mander.xyz/post/47729411

potentially a common one, but we'll only know after password leak from somewhere

it's crazy how people memoryholed that (and japan doing the same, and a handful of other countries). or how until 2022 war norway wasn't really thought of as petrostate by people who didn't pay attention. or how ten years ago, if you said that putin bombed apartments to wage war on chechenya to win elections all to pardon yeltsin, people would think that you're a crackpot

no there's also racist twitter

i've collided with an article* https://harshanu.space/en/tech/ccc-vs-gcc/

you might be wondering why it doesn't highlight that it fails to compile linux kernel, or why it states that using pieces of gcc where vibecc fails is "fair", or why it neglects to say that failing linker means it's not useful in any way, or why just relying on "no errors" isn't enough when it's already known that vibecc will happily eat invalid c. it's explained by:

Disclaimer

Part of this work was assisted by AI. The Python scripts used to generate benchmark results and graphs were written with AI assistance. The benchmark design, test execution, analysis and writing were done by a human with AI helping where needed.

even with all this slant, by their own vibecoded benchmark, vibecc is still complete dogshit with sqlite compiled with it being slower up to 150000x times in some cases