rattlesnakedave

Lucky you. Mine is using ChatGPT to review code written by curmudgeons that don't use it.

We already have state level actors laundering false information through global news outlets. What you describe is really only a continuation of that. Better processes for vetting information (be it through classical "is this source trustworthy" markers or pgp keys on the high agency end) is the only way out.

Perhaps we could form a similar agency that could find and prosecute those stealing the catalytic converters.

I wouldn't call "having a catalytic converter" installed in an industry standard manner a "fundamental design flaw."

> So the only important difference is that Buffer creates a mutable view at slice().

No, it also (from the article):

> introduces numerous methods that are not available in other JavaScript environments. Consequently, code leveraging Buffer-specific methods needs polyfilling, preventing many valuable packages from being browser-compatible.

No. Wearable AR tech is the future. The trend has been "get this device as out of my way, and integrate it into my life as much as possible." e.g: big iron -> desktops -> laptops -> smart phones enabling greater mobility and flexibility of use.

We're just starting to see the next state of it with wearable tech. Smart watches. Airpods. Many people have these. Many people wear them for extended periods because they're comfortable interfaces to the services they care about. A family member has a hearing aid that's connected to their phone's bluetooth. Comfortable enough to wear all day & discretely listen to phone audio whenever. I think that's the next step (obvious evolution from airpods). Glasses -> AR displays shortly after.

As a consumer, this doesn't really hurt me. I get good products for cheap delivered in two days or less. I don't see how the FTC is helping me here.

At least with credit cards you have some form of recourse. ACH/Debit cards you're totally hosed.

They shouldn't be able to set arbitrary fees on different payment methods. They should also not be allowed to advertise an "autopay discount" if they price discriminate different payment methods. It should be a "give us your bank account information discount" or something.

> It enables the US to weaken other countries by draining away their intellectual capacity

Are you implying that if they don't emigrate they'll be properly utilized in a way that is a threat to the US's current hegemony? If so, why aren't these countries doing that now?

This has not been my experience. Paying for admission to museums/sporting events I apple pay from safari on my phone then am presented with a QR or a pass to add to my apple wallet. It's really nice and I much prefer it to standing in line.

Code is law. The issuer of tokens backing rwas should be able to figure this out and reissue.

I'm not sure the Sam Kinison approach scales. We need cheaper cleaner energy. Growing food locally just shuffles the variables around for marginal emissions benefit with massive hits to scalability.

Lens Protocol, some DID stuff like disco.xyz, there are a few that gate access to interesting communities (more than just "here's a jpg"), I think benddao.xyz will be good for borrowing against IP (defined as NFTs). All still very fledgling, but I think these are the types of use cases that will last.

Who is this, and why do so many people care they got burned by an (even at the time) obviously overhyped NFT project? There's nothing of substance here. Certainly nothing technically compelling enough to warrant the HN front page.

There are plenty of legitimate web3 and defi projects out there. The ethereum network, on-chain real world assets like USDC, protocols like Uniswap and AAVE, interesting stuff happening in the DID space. This blog post just reads like someone (who is this, by the way? this is a single post on a bear blog- why are we taking this so seriously?) who got caught up in and then burned by an overhyped NFT project.

I'm always incredibly skeptical of any set of tweaks that is supposed to take off-the-shelf software and make it more private (how?) or secure (from what?). I'm sure some of these tweaks do that, but can't help but think they increase your attack surface over all (unless you have the time to read and think carefully about each settings change- in which case, you probably could have just changed the settings yourself).

.zip is not an inherent security risk.

Yes

Judging by the amount of infosec dorks I’ve seen kvetching on twitter over .zip, it’s probably blocking less popular TLDs.

> We're engineers, we could implement location tracking in a way that only the user being tracked has access to it. Google could store it in the cloud but encrypted with a key Google has no access to.

Many other features that people find useful wouldn't be possible in this world. If that's the product you want, find an alternative that's not Google maps. I suggest OsmAnd.

You're leaving out the critical part where the VP of whatever signed off on the press release, then moved on while the feature was implemented as described in the release.

> Location History: Location History is a Google account setting that is off by default, and for those that turn it on, we provide simple controls like auto-delete so users can easily delete parts, or all, of their data at any time. Some of the places people visit — including medical facilities like counseling centers, domestic violence shelters, abortion clinics, fertility centers, addiction treatment facilities, weight loss clinics, cosmetic surgery clinics, and others — can be particularly personal. Today, we’re announcing that if our systems identify that someone has visited one of these places, we will delete these entries from Location History soon after they visit. This change will take effect in the coming weeks.

This seems to be pretty clearly what was happening, as described by the author of the article. *If* the systems detected an abortion clinic visit, it was deleted. No further guarantees were made in the blog post. The same post provides links to documentation on managing your location settings and history, so the user can adjust if they are unhappy with Google's behavior.

> The user shouldn't have to understand how technology works, or have a grasp about how hard the problem is.

They enabled location tracking, and got mad when their location was tracked. You can really only do so much from the product side here. Personal responsibility has to come into play at some point.

To use many of the snapchat filters (specifically ones that have info about the weather, the city you're in, etc.) you have to have your location services enabled, at least while using the app. These are pretty popular, so most people have their location services enabled.

There's also the "snap map" which for some reason doesn't freak normies out, and they have location services enabled for that as well.

No

You get to decide what fork you run.

Infinitely divisible

What have they produced since 1940?

It depends on what you mean by "smaller." At the majority of smaller companies, it's just CRUD app stuff, probably in C#, with significantly less freedom (often beholden to very non technical middle management).