Backups: No. Google does not grant you access to the full disk to make backups anymore (for many years now).

Factory reset: Yes. This will NOT restore your personal data. See https://developers.google.com/android/images for Google’s OS image downloads, and https://grapheneos.org/install/cli#replacing-grapheneos-with-the-stock-os for how to revert from Graphene.

I don’t see any mention of whether this uses local models or cloud models. I’m not interested in sending anything I care about it into the cloud.

Spot on.

SNW is good but I don’t think we’ll ever see a return to the old TV format of 20+ episode seasons. You can’t do random episodic stories all that well in 6-12 episodes. Short seasons have no room to breathe.

Even Futurama has this problem with the two new Hulu seasons, and that’s without the burden of an overarching plot to keep moving forward.

In Settings > Home, there’s a Sponsored Shortcuts checkbox.

If you think this isn’t related to human rights, then you’ve missed the point.

People have the right to use technology, and indeed we effectively need technology to exercise our right to free speech. You cannot have one without the other. Not anymore.

The right way to think about this that they are arbitrarily banning a topic of discussion simply because it is not dead-center average. This isn’t even a legal issue, and the justification is utter nonsense (Facebook itself runs on Linux, like >90% of the internet). No government has officially asked them to do this, though the timing suggests that it is unofficially from the Trump administration.

This is about exerting control, establishing precedent, and applying a chilling effect to anything not directly aligned with their interests. This obviously extends to human rights issues. This is a test run.

No. Definitely not. The only reason to use Python2 would be if you inherited an old code base, and then your first order of business would be migrating it to Python3.

Sounds cool. I’m using LM Studio and I don’t think it has that built in. I should reevaluate others.

I’m not entirely sure how I need to effectively use these models, I guess. I tried some basic coding prompts, and the results were very bad. Using R1 Distill Qwen 32B, 4-bit quant.

The first answer had incorrect, non-runnable syntax. I was able to get it to fix that after multiple followup prompts, but I was NOT able to get it to fix the bugs. It took several minutes of thinking time for each prompt, and gave me worse answers than the stock Qwen model.

For comparison, GPT 4o and Claude Sonnet 3.5 gave me code that would at least run on the first shot. 4o’s was even functional in one shot (Sonnet’s was close but had bugs). And that took just a few seconds instead of 10+ minutes.

Looking over its chain of thought, it seems to get caught in circles, just stating the same points again and again.

Not sure exactly what the use case is for this. For coding, it seems worse than useless.

vd (VisiData) is a wonderful TUI spreadsheet program. It can read lots of formats, like csv, sqlite, and even nested formats like json. It supports Python expressions and replayable commands.

I find it most useful for large CSV files from various sources. Logs and reports from a lot of the tools I use can easily be tens of thousands of rows, and it can take many minutes just to open them in GUI apps like Excel or LibreOffice.

I frequently need to re-export fresh data, so I find myself needing to re-process and re-arrange it every time, which visidata makes easy (well, easier) with its replayable command files. So e.g. I can write a script to open a raw csv, add a formula column, resize all columns to fit their content, set the column types as appropriate, and sort it the way I need it. So I can do direct from exporting the data to reading it with no preprocessing in between.

I’m only vaguely familiar with Tailscale, but I am very interested after reading this and will seriously look into it as soon as I have proper time. The author makes a lot of excellent points, and very directly explains a lot of the problems I have with modern computing.

As an industry, we’ve spent all our time making the hard things possible, and none of our time making the easy things easy.

This has been the trend for literally the entire 21st century so far. I’m also one of those “mature” computer users. I started coding before JavaScript was even a thing. And I’ve been repeatedly shocked and frustrated at how things that took me literally one line of code in the 90s somehow require entire custom classes built atop massive frameworks today. Dude, all I want is to add a row to a listbox. It’s not rocket science. I don’t need it to be performant with millions of rows. It’s only going to have, like, ten. This does not require data providers and callbacks and backends. (I’m sure there are modern frameworks that make this easier, but this is a real-world example from the Objective-C/Cocoa era of Mac OS X. Not coincidentally, I stopped caring about writing GUIs around that time.)

https://en.wikipedia.org/wiki/Biquette

According to Biquette’s caretaker at a communal Ferme de Mauriac, the goat spent her first five years (probably ca. 2003–2008) at a milking factory before being handed over to Mauriac because “it was cheaper than a slaughterhouse”.[1] Biquette rose to popularity in early 2012 first, with photos and recordings of the band Wormrot’s concert in Mauriac, with Biquette in the front row. BuzzFeed dubbed Biquette “Punk Rock Goat”,[2] and Metal Insider called her photo “one of the best images in metal”.[3] According to the Wormrot’s manager, Biquette was very tame, and followed the band around “like a dog”.[4] The caretaker of Biquette, named Flo, said in an interview that the goat loved concerts and other gatherings of people and theorized that she liked the vibrations of the wooden floor caused by the live music. Flo also added that Biquette loved stealing cigarettes and cigarette butts, leftover alcohol, paint and oil drains.[1] On December 9, 2013, Biquette’s Facebook fan page alleged to the goat passing away,[5] with Flo clarifying in a January 2014 interview that the cause of death was “a big mystery” and adding that given a 20-year average lifespan of a milking goat, Biquette “burned the candle at both ends” of her 10 years of life.[3]