stevewatson301

16 ms·

121.
by stevewatson301 4y ago
I think the current App Store model works fine. There could perhaps be more stringent government regulation around app development and data practices, but I don't believe that's the solution either as it would kill off small time
122.
by stevewatson301 4y ago
This is a particularly bad example since the OOXML standardization process was fraught with issues and there are deviations between the standard and Microsoft’s implementation. For starters, see https://en.wikipedia.org/wiki
123.
by stevewatson301 4y ago
While I agree with your sentiment, how do you think that might work out if phone manufacturers were required to have an app ID blocklist? As an example (I’m not sure what the current state of things is on Firefox these days as it has been a
124.
by stevewatson301 4y ago
> I can't for the life of me figure out why everyone cites Facebook here. And yet, people have a preference for installing apps, as evidenced by the populace that has the app on their phone as opposed to using m.facebook.com on thei
125.
by stevewatson301 4y ago
As stated elsewhere on this thread, the 30% isn’t entirely going to Apple’s pockets — they have costs such as App Store bandwidth costs, support costs for purchases made, and the likes.
126.
by stevewatson301 4y ago
Cloudfront is terrible for DDOS protection though, given that there is a per request pricing (and no, AWS WAF doesn't help as it just imposes additional pricing on top, the only thing it does is to prevent Cloudfront from processing th
127.
by stevewatson301 4y ago
Lambda function endpoints[1] are a replacement for some use cases. [1] https://aws.amazon.com/blogs/aws/announcing-aws-lambda-funct...
128.
by stevewatson301 4y ago
Then again, it depends on the prices that you pay. If you have customers paying somewhat decent prices for your service/product, they interact in an empathetic manner. However, if you price your services too low, you'll get a bunc
129.
by stevewatson301 4y ago
Thanks for providing the original RFC, though reading it I find it to be much worse than I thought because of its ability to detect actions per client. Now there’s a bunch of crypto to prevent the identification of an individual device, but
130.
by stevewatson301 4y ago
I posted a comment a few days ago here ( https://news.ycombinator.com/item?id=31670689#31671551 ) about my views about this “feature”, which I’ll repeat verbatim here. Needless to say, it’s something I don’t like. Original co
131.
by stevewatson301 4y ago
https://archive.ph/bNmbX
132.
by stevewatson301 4y ago
This extension takes an interesting approach to spoofing data, which is nice! In my case, I’m interested in doing the same thing inside of Puppeteer for web scraping, unfortunately it seems like the only possible approach is similar to cont
133.
by stevewatson301 4y ago
Cloudflare has an article too about it: https://blog.cloudflare.com/eliminating-captchas-on-iphones-... In my view, this would just DRM-ize everything on the web. Of course, Cloudflare and Fastly don't talk about this
134.
by stevewatson301 4y ago
Not the parent commenter but this isn’t as far fetched as it seems. Since much is abstracted by the Win32 and other APIs, they could write something to do exactly this.
135.
by stevewatson301 4y ago
https://archive.ph/nX06E
136.
by stevewatson301 4y ago
The law that they’re talking about also mandates cloud and server providers to maintain IP allocation histories and validate customer identities by way of KYCs.
137.
by stevewatson301 4y ago
Fake WHOIS records, you can typically populate anything there. Some geolocation providers blindly trust the values that you put in there (for example, Maxmind); others do triangulation based on trace routes and ping times to deduce if the a
138.
by stevewatson301 4y ago
The field is active even today, you may want to check out TeamOS. (I’m not sure if I can leave a link to it here, so just search for it.)