Interesting look at how trading culture has spread into places people do not usually associate with markets. Access to zero-commission apps, constant financial content, and group dynamics can make this kind of behavior grow quickly. It will be worth watching how leadership handles the risk side, since impulsive trading and high stress environments are not a great mix.
I see this in a similar light to the opioid crisis. While it won’t directly kill you like opioid addiction or overdose, economically strip mining Gen Z and Gen Alpha for gains using meme stocks, crypto, sports betting, prediction markets, and similar systems is going to leave us in a bad spot after these enterprises have left with their gains.
Indicators to track will be suicide, bankruptcies, domestic violence, military washout rate, etc.
Nice to see a practical walkthrough of pretraining instead of only fine-tuning examples. Most people don’t realize how much of the work sits in data prep, stable training loops, and managing compute. Even a small BERT run is a good reminder of the gap between theory and an actual training pipeline.
This looks useful for quick demos and sharing work without dealing with full deployment. Curious how it handles security boundaries and resource limits when exposing a local environment to the internet.
Good write-up. Incidents like this show how easy it is for data to leak through third-party tools, even with good internal policies. The more dependencies a product has, the harder it is to keep the full chain secure.
That’s why you should only export anonymous information to external parties. There is no valid reason for OpenAI to export my personal information like this.
I will report OpenAI to the data protection agency in my country and I encourage others to do the same. They can not blame Mixpanel when they sprinkle others personal information around like this. NOT OK.
Name that was provided to us on the API account
Email address associated with the API account
Approximate coarse location based on API user browser (city, state, country)
Operating system and browser used to access the API account
Referring websites
Organization or User IDs associated with the API account
Rookie mistake for a billion dollar plus company, let alone the most valuable in the world.
I find throwing mixpanel under the bus whilst ignoring the giant elephant of "why were you giving them that user data in the first place" to leave a sour taste
The numbers in the article are huge. It really shows how expensive this stage of AI development has become. I’m curious how long companies can keep operating at that level of burn.
The tech giants have a lot of cash-flow to burn, and at this point it's better for their investors that they do rather than admit it was a loss or the stock value would fall.
It might be a huge pile of cards but this time they have the coffers for it, if/when it falls it will be from one of the fake it till you make it companies like openai that are built on promises (and frankly their revenue numbers are no where near their promised spend so they seem dependant on more and more deals)
A fun reminder of how easily we add assumptions that aren't in the question. The “Age of the Captain” puzzle shows how quick we are to look for hidden meaning when there isn’t any.
Nice project. On-orbit grasping is tricky because of tumbling objects and unpredictable motion. An adaptive gripper with force sensing seems like a practical improvement. Would be interesting to see how it performs in real microgravity tests.
I’ve been seeing similar issues with large travel sites lately, so your experience doesn’t surprise me. When the homepage returns a 200 but shows an error page, it usually means something broke in their reverse proxy or CDN rules. That tends to happen when a new deployment goes live without enough real-world testing.
Since most of Expedia Group’s support is script-driven, it’s almost impossible to report a technical problem unless you know someone on their engineering team. The shifting behavior across browsers and devices also makes it look like a bad A/B test or traffic-split configuration.
It’s not great when a company that size lets something this visible slip into production. Hopefully someone from their engineering team notices this thread and rolls back the change.
The post shows a common issue with Wayland. The protocol is there, but each compositor handles things a bit differently, so tools like xdotool end up running into gaps or inconsistent behavior.
Wayland is improving, but there is still a difference between what the spec supports and what developers can rely on across the ecosystem.
A good look at why automation on Wayland still feels rough for some users.
