BHSPitMonkey

You can just use a Keepass database and then you aren't locked in to a single OS (KeepassXC, Keepass2Android, etc.). Synchronize any way you like.

I know the dots seem large in the visualization, but these satellites are approximately the size of cars. They're specks of dust at this scale.

Free File Fillable Forms is offered without limitation, and should handle any situation. The problem is that this is still too intimidating for most people without a guided wizard or a human advisor because of the intrinsic complexity of our tax code and the amount of data entry involved.

https://www.irs.gov/e-file-providers/free-file-fillable-form...

It might be palatable if it's quite a bit less expensive, which could be the case if we start passing externalized costs (e.g. offsetting the impacts of carbon emissions, pollution, noise, etc.) down to the consumers who use these services.

Scraping and an official API are equally "dicey" in that the method isn't relevant to the question of how the content itself is licensed to be used.

I've been to Paine, and apparently I just ignored everything outside of the passenger facility. Oops!

Are you thinking of Boeing Field? Paine is a tiny little luxury airport with 4 gates.

Self immolation implies making a personal sacrifice in the name of a cause. In this case, they betrayed a set of their users with the goal of greatly increasing their wealth, and that outcome is now happening.

This doesn't track. They spent a lot of time and energy coordinating with the authors of popular mobile clients, and could easily have extended some means of letting them continue to operate given that they were clearly not harvesting content for themselves. Meanwhile, content can still be harvested for LLM training without the API (by using the HTML site).

It seems like the real intent was to regain control over the surfaces users use to consume the site, especially on mobile.

The same is true for an asset's licensing/royalty-free status, which creators are surely aware of when pulling these things in.

You can also add TOTP secrets to entries in KeePassXC and generate/copy codes there (Ctrl+T).

Or they spare you, betting you'll leave on your own terms and they won't need to pay you a severance.

I continue to use SketchUp for that, as is the closest thing to CAD I can quickly work in without needing to spend a month in training first.

This is your regular reminder to audit your password manager for accounts you no longer need, and then go and have those accounts deleted.

Of course you can't guarantee that your data will actually be purged, or that it hasn't already been compromised from these places - but less exposure is better than more exposure, right?

> Or build a couple dozen and put in a lower orbit. Not like it would make a dent in China or Russias military budget, or require any tech newer than 20 years old for them.

Look at this animation[1] for a moment (click the >> or >>> button to speed up) and think about what it would actually take to get "in front" of enough satellites to block out a given geographic region; even just a single city. There are hundreds of satellites in each orbital plane, rapidly cycling through and taking each others' place.

You obviously cannot have counter-satellites in a geosynchronous "position", and you also can't have satellites simply move between greatly different orbits (or phases of existing orbits) willy nilly; The delta-V requirements are just too great. This just isn't a feasible strategy.

[1] https://heavens-above.com/Starlink.aspx

Maybe, but unless your goal was to deny service to a small, fast-moving window of the earth's surface you would need quite a lot of these.

Granted, you've found the one (and only?) notable exception to the "no legitimate torrent use cases" rule that I can think of. :)

And this has a legacy roughly as long as BitTorrent itself. The fact that BT never established a footing in other use cases (even those where you would think it would be a great solution) is telling.

> After the recent few years of inflation middle class is now subject to higher tax brackets than ever, and poverty class is being taxed at almost 30% if you include some states' state tax.

Under the 2023 tax codes, a single filer in California would have to have an household income of $118,250 in order to see a 30% effective tax rate across federal and state taxes combined. I understand $118k might not go as far as it used to (depending on the specific location), but that's hardly the "poverty class". Under the same conditions, a $50,000 income would see an 18.84% effective rate.

Both calculations assume the standard deduction is used; common tax credits and deductions would bring the effective rate lower. These were calculated using: https://smartasset.com/taxes/california-tax-calculator

I don't disagree with the premise that taxes, both federally and at state levels, could be more progressive than they already are, ceteris paribus. Property and sales taxes are broken in this regard, and the obscenely wealthy have too many pathways to avoid contributing meaningfully to the nation's collective tax burden.

Apart from STS-1, we also have the even more recent/relevant SpaceX example of this happening: https://en.wikipedia.org/wiki/Crew_Dragon_Demo-2

With both Crew Dragon and Starship, there will have been _many_ successful missions involving un-crewed variants of the spacecraft (Falcon 9 and Cargo Dragon were both well-proven systems before crew was a possibility).

Your clone seems to be 4 commits behind the version I'm seeing in most mirrors, which has the following HEAD:

    commit 15e6e48bef0216480661444a8d8b348c1cca47bb (HEAD -> master, origin/ma
    ster, origin/HEAD)
    Merge: dc94882c9 2f57c5a0e
    Author: Narr the Reg <juangerman-13@hotmail.com>
    Date:   Fri Mar 1 01:57:00 2024 -0600

        Merge pull request #13198 from zhaobot/tx-update-20240301020652
        
        Update translations (2024-03-01)

I see several on GitLab.com with identical commit histories, for what it's worth.

Android built their own implementation of the proprietary Java language to be able to run programs that were written to run on the official JRE. Can you imagine if Oracle tried to sue Google over that? :)

Obviously piracy plays a large (maybe the largest?) role here, though I wouldn't overlook the modding use case. I would be quite interested in running titles I legitimately own on more powerful hardware where I can play around with the resolution and framerate freely (and would have already used Yuzu for this purpose by now, but for laziness).

Existing discussion: https://news.ycombinator.com/item?id=39593647

Existing discussion: https://news.ycombinator.com/item?id=39593647

Commuting to/from an office is usually a prime example of when a laptop's weight would matter.

Presumably even in a single-payer system, you still need just as good of an accounting of costs and care provided. The data needs are all still there, just fewer parties are transacting.

> To give ABQ police the benefit of the doubt, that pattern could also be compatible with more gun crime equaling more surveillance. It would be nice to have enough gun crime and sensor location data to see how true that is.

The very point of the article is that, absent leaks like this one, there could be no way for anybody to independently study or verify the fairness of the sensor distribution, or even the real efficacy of the reports the system produces—which is a troubling situation to be in when the state has an outsized amount of power to prosecute people based on potential junk science that will be hard for defendants to challenge in court.

The answer isn't to give police departments the benefit of the doubt (which they so rarely earn), but to demand better transparency and citizen oversight of the technology poised to be used against us.

Yep, it was added fairly recently. Exciting times!

"Engine-rich exhaust" is another one that gets a chuckle.

For those wondering, it refers to when a rocket engine is literally burning itself into oblivion—so the exhaust plume is compromised less of fuel particles and more of, well... engine :)