exactly

I’m starting to suspect 99¢ isn’t a sustainable price point.

This doesn’t make sense as described. The Mac and its apps are optimized for keyboard and mouse. A tablet form factor would at a minimum require Apple Pencil; fingers aren’t precise enough. Combine that with the terrible iOS/iPad virtual keyboard and it does not seem compelling.

Moons vs. dwarf moons? (Sounds like a fantasy novel series.)

Apple has not made the necessary APIs available. Only those two apps have animated icons. They’re made by Apple and so they are able to use the private APIs needed to do it.

Or they changed the headline and due to caches CDNs or other reasons you didn’t get the newer one.

archive.today has your original headline cached.

Thanks for posting. While it’s a needlessly provocative headline, if that’s what the article headline was, then that is what the Lemmy one should be.

That is odd. It’s not what I see:

A very poor Lemmy article headline. The linked article says “alleged” and clearly there were multiple factors involved.

I have used the Excel/Word/Keynote formats with iWork and it’s okay. MS Office is the de-facto standard format and recognized by Google Docs, OpenOffice, and of course MS Office.

I don’t think it’s a truly open format like ODF, but you can be sure it’ll be recognized everywhere for a long time.

deleted by creator

It’s a PR issue not a legal one.

This draft spec was eventually published as RFC 9562. Compared to the previous spec it adds versions 6, 7, and 8, plus best practices guidance.

Basically, there are a bunch of UUID alternatives that arose to fix the problem that UUIDs are bad for use as database keys in large tables (here’s the perspective of MySQL experts Percona). A bunch of these alternatives are actually linked from the RFC, which I haven’t seen done before. Version 7, in particular, is meant to address this use case.

There also needs to be some way to indicate that a JSON construct is a Set, Map, plain object, or array. You’d want a date/time type as well.

Without breaking existing JSON parsers, the way to do that is to add metadata like a _type field to an object, or to add a “sidecar” object like superjson does. Which works but is ugly IMO.

Then there’s BSON, YAML, JSON Schema, and the one we don’t mention ₓₘₗ. To my knowledge all of those could be extended in a way to support new types, but require the producer and consumer to both understand and follow whatever convention you use. They lack the universal interchangeability of JSON.

Set and Map would be more useful if they were compatible with JSON. I see a lot of people using an object as a dictionary or an array as a set because of that.

Sometimes it’s the only option or the preferred option.

I haven’t. Maybe someday I’ll be willing to, but not today. It’s a hassle and extremely intrusive to provide my bank statement and photo ID to a company whose security I don’t trust.

That’s usually how I pay if someone requests money. Venmo is owned by PayPal but my account there works just fine.

I thought about that, but they ask for enough info that they’d be able to identify me. And then they’d probably ban me. At least right now I have the option of restoring my account, even though I have no intention of doing so.

True, it’s a private (not local) IP. It could easily have connected to a remote system, as their proof-of-concept did.

This code execs cmd.exe and pipes output to and from a hardcoded IP. That’s pretty weird. What’s running on that IP? How does the extension know something is there?

It looks like VS Code has no review — human or automated — or enforced entitlement system that would have stopped this or at least had someone verify it was legit.

Their findings included an extension that opens an obvious reverse shell.