kiss my ashe

we're looking to create an AI policy, and when we were talking about this, my boss (older millennial) was genuinely shocked to hear that younger people do not (seem) to view AI positively (a la the recent commencement speakers being booed)

please rb for larger sample size!

Question 1/3

Thank you for helping with this data collection. Please rb for as big a sample as possible!

1. The court holds Google responsible for statements made by its AI, considering them Google's statements (search engines have limited liability for results in their engine as they're the words of other sites/companies/people), meaning when their AI lies/hallucinates they're liable for the defamation/harm resulting from those statements.

2. Google's defense that customers are generally aware of the lack of reliability and are responsible for fact checking was dismissed. As the court pointed out, that would "significantly diminish" AI Search's stated purpose and it can't be distinguished from Google's business practices/statements as a search tool.

3. Studies have found about 91% of Google's everyday AI responses are accurate, leaving millions of searches per HOUR with potential liability for falsehoods. 56% of correct responses weren't supported by the sources the AI listed. Both of which mean Google is now liable for a LOT more AI "errors."

4. Google was held liable for 80% of court costs in this case and this precedent is expected to reverberate around the world. This is a massive shift from the 3rd-party search provider role Google has previously played and it comes right as they've tied ALL searches to their AI search.

i have a file or folder on my pc that i want to share with other people. let's call it gayshit.mp3

unfortunately gayshit.mp3 is 750mb and im not paying for discord nitro so i need another way to send it

i put it into qbittorrent and it makes a torrent file. this is essentially a very small file that points to gayshit.mp3 so other computers can find it. kinda like a treasure map

i send this tiny file to my friend, who loads it into qbittorrent. their computer takes a moment to find mine over the vast expanse of cyberspace and then (as long as my pc is running and the file is still where it should be), it gets copied from my hard drive to theirs

this is the cool part: if somebody else loads that tiny file, they can download it from both of us. if i'm offline but my friend is on, the third person can still get it. this also means that if two people have separate halves of the file, they can download the other half from each other. as long as some combination of people have the pieces between them, they can all have the whole thing.

crucially this does not require a server!!! you can just upload the file to a few people and as long as they keep it, it's still accessible. as long as somebody, somewhere is still connected, it's available forever. the only way it goes away is if everybody disconnects from it.

twelve episodes, twelve contestants - a mix of annoying middle aged sci fi authors, fan fic authors and random people off the street

a variety of against the clock writing tasks, big finish scripts, ability to interact with actors without shouting at them and challenges where you have no budget or doctor for an episode

judged by solely by christopher eccleston

This is because as a beginner, you have troubles because you don't have much knowledge.

But then you learn a bunch more, and now you've got the skills to do a bunch of stuff, so you run into a lot of problems because you're doing so much stuff, and only an expert could figure them out.

But then one day you are an expert. You can reprogram everything and build new hardware! You understand all the various layers of tech!

And your problems are now legendary. You are trying things no one else has ever tried. You Google them and get zero results, or at best one forum post from 1997. You discover bugs in the silicon of obscure processors. You crash your compiler. Your software gets cited in academic papers because you accidently discovered a new mathematical proof while trying to remote control a vibrator. You can't use the wifi on your main laptop because you wrote your own uefi implementation and Intel has a bug in their firmware that they haven't fixed yet, no matter how much you email them. You post on mastodon about your technical issue and the most common replies are names of psychiatric medications. You have written your own OS but there arent many programs for it because no one else understands how they have to write apps as a small federation of coroutine-based microservices. You ask for help and get Pagliacci'd, constantly.