shadowfiend

... Yeah, that's a replacement for your girlfriend kind of like watching TV is a replacement for eating dinner...

The gp's interpretation of that tweet is such a completely incorrect reading as to make one think it's likely disingenuous.

The actual reason here, implied but not stated outright in that one, is that Discord being a public platform, having only numbers to discriminate between users makes it extra-trivial to impersonate someone else. Obviously you can still do some of this with unique usernames (you see slight misspellings, adding harder-to-see characters like periods, etc, as strategies), but these are more complex to execute on at scale and easier to block once and reduce the impact, vs being able to use ~arbitrarily many post-username numbers.

No: https://developers.cloudflare.com/browser-rendering/rest-api...

In front: https://developers.cloudflare.com/browser-rendering/rest-api...

No: https://developers.cloudflare.com/browser-rendering/rest-api...

FaceTime got caught up in patent issues that precluded both opening it up and resulted in architecture changes: https://arstechnica.com/tech-policy/2013/08/report-after-pat... .

The point above wasn’t about value to shareholders but rather about being able to pay the people doing the actual work.

Apple and Google and any app store provider have the ideal goal of zero friction for real, valuable apps and infinite friction for bad, scam apps. They can never hit that ideal, but when you're getting rage from both ends it's likely that you are in a place on the continuum that is far below ideal—you make it a huge pain for real, valuable apps and too easy for bad, scam apps. This appears to be where the Apple store is, at least, and it's an unfortunate place to be. They may be doing their best, but it sounds like their best has some pretty significant room to improve.

While I don’t claim to know the finer points of the law, I believe the judge was pretty crystal clear that Apple was 100% within their powers to kill the developer account that Epic used to do this.

Epic didn't publicly criticize Apple or testify against them in court to get into this situation, they willfully and deliberately broke the legal developer agreement that they signed to get press coverage (they could have filed suit on the anti-steering rules regardless).

Not only did they do this, they then filed suit to say that Apple shouldn't have been allowed to suspend their account—and lost (though arguably won the broader war since anti-steering is currently dead).

There are a ton of things Apple is doing wrong around developer stuff and anti-steering rules and all of it, but I dunno, I feel pretty good about them saying to a specific developer, “actually, you've shown yourself to be willing to ignore the legal agreements you sign, so we're not going to be doing business with you any longer“. Epic's stunt should cost them, if they then want to talk about how they've martyred themselves for developers everywhere. Good work, but a martyr who comes back to life isn't really a martyr, right?

Ah, I think I misunderstood you. Yes, this does mean that you need something else to define the typescript to json schema conversion—either by using another tool or by starting from json schema and getting to the typescript types you want.

Feels like it’s worth that trade off to have a consistent experience consuming other APIs as well, but I could be wrong; I think so far I’ve only used it when I need to consume APIs rather than produce them.

Appreciate the pointer!

You are mistaken: https://ajv.js.org/guide/typescript.html#utility-types-for-s...

Ohp. That sounds pretty annoying. Was this a GitHub scrape of places using the library?

Ajv has supported that for at least a couple of years afaik, and consumes JSON Schema natively which is good for consuming other APIs, not just feeding external clients—its base data format is interoperable, basically.

That’s mostly why I’m curious about the lack of mention :)

What’s the go-to reason to use this over ajv? In particular, being rooted in JSON Schema feels like a pretty big win tooling-wise and interop-wise.

Thesis* | Engineering Hires | Remote

Thesis is a cryptocurrency venture studio whose mission is to empower the individual—we seek, fund, and build products using cryptocurrency and decentralized technology that further this mission. Current and past Thesis projects include Fold (2014), tBTC (2020), Taho (2021), Etcher (2023), Embody (2023), and Thesis Defense (2024). Investors in the company include Andreessen Horowitz, Polychain Capital, and Draper Associates, among others. We are a remote-first company, led by founders who have been operating in the cryptocurrency and web3 space for a decade (actually for a decade ;)).

Our current focus is on building Acre, a Bitcoin-in Bitcoin-out BTC staking platform, and Mezo, an Economic Layer for Bitcoin. Across the board, we are focused on building a new home for Bitcoin holders to cultivate Bitcoin and grow wealth together. Our projects are built with an emphasis on creating something useful with a clear value proposition rather than a perfect technical machine that provides unclear value.

We’re a fun, down-to-earth, fast-paced and highly collaborative team looking to expand our engineering (Go, Solidity, and TypeScript) and product capabilities (amongst other disciplines) and this is where you come in. Join a team that strives for excellence and help us build technology that enables the integrity and empowerment of the individual.

Check out our open positions at https://thesis.co/jobs .

Thesis* | Engineering Hires | Remote

Thesis is a cryptocurrency venture studio whose mission is to empower the individual—we seek, fund, and build products using cryptocurrency and decentralized technology that further this mission. Current and past Thesis projects include Fold (2014), tBTC (2020), Taho (2021), Etcher (2023), Embody (2023), and Thesis Defense (2024). Investors in the company include Andreessen Horowitz, Polychain Capital, and Draper Associates, among others. We are a remote-first company, led by founders who have been operating in the cryptocurrency and web3 space for a decade (actually for a decade ;)).

Our current focus is on building Acre, a Bitcoin-in Bitcoin-out BTC staking platform, and Mezo, an Economic Layer for Bitcoin. Across the board, we are focused on building a new home for Bitcoin holders to cultivate Bitcoin and grow wealth together. Our projects are built with a focus on creating something useful and valuable rather than a perfect technical machine that provides unclear value.

We’re a fun, down-to-earth, fast-paced and highly collaborative team looking to expand our engineering and product capabilities, amongst other disciplines, and this is where you come in. Join a team that strives for excellence and help us build technology that enables the integrity and empowerment of the individual.

Check out our open positions at https://thesis.co/jobs .

The only provider here who is stated to have said they will be complying is Google, right? So not only is singling out cloudflare incorrect, the title itself is incorrect. “French court orders Cloudflare, Google, and Cisco to poison DNS to stop piracy block circumvention” is the correct title for the article contents, possibly with an addendum of Google saying it will comply.

Just to make sure I understand—you're saying that because your family, which is 4x the poverty level income, got this discount, and did not need it, you believe that this program did not help people under the poverty line?

Or is it that because your family, which is 4x the poverty level income, got this discount, and did not need it, you believe this program was not meant to help people under the poverty line?

Which is to say, can you make your point more precisely?

Enforcing past behavior under laws that haven’t come into effect yet is not a great approach though…

They do not. This entire case is about them not being able to use in app purchases (in which case they would pay 30%) or steer people to their site to pay for subscriptions. Spotify doesn’t sell subscriptions from the apps, and thus they pay nothing.

There is no iMessage app. There is a Messages app that implements two systems: iMessage and SMS/MMS. iMessage is the system whose security model is being discussed here, and the security model of SMS/MMS is mostly irrelevant to it.

That feels like the start of talking past each other here heh. GP is making a values statement. If a good product gets to be exempt from the values in someone’s value system, then any product is.

More likely here following the law in this instance isn’t part of your value system, and neither is free/libre software being used on its authors’ terms, so you are (internally) free to decide to buy something even if it doesn’t adhere to the GPL. If I’m right about that, adherence to these things is a (maybe very-)nice-to-have rather than a core value, whereas the GP I think is coming from a place where one of those is a core value.

https://github.com/mssun/passforios might be of interest.