Archiving my Twitter, Facebook and other social network activity
I finally got the invitation to the #ArcBrowser for Windows beta.
A couple of months after I stopped using it on my work Mac.
And it only runs on Windows 11 for now.
I guess that saves me the trouble of trying to decide whether to test it on a VM, an actual Windows machine, or a fresh Wine bottle.
I’ve had no problems running GNOME and Wayland-native applications on Wayland and my NVidia card for the last…year?
XWayland, however, still has issues on this card. 2D apps are a bit laggy, but running 3D games? Slow, flickery, or both.
Which means I’m still logging into an X session to play Minecraft or anything from my Steam library.
I tried running Minecraft directly under Wayland over the weekend after installing the latest driver update, but it’s still not playable.
With Fedora planning to drop X entirely soon, I’m going to have to start thinking about what to do if the remaining compatibility issues aren’t fixed by the time F39 hits EOL.
On the plus side, if I do that, I should be able to switch the rest of my Windows games over to Linux+Proton (except for bedrock Minecraft) and reclaim that space instead of staying on a soon to be EOL Windows version.
—
I think if I wasn’t already looking at buying a new laptop I’d be more inclined to upgrade multiple components at once.
I need to dig up my notes on what exactly was incompatible between this mobo and the Radeon GPU I tried to use a few years back, and whether I went with NVIDIA because the board conflicts with AMD GPUs in general, or because I just didn’t want to go through more rounds of compatibility testing. Or just redo the research from scratch. Assuming I can get a search engine to actually show matches for the specifics instead of what it thinks I should’ve asked for.
—
Argh…the only post I made about it was too vague, only mentioned that “Indications pointed to chipset compatibility problems with the mobo.” And I couldn’t find any notes on my computer about what chipset was likely to be the problem. No bookmarks either. The only thing I found was a reddit thread I’d saved to Pocket, which suggests that the ASMEDIA driver on the board for the SATA controller can interfere with AMD driver installation on Windows (one of the problems I had at the time), but switching it to IDE mode clears up the conflicts. Oddly enough, I ran into another issue with the ASMedia controller a year later, which involved Windows completely losing track of drives attached to that controller, which I solved by moving the cables over to the AMD controller instead.
It’s possible I saved the thread to Pocket because of the disappearing drives, but it’s also possible it’s the same underlying issue, and now that I don’t have anything attached to that controller, an AMD GPU will work properly on here. If so, that’s a much simpler (and cheaper) upgrade than swapping in a new mobo/cpu/ram combo at the same time.
The Hot Cha Cafe at So Cal Landmarks:
In about 1932, a small, hexagonal shingle-style Victorian building in Long Beach got a programmatic makeover, adding a large, angular percolator made of metal and glass on the roof, to become the Hot Cha Café. The name changed to the Koffee Pot Café, but it remained a coffee shop into the 1960s…
If this was still a cafe I’d totally go there just for the style. I’m glad it was restored instead of demolished!
#Architecture #ProgrammaticArchitecture #coffee #cafe #LongBeach
Reply to 404 Media article via Fediverse post:
My previous understanding of the firehose is that it’s basically an aggregation of what you’d see in a bunch of blogs’ public RSS feeds. Which, OK, fine. Analyze your heart out. Display my posts in your RSS reader. Just make sure private posts and comments don’t leak.
But LLM training isn’t the same as analytics, or showing a properly attributed post in a reader. And quietly changing the terms to allow more kinds of re-use on something most people using the service don’t know about? Not cool.
And not making it clear what is and isn’t included for which purposes? That breaks down trust.
Before this, I wasn’t worried about the Firehose. But now I’m not sure I can trust Akismet, never mind Jetpack, and I’m looking for a new spam filter.
Just got an email from Niantic that they rejected the spelling correction I submitted for the name and description of a Pokéstop whose sign is clearly visible in the main photo…
…back in 2021.
Probably one of those automated “no activity on this issue for 3 years, closing” things.
But c’mon, the correct spelling is RIGHT THERE.
I’ve been meaning to disconnect from Jetpack for a while now. This seems like a good time to do it, and to finally clear out the older Tumblr and WordPress.com blogs I don’t use anymore.
https://www.404media.co/tumblr-and-wordpress-to-sell-users-data-to-train-ai-tools/
Cut/copy and paste is such a basic feature that it gets really annoying when it fails.
Looking for info on how to apply a relatively simple spec:
Pages and pages of articles about why you should use it (half of them paywalled)
One of which mentions the actual RFC whose number you’d forgotten.
Replying to a comment on why Ro would have seen someone’s post about The Bad Space.
It’s even worse: The relevant Kolectiva user replied directly to one of Ro’s posts on what had previously been a constructive thread about blocklist sharing in the context of last week’s spam attacks.
Original thread start:
https://sauropods.win/@futurebird/111969325179943537
Ro replied in the discussion with a link to an article he’d written at Nivenly about the topic. The person in question replied saying he wouldn’t trust Nivenly because the Bad Space was a Nivenly project. Ro replied that it wasn’t true, pointing out that TBS was independent and he’d used it as an example in the article because he knew the project, having built it…
…and then it just went off the rails completely with the guy repeatedly trashing TBS, Nivenly, anyone involved in the project, and just doubling down every time someone posted contradictory information.
And then he started a new thread summing up the same claims he’d made and completely ignoring anything anyone else had said.
Ro’s posts in the original thread appear to have been deleted, but his first post was a simple “I wrote something on this exact topic you’ve brought up, here’s the link.”
Hah! “Local tourism industry workers who want to have their own vacations at least once in a year hate this one weird trick!”
https://tinyview.com/itchy-feet/2024/02/25/travel-hack
Audio cables:
Bluetooth audio:
Going to have to check out the new @classicpress 2.0 release which re-forks from #WordPress 6.2.3, again removing blocks and full-site editing in addition to making additional #ClassicPress – specific changes.
Huh, this cutting board “will not blunk knife”
OK then.
This article on the minimal markup needed for link previews has got me thinking about consolidating metadata again.
I could go pure #IndieWeb and throw out everything that isn’t visible on the page and marked up with microformats2, but I there’s a lot of stuff out there that doesn’t read microformats2.
I’ve already consolidated most of the <meta> tag-based labels like OpenGraph and older HTML conventions. What I may get rid of:
I assume anything that uses Schema.org will fall back to OpenGraph or plain HTML for anything they have in common, but I don’t know whether they’ll still fall back if I keep a JSON-LD chunk with the Schema-specific fields like more detailed article types, what media/event/place is being reviewed, etc.
I wonder if I can add them as microdata where I already have the microformats2 info….
I’m reminded of an exchange from Scalzi’s “Starter Villain” that goes something like this:
“So we’re like, Spotify for evil?”
“Please, we actually pay our workers!”
Good article on the security implications of shipping big, complicated software with tons of dependencies.
Why Bloat Is Still Software’s Biggest Vulnerability – Bert Hubert
The world ships too much code, most of it by third parties, sometimes unintended, most of it uninspected. Because of this, there is a huge attack surface full of mediocre code.
A downside of vague tooting is that when everyone on your feed starts complaining about something without saying what it is, you have to spend extra time figuring out whether it’s something you ought to know about.
Props to Niantic for both the timing on the raid day and for letting the players connect the dots themselves.