I made a new media platform where users can share and discuss things. I made it because I was sick of reddit and other major social media hiding content related to the Epstein files. On my site, nothing ever gets deleted, there are no mods, and absolutely no bots. Please try it out and let me know what you think. If you like it, spread the word. Thanks!
While this is true in many places, i believe it is also quite untrue in many more. For example where I live, it was snowing last week. Quite cold but you can't tell csuse the snow already disappeared by the morning. And then suddenly it was sunny a few days after. Today, it was as sunny as the past few days, but the temperature was quite warm. Couldn't tell just by looking outside.
> The Google admin tools and process haven’t quite been able to cope with this situation and people have been overly banned with poor information sent to the users.
I can’t recall any success story of Google’s support team or process coping with a consumer’s situation, many have been posted here. this isn’t a new outcome, just a new cause
I do want to understand what’s happening with the $250/mo fees of users caught in this. will it be automatically cancelled at some point?
I agree that distance is not a great metric. The maximum travel distance on a smartphone screen is already tiny. I'd say the best metric is accuracy or lack of amibiguity, something like average confidence level that any given swipe means a particular word and not another. (This is assuming swipe-based word entry, which I much prefer to anything tap-based.)
I used a Blackberry Classic up until last year when my provider dropped 3G coverage. It's probably a good thing as I never got phone addiction since the browser was unusable and didn't have the apps. I did get in the habit of carrying an iPad with me though for that: but at least then you only pull it out when necessary. I might have to check out the Zinwa retrofit kits mentioned in the article: I do miss the hardware keyboard when using the Android I replaced it with.
The Pinephone with the keyboard accessory was tempting too, but the software readiness (and older hardware) didn't seem practical as a daily driver.
Great site thank you. Just curious, I looked up my company(more than 40k employees across the world including many US states) and it seems like I am not seeing the layoffs that colleagues have experienced. This is probably expected as im probably missing some criteria. Do all layoffs have to have a WARN notice or are there mechanisms/criteria that allow companies to lay people off without filing these noticies?
A WGAN-trained portrait generator running on MSX computers (Z80 @ 3.58 MHz).
Generates 24x24 pixel portraits with 256 gray levels (8 displayed via dithering).
Users can control gender, hair style/tone/type, and skin tone, or generate random portraits. Uses only 16KB RAM
for code and activations, weights stored in ROM. ~20 minutes per portrait on real
hardware. Available as ROM cartridge.Repository includes complete pipeline:
training code, C runtime for PC testing, and ROM generation
>The technology is non-consensual. Usage is up as usage is un-avoidable. LLM technology is pre-packed an obscene range of previously used products: Notepad, spreadsheets, search, IDEs, cell phones, web browsers, and more. It doesn't matter if you mark an email as private, the Microsoft Copilot opt-out was never real and your recipient probably shared it an LLM anyway.
The technology itself isn't the problem, the technology itself isn't non-consensual, and usage is avoidable.
The problem is that you're using software (including operating systems) that fundamentally doesn't recognize the rights and freedoms of the user. The entirety of Microsoft Windows is a prime example of such software.
I use all of the software (and hardware) above without any LLM integrations. You can, too, if you want; it may involve leaving the familiar territory of non-free software and operating systems you've become accustomed to, however.
The biggest break usually happens in the 'loop-back' logic. When an agent receives ambiguous output and starts hallucinating its own confirmation, it can consume API credits exponentially without achieving the goal. We really need better 'circuit breaker' patterns for autonomous agents to prevent these feedback loops.
One way to think about transactions, as I wrote in an earlier comment, would be to think of them as being like snapshots in a copy-on-write filesystem like btrfs or zfs. But another way to think of them is being like Git branches.
When you BEGIN a transaction, you're creating a branch in Git. Everyone else continues to work on the master branch, perhaps making their own branches (transactions) off of it while you're working. Every UPDATE command you run inside the transaction is a commit pushed to your branch. If you do a ROLLBACK, then you're deleting the branch unmerged, and its changes will be discarded without ever ending up in the master branch. But if you instead do a COMMIT, then that's a `git merge` command, and your changes will be merged into the master branch. If they merge cleanly, then all is well. If they do NOT merge cleanly, because someone else merged their own branch (committed their own transaction) that touched the same files that you touched (updated rows in the same table), then the DB will go through the file line by line (go through the table row by row) to try to get a clean merge. If it can successfully merge both changes without conflict, great. If it can't, then what happens depends on the transaction settings you chose. You can, when you start the transaction, tell the DB "If this doesn't merge cleanly, roll it back". Or you can say "If this doesn't merge cleanly, I don't care, just make sure it gets merged and I don't care if the conflict resolution ends up picking the "wrong" value, because for my use case there is no wrong value." This is like using "READ UNCOMMITTED" vs "SERIALIZABLE" transaction settings (isolation levels): you would use "READ UNCOMMITTED" if you don't care about merge conflicts in this particular table, and just want a quick merge. You would use "SERIALIZABLE" for tables with data that must, MUST, be correct, e.g. account balances. And there are two more levels in between for subtle differences in your use case's requirements.
As with my previous comment, this is probably obvious to 98.5% of people here. But maybe it'll help someone get that "ah-ha!" moment and understand transactions better.
The copyright information is in debian/copyright, I forgot to also add a LICENSE.txt to the repo root. Indeed, all source files are covered by AGPLv3. Is this an issue for adoption? It only covers the challenge itself, not the services it's deployed on, and no extra work is needed if the source isn't modified.
For a K-8 environment, it might be worth looking into local e-waste recycling non-profits or university surplus programs. Often, large institutions rotate their hardware every 3-4 years, and they are usually happy to donate older but functional Chromebooks to schools in need. Also, check out 'DigitalEquity' initiatives in your area; they often have streamlined pipelines for this exact scenario
Surely you'll be able to tell who's YOLOing commits without allowing junk into your repo that you'll have to clean up (and it almost certainly be you doing it, not that other person).
DS_Store files are just annoying, but I've seen whole bin and obj directories, various IDE directories, and all kinds of other stuff committed by people who only know git basics. I've spent way more effort over time cleaning up than I have on adding a comprehensive gitignore file.
It takes practically no effort to include common exclude patterns and avoid all that. Personally, I just grab a gitignore file from GitHub and make a few tweaks here and there:
That's a neat factoid, but my point was about repudiating the current boneheaded US foreign policy rather than anything to do with where copyright was invented.
No, 100% would be equal to paying someone 50% of market rate. If market is $100k and someone was paid $80k, you could say “paid 80% market rate” or “25% less than market rate” (since a 25% pay increase would bring them to market rate)
That's quite the strawman. The reason it's ethical is not that LLM's are unpopular or someone dislikes them. It's ethical because LLMs introduce safety hazards, i.e. they cause harm.
The vast majority of YouTube takedowns are done through voluntarily moderation, not via copyright takedown. They require no more due process than moderation of posts on this or any other website.
Oh, IEEE 754 double precision floating point accuracy? Rule of thumb is 17 digits. You will probably get issues related to catastrophic cancellation around x=0. As I said earlier the easiest solution is just to measure in this case. You don't really need to fuzz a sine approximation, you can scan over one period and compare against exactly calculated tables. I would probably add a cutoff around zero and move to a linear model if there is cancellation issues.
And if the measurement shows the approximation has too much floating point error, you can always move to Kahan sums or quad precision. This comes up fairly often.
If I really had to _prove_ formally an exact error bound, that would take me some time. This is not something you would be likely to have to do unless you're building software for airplanes, or some other safety critical domain. And an LLM would absolutely not be helpful in that case. You would use formal verification methods.
As much as I think the outsourcing firms are terrible, underpay employees and in general abuse H1B system, I would like to point out that any analysis that compares Google and Meta with Infosys purely based on H1B filings, is going to be flawed.
One of the glaring problems: Google, Meta, Amazon and pretty much every major tech company pays significant amount of compensation in the form of stocks (and other bonuses), which usually is excluded from the H1B filing. The average “compensation” at these companies is actually much more than the 40% reported here. Plenty of people I know make upwards of $400k but all encompassing, but their H1B petition only includes the base salary which is about $200k.
Sell an additional $200 box containing a Raspberry Pi with Home Assistant on it and a cheap capacitive touchscreen and pre-configure it with Tailscale. Would be reasonably consumer-friendly. Give it a fancy name and start slapping "{$HOME_ASSISTANT} Compatible" branding logos on partners boxes.
If it's not quite as consumer-friendly as you want it to be, contribute your engineering hours to the Home Assistant product until it is.
Bonus points for giving it 25-250W audio output to power speakers and letting you pair them together to play music in sync across different rooms of your house connected to speakers of your choice.
