Thanks, that's a great source! Definitely illuminates a part of Cloudflare's infrastructure I had no idea about before. Interesting to hear about their cooperation here given their publicly very anti-censorship reputation.
Does it? IMO it looks very outdated and cluttered compared to most editors. Clicking around a bit, this screen specifically stood out to me as lacking a lot of visual hierarchy: https://i.imgur.com/Y7iBS2p.png. It just kind of reads as a visual jumble with too many elements competing for your attention with slightly different/incoherent styling—I count 5 different unique button styles on this page alone, with some buttons having flat borders, some buttons having shiny highlights, and 3 completely different shades of grey button borders. Definitely doesn't feel "designed" to me.
I heard recently during the big government purge that a lot of the actual mechanics of that purge functioned by revoking people's Dreamweaver licenses, and that a lot of .gov websites run on Dreamweaver. Probably the US government is singlehandedly keeping Dreamweaver alive through large annual contracts for new features. I don't have any concrete sources on this, it was just Twitter gossip, but it makes a lot of sense to me—Dreamweaver provides the ability for non-technical government employees to edit the site, low system requirements for the servers, and presumably enough Enterprise features to ensure template homogeneity across an org as large as USG.
You can't make that statement blindly without knowledge of the entire cryptosystem and threat model. For example, to me, an encrypted version of my email address, as used by many ad networks to do retargeting, is still sensitive information if it lets Walmart serve me ads based on my Google search history.
Yes, I think they should rephrase it so that it's literally correct. Personally, I have a very high trust in the safety of Signal's encryption and security practices. But privacy policies aren't for the Signals of the world, they're for the ad networks and sketchy providers. For example, many ad networks collect "Safely Encrypted" email addresses—but still are able to use that information to connect your Google search result ad clicks with your buying decisions on Walmart.com. Whether something is "safely" encrypted is a complicated, contextual decision based on your threat model, the design of the secure system in question, key custody, and lots of other complicated factors that should each be disclosed and explained, so that third parties can assess a service's data security practices. Signal is a great example of a service that does an excellent job explaining and disclosing this information, but the fact that their privacy policy contradicts their public docs lessens the value of privacy policies.
However, my understanding is that airlines have much more sophisticated per-flight and per-passenger models that calculate the predicted no-show factor based on the historical rates for that particular route (e.g. you're more likely to get more no-shows in business class flying from NYC to SF compared to holiday travelers with a reservation on the Florida Keys)
Thanks, that's a fair point that I was overlooking. When I say a "federated server", I don't just mean a self-hosted PDS, I mean a third party app that potentially has its own lexicon and design decisions. Creating a robust third-party app that can meaningfully interact with the Bluesky network is still a very difficult engineering challenge, which I think this article does a good job demonstrating—that was the tension I was trying to underscore in my comment. Bluesky may be solving those engineering challenges for those clients who are satisfied with Bluesky's frontend and AppView, but every single other app built on top of ATProto will have to resolve those same challenges. This is directly downstream from Bluesky's "global firehose" topology and various design decisions that stem from that.
AppView is a specific term of art within the Bluesky federation architecture: https://atproto.com/guides/glossary#app-view, you were incorrect in identifying the public frontend repo as the AppView.
This is great to hear—my current understanding of the most recent state of the art on the topic is https://alice.bsky.sh/post/3laega7icmi2q which mentions that the self-hosted appview is not yet open source. So I'm glad to hear the situation has changed in the past 3 months.
Note that all of this reflects design decisions on Bluesky's closed-source "AppView" server—any federated servers interacting with Bluesky would need to construct their own timelines, and do not get the benefit of the work described here.
Lots of competitive games still have LAN options because they're basically required for reliable in-person tournaments. I'm familiar mostly with Nintendo games like Smash, Splatoon 3 and Mario Kart but even very modern games like Valorant have the technical ability to run LAN servers (even if the game's publishers keep the actual LAN servers closely guarded and only use them for large in-person events). And of course CS and LoL and similar have LAN modes
No? They made a goal to show 0.0000 in as few places as possible, and they got as close to it as they could without compromising their other requirements.
Do any companies pay bounties for path #2? My understanding is that it's forbidden by most bounty programs since it could be seen as a form of extortion.
For #1, as tptacek says, it would be trivially easy for Google to shut a service like that down as soon as it was created, and prosecute the people running the service under the CFAA. Also, the amount of demand for that kind of data is pretty small given the number of email address databases already available online through legal means (e.g. Zoominfo, RocketReach, etc). It's a path filled with a lot of risk and not a ton of reward.
> The dollar value of a responsible report going up means more responsibility overall and less problem leaks, exploits, etc.
Does it? I just had a bug bounty program denied for budget approval at my work because of the cost of the bounties and the sufficiency of our existing security program. On the margins, it's not clear to me that the dollar value of a report going up is incentivizing better reports vs pricing smaller companies out of the market.
It's only easy to miss a comma at the end of a long expression because you need to calculate whether it should be there in the first place. If commas were always required unconditionally, it wouldn't be a problem.
Don't let the perfect be the enemy of the good. I'm sure that 99% of the people who are requesting trailing comma support care about select lists. And CREATE TABLE for the rest. Yes, the SQL standard has a huge surface area of custom syntax (rather then most programming languages which have a smaller number of composable atoms), which makes adding "consistent" syntax changes a challenge, but it doesn't mean you need to boil the ocean. Just get trailing comma select lists into a version I'm likely to use in the next decade and I will love you forever!
CLS was roughly designed to measure annoyingness in terms of "moving layout elements". I'm sure Google has even more nuanced signals to measure e.g. ad coverage vs content coverage
Right, they're saying that the title is misleading/ ambiguous because it confuses the order of defendant and plaintiff, so if you just read Apple's motion you'd be confused about which is which and who Apple is arguing with
Yes, sorry, I was being maximally-broad in my comment but I would think it's very, very, very likely that OpenAI is currently charging huge margins and markups to help maintain the cachet / exclusivity / and, in some senses, safety of their service. Charging more money for access to their models feels like a pretty big part of their moat.
Also possibly b/c of their sweetheart deal with Azure they've never needed to negotiate enterprise pricing so they're probably calculating margins based on GPU list prices or something insane like that.
Right, and DeepSeek doesn't employ any because they're a bunch of quants who are used to building internal systems. I don't see how this responds to OP's point.