I don’t get the problem with flathead, for household applications it seems the most superior because I can use literally anything in my house to drive the screw (butter knife, credit card, a housekey)
plus almost every size of flathead screwdriver can fit in almost every size of flathead screw.
In Japan if you work full time for a larger employer, you pay into “shakai hoken” (societal insurance) this pays you like a third of your salary if you get injured and have to refrain from work for awhile. (This is at least partially paid for by your company because you can only legally be fired in Japan if the company proves beyond a reasonable doubt you were either belligerent or the company couldn’t survive without you)
They don’t pay out unless you call crime stoppers. If they called 911 they don’t pay out.
Guix user pains. The packages download at that speed.
It’s a tossup whether downloading Librewolf or building it will take longer
This is much more likely as LLMs typically only respond that they can’t formulate a response when there’s an error in the prompt pre-handling systems.
バルス(barusu)
This isn’t entirely accurate. Main issue is that this is all very new and moving very fast, so while it’s not fair to call atprotocol completely open it’s not fair to call it centralized either.
Right now you can run a relay independently and you can scrape bluesky’s PDS set with it (guy did that in July and it cost about 150 bucks a month, probably more expensive now. https://whtwnd.com/bnewbold.net/3kwzl7tye6u2y) there’s just not much incentive to do so. This recent policing of accounts might change the calculus on that thought process, but for now it’s not really that you “can’t” it just nobody really wants to. (Additionally there’s only like one client that lets you set multiple relays and/or appviews, so the front-ends haven’t caught up with this idea either.)
Theres about 760 or so independent PDSs right now: https://blue.mackuba.eu/directory/pdses and the list is growing.
You can host an independent blog using your own PDS and not even using bluesky’s Relay network at all: https://github.com/haileyok/blug
Or you can still have your data independent on your PDS but still allow the relay to scrape your blog update mentions: https://whtwnd.com/
More detailed is here: https://whtwnd.com/alexia.bsky.cyrneko.eu/3l727v7zlis2i
tl;Dr:
They are VC-Funded, they will inevitably screw over everyone!
I understand where this notion might come from, though, ATproto has already matured enough that it could be used without BlueSky PBC existing. It could die tomorrow, and with little effort the ~650 non-bsky PDSs and a relay (which would have to handle much less data at that point) could be ran by volunteers and interested people.
That’s ironic considering the magic word is basically shouting “balls”
BYD are a battery manufacturer that happened to break into the Car Market. One of the few EV manufacturers of trust with interesting battery news.
That’s fine, most of the content was written by corporate robots before anyway.
Pages that don’t work well with darkreader aren’t many, but when they do fail they fail somewhat entertainingly:
I run btrfs on every hard drive that my Linux boxes use and there’s the occasional hiccup but I’ve never run into anything “unrecoverable.”
I will say that compared to extfs, where the files will just eat shit if there’s a write corruption, because btrfs tries to baby the data I think there appear to be more “filesystem” issues.
Typically when there are “can’t mount” issues with btrfs it’s cause the write log got corrupted, and memory errors are usually the cause.
BTRFS needs a clean write log to guarantee the state of the blocks to put the filesystem overlay on top of, so if it’s corrupted btrfs usually chooses to not mount until you do some manual remediations.
If the data verification stuff seems more of a pain in the ass than it’s worth you can turn most of those features off with mount options.
I’ve had btrfs go into an error state because of a bad write before, but it was pretty easy to recover from
Seeing as how the full unquantized FP16 for Llama 3.1 405B requires around a terabyte of VRAM (16 bits per parameter + context), I’d say way more than several.
Yea a surprisingly small number of people don’t know a git remote can literally be any folder outside of your tree, over almost any kind of connection.
I thought about doing a forge but realized that if I was the only one working on this stuff then I could do the same thing by setting my remote to a folder on my NAS.
A bit of a counterpoint: https://whtwnd.com/alexia.bsky.cyrneko.eu/3l727v7zlis2i
The way some moderation lists (ban/labeling) work is algorithmic.
You can actually host one of these services yourself!
That’s not true at all actually, running a PDS uses about as many resources as a regular personal blog HTML server (as it doesn’t do anything but serve up your signed posts), and running a relay with only the couple thousand people that have decided to host their own PDSes is home self-hostable.
Good blog post here clearing some stuff up: https://whtwnd.com/alexia.bsky.cyrneko.eu/3l727v7zlis2i