AgentK20

So they're going to pay back the subsidies they took from the various governments that they received in exchange for opening those stations.....right?

Tailscale? Unless I'm misunderstanding the use-case (which I probably am)

I mean, if you're looking at this in terms of an infrastructure spend as compared to running a new undersea cable to a remote island/village/site, which may cost millions of dollars, this kind of upfront cost actually seems pretty reasonable. I'd love to see comparisons to similar infrastructure projects.

Sounds like there’s some additional EMI shielding that is needed for future iterations of megaconstellations. On the plus side since they have relatively (compared to geosync satellites) short lifespans of only a few years they can probably sort this out by passively fixing the next generation of satellites. Additionally, from what I have seen of the way they pack the Starlink satellites into the fairing, they seem to be volume constrained in the fairing rather than mass constrained, so there may be additional mass budget available for little overhead.

One thing that I feel is probably not being thoroughly considered is that, given that this will likely be a credit/debit card transaction, just how many fraudulent card charges will be rung through this system, and how this will likely result in Twitter/X being banned by Visa and the other payment processors.

One of the many reasons that almost NO ONE accepts less than $2-3 on the internet for things is that if you receive a chargeback from the bank due to fraud, there is a $20-$100 FEE that is applied to your account (in addition to the transaction being reversed), and if you get too many of these (both by percentage of transaction count and dollar volume) you will be banned from the payment processor.

With the proposed $1/yr fee, it would be trivial to pay a few hundred dollars on a shady website for stolen credit card numbers, ring up huge numbers of $1 charges, and induce tens of thousands of dollars of damage while harming X's relationship with their payment provider.

That's great in a world where people are unable to resell devices, but the concept of "ownership" is fluid in a world where users can sell their devices. I can think of many scams that could abuse a system where anyone who presents an ID associated with a receipt can claim "ownership" of a device and bypass various security measures. Keep in mind, Apple's threat vectors range from "random phone thief" to "state level actors", with equally as varied clientele.

And yet some of us are just finding out about this feature now.

To quote the article:

> Salted and hashed passwords (mainly concerning users prior to 2018 when Discord.io began exclusively using Discord for logins)

So it sounds like they used to have their own accounts before integrating via Discord OAuth, and some users may be affected by this. Unsure if they didn't delete users' hashed PWs once they migrated to the OAuth flow or something like that.

They did post a long writeup if you want to hear straight from their newsroom: https://about.fb.com/news/2023/05/metas-position-on-canadas-...

Disclaimer: Meta employee programming games, unrelated to any of the ongoing discussions.

...Is this article plagiarized from this article posted June 26: https://www.entrepreneur.com/growing-a-business/the-damaging... ? It was even submitted to HN and had a few hundred comments: https://news.ycombinator.com/item?id=36500448

JFC, how is the _maximum_ sentence for (what I would consider had I been the victim) ruining her life for nearly a year (July '16 to June '17 from the looks of it) only ten years? I'm sure there will be a separate civil suit for loss of income, peace of mind, etc, but I would think that they would throw the book at someone like this. Not to mention the fraud he committed by forging policy cancellation letters...

I think there's also something to be said here about the fact that a child of age 7 was allowed to play a game rated age 13+. Sure, "its cartoonishness allayed their worries"....but the decision to rate a game for a certain age is taking in a lot of different factors. If you take a 7 year old to a PG-13 movie which then traumatizes your child, you don't get to complain that "the poster looked so cartoony so I thought it would be fine" and then claim that it's the movies fault.

That said, I do believe that online games ratings should take into account additional factors like monetization models, expected screen time, tendency to be habit-forming, and that information presented to the parents. Really I feel that parents are underequipped these days to deal with the volume and types of media their kids have the ability to consume.

The github.io site that they include the link to is the actual repository that can be read by Helm, in particular by it polling the known "index.yaml" file at https://teslamotors.github.io/helm-charts/index.yaml. Something _could_ be done using Github's "/raw" endpoint, but generally speaking Github pages works better for this sort of purpose and also is built to be a CDN, meaning it has additional caching layers in front of it that make it more performant.

ocelotpotpie's sibling reply to this has good explanations for the terminology. If you're curious to actually see the software:

* https://www.spigotmc.org/wiki/bungeecord/ - Older, less-performant but still used by some teams

* https://papermc.io/software/velocity - Newer, more performant, maintained by the team that makes Paper, one of the leading performance MC server implementations.

For context of scale btw, when Hypixel had 200k+ players online at peak we had something like 2,000+ 1U E3-1271v3's each with 32GB RAM, all colo'd in a single DC in Chicago. Egress is 70-80gbps or so 95th percentile, with most months (at high peak) egressing 10PB/mo+ of real-time, uncacheable data.

Ohhh, very interesting. I'll admit I only took a cursory glance at the code when it was first announced on the Paper discord since I'm not as much involved with MC anymore, but that's good to know. I'll need to dive in again one of these days.

Keep in mind that the entities-in-viewing-range scales quadratically with players. 10 players in view distance is (at 20 ticks per second) 180 packets per second *per player*, or ~2k pps on the server. 100 players, ~200k pps. 1000 players, ~20m pps. All on a single Java thread, hence why Minecraft typically performs better on high clock-speed low(er) core count CPUs. Folia splits the load for the world into multiple threads, but only on a per-region basis, with each 512x512 being (potentially) on a different thread.

