cremp

As someone whose seen first hand how addictive it can be among adults with type A personality, and how it causes relationship issues because they can't stop consuming the content - it feels to me true about the lawsuit itself, but all other social media is doing the same doom-scrolling.

Why Snap is choosing to list it's ties with DHS to get into federal court is confusing - what benefits would Snap get by going to federal?

Back before ClusterFlutter (which was just a lot of Java object type-casting, large multi-dimentional arrays, and overflow math) botting was pretty easy to write yourself with very little JVM knowledge.

Bans were (and still are) pretty hard to come by as long as you pay for a membership.

Great scripting language, but has a pretty troubled past.

Once the original creator moved on from ownership, the new owner also had a business with Runescape botting.

The story is that it didn't go well for the maintainers of Autohotkey until another person took the reigns.

This might be a good plug for Morphie or Revanced patches to automate the patch process.

> a basic level of device security across all iMessage threads I have

Is that really true though? Jailbroken phones, iMessage may still work. Any device security gets thrown out the window.

You also can't expect everyone to have an Apple device for security, which we've seen time and time again SS7 being weak - So is the requirement to remove SS7, for everyone to jump on the Apple train?

I see Beeper as doing Apple a service, not so much a competing platform, but a gateway to the iMessage ecosystem - 'Hey, this would be pretty cool to use without this app and have it native' vs the 'Only Apple devices can use this.'

> More and more of the internet is now moving behind Cloudflare

This is a big double-standard here on HN. Everyone hates Google for making decisions on behalf of the internet as a whole; yet Cloudflare has done the exact same thing with a different OSI layer.

I'm not very trusting of Google, but I certainly dont trust Cloudflare any more-so, because they keep things much closer to the chest.

For the overflow, Jagex with RuneScape did it in Java. They also did stupid Object arrays 7 or so levels deep, doing casts on casts in between. The bytecode itself made the actual runtime slow to a crawl (anywhere from 5 to 10x slowdown.) This was circa 2014.

Spit-balling; when will they put GSM chips in them? The cost of a data-plan could easily be reached with estimated figures for ads and selling usage data.

For maven, to push artifacts via the correct mvn deploy:deploy-file requires a S3 wagon (transport layer) software to actually make the S3 calls. For bigger orgs, having everyone use a wagon is a non-starter.

All I'm seeing this does is give the proper http endpoints so you dont need the wagon. Is it worth ~2x the price, no, but it's better than the other enterprise-y solutions.

Samesite won't break it if you set it none. Eg samesite=none Google failed to set it before the official rollout.

Reason is that sso effectively uses an iframe or popup to a 3rd party auth provider (Google, Microsoft, Auth0...) Provider saves a cookie with that state (from something like accounts.google.com) and usually reads it back from first party context.

If samesite is not set to none, supporting browsers are not allowed to write cookies on the auth domain from the firstparty context, and so the firstparty scripts don't think it ever happened, even though it did. First party scripts can't read it and so sso failed.

Corrected; Thanks.

Didn't realize the US was that bad.

Maybe I'm just skeptical and a cynic, but...

> VPN with an in-app purchase

Lets pay for a product, and they have the ability to sell that data.

I get, acting like a pi-hole and what-not but, a VPN for that task seems overkill.

I'm not saying that the product doesn't have it's use, but it is not how DoH should work.

I'm trying to bolster the point that they are promoting logs and more importantly, blocking DNS queries.

How can I trust the DoH endpoint if I know they have an active product whose purpose is to log and not give back the requested IP.