IPv6 addresses are ugly and hard to memorize. IPv4 addresses are pretty and easier to memorize. That's about the end of the discussion as to why it's basically a failure.
It's so ingrained in you you don't even consider it a use of ipv4. 192.168.1.x is natural and pretty. ipv6 is a horror show and incompatible with the way that we think and remember things.
"Ah, crap, avahi isn't working, but fortunately I remember that that computer is blablabla.34." The IPv6 equivalent of that is like "fd12:3456:7891::1". Absolute non-starter.
I briefly tried to contribute to a popular AI project (a ChatGPT-like web-based interface) where I found some bugs and reported them as issues, with steps to reproduce. The maintainer closed them and moved them to discussions, which is what he did to any issue he didn't like or personally didn't believe mattered, I guess. Items in Discussions didn't get any attention, nor were follow-ups looked at. One of the issues even involved the total loss of user data on upgrade.
So this makes me think the developer here just doesn't like the idea of issues being reported on his project.
Given the political comments in what's supposed to be a filter, and how everything is prefaced with "shit" like "Pinterest shit," I bet the author had a personal political disagreement with those accounts.
The list is also too specific to be useful in some cases, like, is it really important to you that you add 12 entries for specific Amazon products, like: `
duckduckgo.com,bing.com##a[href*="amazon.com/Rabbit-Coloring-Book-Rabbits-Lovers/dp/B0CV43GKGZ"]:upward(li):remove()`?
As someone with a basement rig of 6x 3090s, not really. It's quite slow, as with that many params (685B) it's offloading basically all of it into system RAM. I limit myself to models with <144B params, then it's quite an enjoyable experience. GLM 4.5 Air has been great in particular
I had a Matrox Millenium card with a breakout box for capturing RCA, S-Video, and Cable TV; I'd watch TV on my Windows 98 SE2 computer, which was the craziest thing back then, but I always felt like the green-screen like effect was some kind of mysterious bug that I'd better not mess with, or video capture would break. Windows 98 was barely working on a good day, so it felt like the computer was in the process of failing in a graceful and useful way, so I'd better not push my luck.
Every so often you could get a glimpse of the man behind the curtain, by dragging the window quickly or the drivers stuttering, which would momentarily reveal the green color (or whatever color it was) before the video card resumed doing its thing. Switching between full screen and windowed mode probably also revealed the magic, or starting a game that attempted to grab the video hardware context. And of course sometimes other graphical content would have the exact right shade of color, and have video-displaying pixels.
I'd pay a decent price for a non-emulated 486 on a credit card sized board, or in a cute little case, with useful peripherals. Something like those Aliexpress mini pocket 386 computers, but 486 is significantly more useful for gaming.
The weakness was carefully going through the menus and manually adding a reporter to your group chat. There's not much the Signal team could have done about that.
I bet they'll phase it out and try to force their worse service, wherein your data is stored on their servers, like they tried to do with PINs. It took enormous pushback to get them to stop mandatory PINs, and even then they made it nagware for a year or two.
I didn't trust their rationale about PINs and remote attestation somehow meaning your data is secured by a small passphrase, just like I won't trust them to not remove a useful and existing feature I already rely on for backups.
Also not mentioned, they designed their existing backup solution to require reverse-engineered community solutions to actually access your data; I have to use a Github project to unencrypt the backup and export my chats, which is something I've never had to do with any other messenger.
From your link, I wish they would answer this, and they've been asked numerous times, and to my knowledge have avoided the question (which is very concerning to me):
>This is excellent news! Will there also be official documentation on the backup format, potentially even official tooling like signalbackup-tools[0] to access/parse backups offline? I'm asking because, having used Signal/TextSecure for 10 years now, my backups are worth a lot to me (obviously) and there have been times when I would have liked to mine & process my backed-up data. (Extract media from conversations in an automated manner, build a more elaborate search, …)
I'm like that poster and backup all my chats obsessively, since way back in the day, and experienced a period with Signal where it was impossible for me to access my own data because of their position.