EDIT: Correction, as doctor_phil points out that's a quadratic scale not an exponential scale. Derp.

Always fun to continue to see innovation within the Minecraft Java space.

At Hypixel we ran (and I believe they still do run) a custom fork of Spigot from 2014-ish, with features from each sequential update to Minecraft being added to our fork via our Spigot fork. This let us diverge greatly and customize the Minecraft protocol to our own needs, saving hugely on internal bandwidth and letting us optimize crap out of the L7 "BungeeCord" reverse-proxy we used.

Dupe of: * https://news.ycombinator.com/item?id=36248815 * https://news.ycombinator.com/item?id=36248876

And what prevents a Malicious Actor (older student? friend who already graduated? someone who wants to sell them?) from acquiring multiple of said age verification tokens from different vendors? Well, now there has to be a database somewhere of all of the tokens that have been created along with the ID number of the person who acquired the token. Who maintains this database? The government? The companies who we don't want storing our data?

Sure, it adds more steps than just "click this checkbox if you're an adult" but kids/teens are a crafty bunch and, unlike drugs and sex, a) the penalty for violation of the rules is not immediately obvious (to the youth, OR even to society) and b) the act of violating the rules is not obvious in itself to people who aren't on that person's phone: there's no physical items left behind for parents to notice.

Effectively what we're talking about here is trying to solve the Sybil Problem, which has no widely-accepted solution.

Oh, fair enough. I hadn't been keeping up too much but hadn't realized they had progressed that far. I'll have to do some tinkering this evening.

EDIT: Actually there's apparently been a lot of progress recently that I hadn't kept up with; see the replies to this comment.

Original message: From a quick peek at the source, this depends on the ChatGPT API for the underlying LLM. It could probably be modified to use a local copy of an LLM, but most models I've seen are 300GB+ and require significant computational resources to operate (think several $15k NVIDIA A100 compute nodes). There's a lot of effort being put in by the open source community to minimize these models and run them on commodity hardware, but as of yet the quality of the responses from the model are correlated with how large (and therefore how much compute) the model has. Give it a year or two and it'll probably be more reasonable to integrate a local LLM for gaming purposes.

Why are the people who ran these companies not in jail?

Reading through the actual text of this bill (obligatory I am not a lawyer), I don't see _anything_ that actually would allow a Person ("a natural person, including a citizen or national of the United States or of any foreign country.") to be considered a "Covered Entity". The language for "Entity" _clearly_ specifies that it is only referring to artificial entities e.g. LLCs, Trusts, etc.

I have my own opinions on the bill, but I don't see a legal pathway in this bill to apply any of the restrictions on it to a Person, only onto companies.

So that it doesn't get buried under a downvoted branch of the comments, here is the original text of the bill for anyone who wants to read it directly: https://legiscan.com/FL/text/S0254/2023

I think the parent comments point was that it’s difficult, if not impossible, to verify the security of even a particular hash. It’s still vulnerable to the same dependency chain vulnerabilities as pinning to latest, but instead locking in a particular version and _hoping_ that it wasn’t pwned. Additionally, you are then not getting any exploit fixes that may be included in newer versions, so even if there was a vulnerability you are now stuck with it until you decide to manually update.

To be honest if you’re that concerned with dependency attacks like that then you should just be hosting your own image registry and building your images yourself, and then only being vulnerable to dependency attacks within the OS distributions and such.

I think this is honestly less about the notoriety of .com, and more about the lack of affordable and available domains for startups to purchase. Got a five letter named startup? That’ll cost you tens of thousands of dollars, IF you can even get it. Meanwhile there’s hundreds of gTLDs that you can buy a domain on for $10-$30/yr.

Always happy to see further development in the field of battery chemistry, but I temper my expectations with the realities of both cost and difficulty to mass produce. More investment and breakthroughs are good, and they push the industry forward, but keep in mind that most people (myself included) would rather a cheaper EV that takes twice as long to charge than vice versa (assuming a base capacity that is enough for all but roadtrips). The article does point out though that short-duration battery-powered flights may be a perfect application for a more pricey but higher-density battery.

Keep in mind that in order for a nuclear explosion to occur, a very precisely timed series of explosions must occur within the device to trigger fission (and then potentially fusion, depending on the type of device). If the inbound missile is kinetically damaged or destroyed before it gets the chance to trigger, then the conventional explosives will likely detonate within the missile in a way that does not reach criticality, resulting in a conventional explosion with a small amount of fallout from the nuclear core that wasn't triggered being dispersed.

Another thing to note about garbage-collected languages (like Java with the G1 collector) is that blocks of memory will often be *copied* to other parts of the physical memory as part of compaction phase [1] (see quote), in order to be able to provide large segments of sequential space. Since the GC is designed with performance in mind rather than security, the original copies are not zero'd as part of this compaction, and instead their raw data will potentially stay in memory indefinitely until overwritten by another part of the application, and will not be zero'd upon termination of the application. Because of this, even with meticulous tracking of references and "raw" memory access only, GC'd applications can leave traces of secrets on memory. There may be workarounds for this by exclusively using "Unsafe" methods, but that drastically limits your API-interoperatility with libraries and such.

> G1 reclaims space mostly by using evacuation: live objects found within selected memory areas to collect are copied into new memory areas, compacting them in the process. After an evacuation has been completed, the space previously occupied by live objects is reused for allocation by the application.

[1] https://docs.oracle.com/en/java/javase/18/gctuning/garbage-f...