746 karma · joined April 23, 2020
This site needs to be improved so that alternative, non-spam opinions are not downvoted into oblivion if this thing has to scale according to Paul Graham's dream.
Whenever I say something that I think is true that is contrarian, some people just downvote me. I never downvote my critics unless it's webspam, even if it's a blatant lie. Learn to respect people. Not everyone is going to agree with your view, that doesn't mean they're your enemy or hate you.
Bye :)
PS: If any HN employee is reading this, purge my account under the GDPR, right to be forgotten and any PII like residential proxy ip address linked to it.
A VM inside a VM.
Eventually people are going to write C# in browser? All NPM packages made available in Python and C#? All PyPI packages in browser?
Active X plugins are back people!
Any processor prior to 2014 is old. And any processor after 2018 that isn't a quad core is also old in my opinion.
My Windows PC is fast and its a breeze to work on. Just don't cheap out on a good device. They're worth it.
Just file a security issue on bugs.chromium.org with demo/instructions. If it's a good one, they'll pay good.
I don't wanna give it out since it's publicly linked to my twitter and I've bad mouthed Apple here... (I don't publicly speak against them for obvious reasons)
What if my server is closer than cloudflare? Why is cloudflare artificially limiting?
This is a stupid decision by Mozilla. Too bad Firefox users when visiting websites making their own CDN's without anycast/country level redirects will see much slower sites.
> In 2011 Google wrote an IETF draft to send Client IP information using the EDNS0 extension and this is usually called ‘edns-client-subnet’. As a DNS client, it means that a truncated version of your IP address will be added into the DNS request. The DNS server will use this truncated IP address to make a more informed decision in how it responds so that you can be connected to the most optimal server. This standard is promoted by the Faster Internet initiative and already adopted by some leading vendors.
Because it is designed to keep privacy, the sender has the freedom to limit the client IP information. Instead of sending a full IP address, the DNS server is able to send partial information such as /24 only. For instance, if your IP address is 66.214.81.22, the DNS server will only expose the first three octets, so 66–214–81. Armed with the real IP address of the querying device, the DNS server can now come up with a much more accurate response. With this more intelligent routing, customers have a better Internet experience with lower latency and faster speeds. Best of all, this integration is being done using an open standard that is available for any company to integrate into their own platform.
source: https://engineering.salesforce.com/why-is-edns-important-for...
Cloudflare 1.1.1.1 for consumers kills EDNS "edns-client-subnet" and instead offers the ip of the nearest cloudflare server to the user even if the website is not using cloudflare. This means your website can not ever serve content faster then cloudflare even if you could potentially be faster.
This is the reason why many internet archives do not allow access to cloudflare client dns (1.1.1.1) users as a form of protest.
BTW, Cloudflare allows you to get informed about the end user's ip via a "x-forwarded-for" header.
For non 1.1.1.1 dns users I can just set up varnish and they'll be served via GEO ip lookup so the domain gets pointed to the nearest ip address. This is much cheaper. I'm not going to buy an ipv4 block just for cloudflare dns users.
Their privacy claim is a lie because your webserver is going to be exposed to the end user i.p. address anyways after resolving from the nameserver.
If companies are people, then companies in many 3rd world countries are children. You don't let adults hit children until they grow to be adults.
We need to look beyond the "Price = 0" narrative when we're investigating things that in this new era are free.
The web browsers that meets the PWA requirements are Chrome, Edge, Firefox (to a large extent), Brave, Vivaldi, all available on Windows, Linux, Mac, Android.
Not Safari. And all browsers including Chrome and Firefox are just Safari under the hood (on iOS) so no completion for Apple. Apple does not even allow a competing browser engine.
I wouldn't call this "PWA support".
When I talk to friends at Google that work at Chrome, and tell them to convince Apple to support many of the features, they tell me that they have given up on them, and I can go talk to Apple if I want. They told me they're gonna keep progressing the web even if Apple wants to stay behind, they won't stop.
I've talked to people at Apple about this, they don't care. They always have a far fetched excuse. I know it's not the engineers fault, they are ordered by the upper management.
Instead of giving the money to Apple, we could easily reinvest it to grow.
And yes, I think that Google is still better compared to Apple as far as the web is concerned. I can freely block their trackers if I want to. Google's interests align with the future of the web. Apple's interests are a complete walled garden. As a consumer, for as long as the web thrives, most people benefit. When a wall garden happens, that is when consumers lose in the longer term.