- This isn't about things that happened decades or centuries ago though. It's about how right now, today, the UK is arresting 12,000 people a year, 30 a day, for supposedly "offensive" posts on social media.
https://freespeechunion.org/police-make-30-arrests-a-day-for...
- Thanks! This is a much better link than the OP, and better preempts the usual round of "why not my other pet language X instead"? questions. Clearly this choice and strategy has been in the works for a long time and the team has carefully thought out all options.
- > Ban all advertisements. (I'm all for it, at this point.)
What would that actually look like though?
Take something that could be considered an ad, but probably most people agree is a good thing. Say you post on here that task X is such a pain in the butt to do all the time as a general gripe, then I say hey, I built a cheap subscription webapp to solve task X easily that you might want to check out. You sign up for it and use it and like it. Seems like everybody wins - you get a problem solved for a small amount of money, I make a little money and get my project used and my work validated etc. But it's still technically an ad.
Lots of stuff like that could be considered an ad. Every "Show HN" could be considered an ad. Suggesting people vote for candidate X or party Y could be considered an ad too - plenty of organizations do pay for actual ads just like that already. Product placements is a type of ad, but it's pretty hard to not do. I don't know how you even make a movie or TV show with people driving cars without showing a particular model of car.
I don't expect that's the kind of ad that everybody is complaining about. Okay, but then how do you legislate the difference? Can you, or anyone, actually write down a definition of the ads you want to ban and the ads you don't? And how will people distort or abuse those definitions? There's billions of dollars in advertising (maybe trillions?), it's not going to all just go away because somebody passed a law. What happens when all of that money gets poured into attempting to abuse such individual personal recommendations? That's already happening on Reddit now, though at small scales for now.
- You don't necessarily have to if you're just getting a speeding ticket. But in order to write a speeding ticket, you have to hand over a valid Driver's License so they know who to ticket. Exactly what should they do if the driver refuses to provide their Driver's License?
- I don't think this makes a lot of sense because, if the password is quick and easy to type, it can probably be cracked by any such device in the time it takes for a single keystroke. A long and complex password might hold up okay, but for it to actually be secure, you would have to type in the whole password on a phone keyboard every single time you opened the app, which sounds like a terrible experience.
I think, if you were actually willing to do that, it would probably be about as convenient and at least as effective to leave the device powered off and rely on the device full disk encryption and hardware security to protect the data at rest, only powering it on occasionally to check or send messages, then immediately powering back off.
- Exactly what "rolling over" would that be?
Maybe you don't believe Durov's statement[0] about it. But is there any actual evidence anywhere that they've ever violated the secrecy of non-e2e private groups or messages for anyone? I've yet to find any.
- Speaking of, maybe I started paying attention at the wrong time, but I could swear I've seen like 10x more post/comment volume whining about how annoying the "Rust evangelism strike force" supposedly is than actual excessive Rust evangelism
- Reminds me of the Oceangate disaster as proof that things at least that dumb can happen in real live involving substantial amounts of money. Including everyone who is actually an expert in the field telling them that this is idiotic and usually quitting.
- Where's the meme of the guy who gets hired on to a tech company, fixes one bug that always annoyed them, then quits immediately
- "Pro-war" seems like an odd assertion here. They're recognizing the status quo in a reasonably neutral way, which seems anti-war to me.
It seems like you're advocating for Western powers to take a position, using either soft or hard power, on a war that already ended many decades ago. Sounds quite a bit like imperialism to me, and pretty far from being anti-war.
An anti-war position, at least from the perspective of a Westerner and Western companies, is more like, you guys lost, suck it up and stop asking us to intervene on your behalf.
- I don't particularly like this article, mostly because he seems to have spent the great majority of it ranting about people on the internet supposedly yelling at him about not being "on the cloud" and semantics about exactly what constitutes "the cloud". I'd be much more interested in reading exactly what he was spending that money on at AWS and how he moved it all onto one or a few bare-metal boxes.
I don't think AWS is particularly expensive at all. In fact, it's rather cheap at quite a few things if you know what you're doing and use the right services. I've got all my server backups going to S3, for which I pay a whopping penny a month. I also host a handful of Docker images on ECR for 7 cents a month - way cheaper than any other private hosting service I know of.
Now RDS, and the equivalent at every other hosting provider I know of, gets quite pricey indeed. IMO, you shouldn't bother unless you have pretty serious needs for reliability and speed. Apt install your DB server of choice on bare metal goes quite far. Or possibly pull a container of it into whatever you're using to manage containers.
- Actually I think I might be a little misguided here - confusing a mutex with an awaitable lock method versus blocking, and a mutex whose LockGuard is Send and can be held across other await points.
To clarify, I do still think it's probably wise to prefer using a mutex whose LockGuard is not Send. If you're in an async context though, it seems clearly preferable to use a mutex that lets you await on lock instead of possibly blocking. Looks like that's what that Safina gives you.
It does bring to mind the point though - does it really make sense to call all of these things Mutexes? Most Mutexes, including the one in std, seem relatively simplistic, with no provision for exactly what happens if multiple threads/tasks are waiting to acquire the lock. As if they're designed for the case of, it's probably rare to never for multiple threads to actually need this thing at once, but we have to guard against it just to be certain. The case of this resource is in high demand by a bunch of threads, we expect there to be a lot of time spent by a lot of threads waiting to get the lock, so it's actually important which lock requesters actually get the lock in what order, seems different enough that it maybe ought to have a different name and more flexibility and selection as to what algorithm is being used to control the lock order.
- Considering this issue did also make me think - maybe the real footgun here is the async mutex. I think a better "rule" to avoid this issue might be something like, don't just use the tokio async mutex by default just because it's there and you're in an async function; instead default to a sync mutex that errors when held across awaits and think very hard about what you're really doing before you switch to the async one.
- Assuming this quote from the article is true, it sounds like the only villain here is the school principal:
> It said the AI alert was sent to human reviewers who found no threat - but the principal missed this and contacted the school's safety team, who ultimately called the police.
So the company AI reviewers correctly determined that there was no actual gun, and the police responded appropriately to a report by a person (the school principal) who claimed to have seen this student with a gun. The question then is what the heck is this principal doing? Why do they have access to this pre-verified AI information, and why are they going off and calling the police with this information before doing any verification themselves?
Well also, none of the coverage includes what was said to the dispatcher, but maybe they screwed up too - I would expect a dispatcher to question the caller in more detail about what's going on. Like, what kind of gun was it, is it in their hand or in a pocket or what, did they point it at anyone or threaten anyone with it or are they just carrying it around, etc, and such information could be used for a more appropriate police response.
- No, it's 100% appropriate. Anyone can have opinions on anything, but frankly, most of them have little relevance to reality. Their use of the word "expert" is supposed to mean the person has knowledge or expertise that renders their opinion on a subject substantially more valid and relevant than any regular person. That clearly is not the case here. If I wanted to know what a random person on the street thought about a subject, I could go ask one myself. The purpose of news organizations was supposed to be to better-inform people by getting opinions from actual relevant experts in a subject.
These people don't seem to have much ability to discuss relevant subjects like what the actual reliability of lower-tier hosting providers is, the value-add to business and iteration speed of having a variety of extra services (SQS, DynamoDB, VPC, RDS, managed K8s, etc) available, etc.
- I did say that those aspects of Ruby would start to be painful at that scale, not that it was totally unusable. Clearly it's usable, and there's certainly less scale-able things than Ruby on Rails out there serving big production traffic today. But I wouldn't recommend switching an app that big in some other language over to Ruby, and at least as many companies have moved off of Rails monoliths when they outgrew them, like AirBnB for example.
- I mostly agree, though I actually wonder if the energy difference is as big as you say. Yeah the big LLM company datacenters consume tremendous amounts of power, but that's mostly for either training or serving ~millions of requests at once. I wonder what the actual net power consumption is for a single machine doing about as much work as a single ordinary person could do with just enough hardware to run the necessary models. Or what the average amount of energy for a single set of interactions is at one of the big shared datacenters - they reportedly have a lot of optimizations to fit more requests on the same hardware. I think it might be only one order of magnitude greater than a human brain. Maybe actually pretty close to equal if you compare total energy used against work being done, since the human brain needs to be kept alive all the time, but can only effectively do work for a limited part of the day.
- Ruby by itself is still a pretty decent scripting language. I still think Rake is highly underrated as a command runner.
Rails is still a good web framework within its limits. If you want to build a small, modest complexity web app with like 1 or 2 developers and under maybe 6 months of active development, modest traffic needs, etc, it's a good way to get everything up and running fast with best-practices for everything.
The lack of types may start to pinch some once you get an order of magnitude more developer-months into the app than that. Lack of overall speed, threading issues, and memory usage may be an issue once you get a few orders of magnitude more traffic. But while you're within those limits, I think you'll get features out on it faster than any other language or framework.
As they say, a lot more startups have died due to not being able to iterate fast enough in the early stages than from their traffic capacity, hosting efficiency, and bug count once they get into serious growth.
- It's a cool and interesting type of attack, but I really don't care for the breathless clickbait headlines that are sourced to a few security researchers demonstrating an attack in a lab, that has already been patched against and has never been seen in the wild.
I recall, when it was originally created, SSL was a rarity, a thing only for the your bank account and the payment page for online stores, because nobody could afford the CPU load to encrypt everything all the time. Now, it's no big deal to put streaming video behind TLS just to ensure your ISP can't mess with it.