tedivm

ProPublica had one of their reports work with gambling addition experts to see how DraftKings would respond to someone presenting signs of a gambling problem. It's a hell of a read, and makes it clear that this company is full of people with absolutely no ethics whatsoever.

https://www.propublica.org/article/draftkings-sports-gamblin...

I don't self host anymore, as it really is a pain, but use Fastmail instead (while my wife uses Protonmail). I would never rely on Google for, well, anything if I can help it.

I think an interesting side of this conversation is how the Google employees are jumping in with DARVO attacks, trying to accuse people of spreading misinformation when they're literally quoting the ToS.

This is something I've seen happen a lot with Google- their employees (especially the director+ folks) are absolutely rabid on social media when it comes to defending their products, and they don't let little things like "facts" get in the way.

Google needs to get a better social media policy because they look like clowns when they do this.

There are a ton of advantages to using uv over pip. I don't use UV because it's faster, although I do appreciate that. I use it because it's smart enough to manage virtual environments for each environment and tool, it can isolate to different python versions trivially, and it handles locking in a way that is actual sane.

Seriously, even as well paid as many devs are these are not machines that are affordable for personal use. Their market is people slapping down millions on frontier model training.

>Indeed, the broad backlash against Flock has grown so strong that the surveillance company last week announced mandatory new audit controls and lower default data retention periods for US users.

I'm a bit disappointed that they didn't call out how much bullshit was in that statement. They are just changing the default settings for new customers. That's it. All the deployed cameras remain the same, and new customers can just toggle those settings off of the defaults. It is so obvious that they were attempting to get credit for doing nothing, and reporters should call that out.

This, like all of their dashboards, is complete bullshit. As a GitHub enterprise user i am absolutely affected by the outage today, and have been affected by all of the GitHub Cloud outages.

There is no separate enterprise platform unless you buy their self hosted server product.

Their CISO literally acknowledged it and then they all continued ignoring it again. This isn't just bad process, this is a broken security organization.

Most automated analysis isn't dependent on just behavior, but rather suspicious things in the code itself. You have a popular open source package with files that exist on pypi but not github then that's a big flag, or if a similar package suddenly has some base64encoded garbage that runs through an obfuscated exec call. In other words the simple fact that the project has obfuscated code is enough to flag for further attention.

That said if the only issue is time, researchers will just run their automated analysis through machines with dates in the future alongside their normal tests.

China is releasing open weight models you can simply run yourself.

Yup, this is one of the many reasons why I prefer OpenCode as my agentic harness of choice. If I'm confused about something I can just read the source code.

The courts have never said piracy, which is how the training sets were originally built, is legal. There are several court cases still ongoing over this.

More memory means less aggressive quantization, more concurrent requests, and larger context windows. I also get a boost in tokens per second (not double, about 1.5x compared to a single GPU).

The 35B model is an MoE (mixture of experts), which uses only a subset of parameters at a time. The 27b one is slower but has way better performance.

No, I use Qwen3.6 27b for everything.

I have a Linux box with two 3090s and it's been great for running Qwen3.6 27b. I lowered the power on each card down to 250w, and then built a small ducting/fan system to vent the waste heat outside. The machine is pretty much silent, and I'm still getting 110 tokens per second out of it for coding tasks.

https://github.com/tedivm/qwen36-27b-docker

This is just not true. There have been leaks due to micrometers in just about every section of the ship at one point or another. A quick search pulls up examples of US modules having issues, especially around interfaces and seals. NASA had a whole investigation between 2018 and 2021 about the recurring issue.

So you both used Anthropic models (Opus 4.7 being from Anthropic)? I'm struggling to understand what your comparison really was here.

Frankly the non-profit has failed. OpenAI is one of the least open of the AI companies (Anthropic is a bit worse). If it wasn't for the labs in China the dream of an actual open ai system would be dead.

They literally threw out every line of code that existed before and rewrote it in a completely different language, seemingly on a whim. That's how it was trashed, in the very literal sense that all of the existing project was tossed in the trash in favor of a completely brand new code base. That's a big deal even if you ignore the coding agent aspects.

Yeah that was a typo, I meant 4.6.

I've had the opposite experience, and have built multiple fantastic applications with Qwen3.6 27b. What quantization have you tested with?

I've completely replaced GitHub Copilot using Sonnet 3.6 with OpenCode using Qwen3.6 27b, and it's been a great experience.

AWS literally did that. They paid for full time developers to contribute back to the redis code base, including core redis developers. If you actually look at the redis code base the majority of it was written by people who never worked for redis.

AWS literally paid for developers for the redis project, including the salary of core members. It's not like they didn't contribute back to the community.

> AWS stomped on open source projects - despite the clear desire of projects like Elasticsearch, Redis, and MongoDB not to be cloned and monetized, AWS pushed ahead with OpenSearch, Valkey, and DocumentDB anyway, capturing the hosted-service money after those communities and companies had built the markets; the result was a wave of defensive licenses like SSPL, Elastic License, RSAL, and other source-available models designed less to stop ordinary users than to stop AWS from stripping open-source infrastructure for parts, owning the customer relationship.

This is completely backwards, at least with OpenSearch and Valkey. AWS didn't create the forks until after the upstream projects changed their license, so it's really weird to say that the forks "resulted" in the license changes when those forks where a response to the license changes. With Valkey in particular it was members of the former redis core development team that created Valkey.

When it comes to understanding large organizations I think a simple principle should apply:

The Purpose of a System is What it Does[1].

Whether malicious or not, the system does what it does. If people wanted it to do something else they would change the system. The reality is that when corporations make mistakes that benefit them those mistakes rarely get fixed without some sort of public outcry, turning the "mistake" into a "feature".

1. https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...

Even if you go service by service you're talking about critical things like `git` operations (literally what they're named for) at a single nine, and stuff that's pretty basic like static web hosting as only two nines. They literally can't even keep static webpages up.

It really has been remarkable watching GitHub just crumble as an organization. There's a lot of discussion about why: the switch from being independent to being part of Microsoft, having resources pushed to Copilot instead of core service, the organization structure itself, a reliance on vibe coding, etc etc.

Regardless of the reason, it's undeniable that GitHub is facing some serious issues. The unofficial status page[1] tells a horrifying story.

I would absolutely love to get some insider perspective on this (if only to learn how to prevent it from happening anywhere I work), but I think it's clear to anyone who has been paying any attention that GitHub is a sinking ship and the only reason people haven't abandoned it already is inertia. Considering how much else is changing in software right now I don't think inertia is enough to sustain a company.

1. https://mrshu.github.io/github-statuses/

Storing on GPU would be the absolute dumbest thing they could do. Locking up the GPU memory for a full hour while waiting for someone else to make a request would result in essentially no GPU memory being available pretty rapidly. This type of caching is available from the cloud providers as well, and it isn't tied to a single session or GPU.

That cost that you're talking about doesn't change based on how long the session is idle. No matter what happens they're storing that state and bring it back at some point, the only difference is how long it's stored out of GPU between requests.