That's just wrong. Telegram is trusted by both Ukraine and Russia. That tells a lot. Also I am living near Russian border and remember well how Durov left Russia and I am quite sure he is not puppet of Putin...
Sites like Hacker News, Stack Overflow, old.reddit.com, and many more greatly benefit from JS. I made GoatCounter tons faster with JS as well: rendering 8 charts on the server can be slow. It uses a "hybrid approach" where it renders only the first one on the server, sends the HTML, and then sends the rest later over a websocket. That gives the best of both: fast initial load without too much waiting, and most of the time you don't even notice the rest loads later.
oh. its worse. the original request for the TLD was only granted because in the application Google specifically mentioned that it should be reserved due to its unofficial use by developers and that if anyone else got it then they might put real domains on it.
I specifically use some .dev domains because of HSTS. Some of us don't cling to http and I prefer an error rather than transparent fallback to unsafe protocol if I screw up the config.
The first point is valid but that is mostly ICANN's fault, they should have proposed it as reserved instead of selling it.
Just my person experience, but I got my relatively uncommon name on .dev for $12/yr so I'm pretty happy with that. While the situation worked in my favor, I agree .dev probably should have been the official internal only TLD.
At my work we have similar issues with all big companies we have some kind of integration. Apple, Google, Facebook... Even Huawei app store decided to copy our apps without asking us first and now we have issues managing them. Too much time is spent to appease those companies and for me it starts to feel like some kind of conspiracy theory...
Verifying phone number is one of the last things which is still effective when fighting against bot registrations. Alternative is to ask money for registration.
Here is idea for hacker news crowd: make service which is a proxy for phone number validation: user needs to validate his phone number once in that app and any other 3rd-party service can ask this app for security code which confirms phone number ownership. We use something similar by offloading phone number confirmation via Telegram bot. Also this proxy service could optionally offload management of "bad" phone numbers used by spammers and add other protections
I'm 100% ok with this. I have the choice of using a Visa/MC gift card I bought with cash. Same as I can do with Netflix. Better than linking a unique ID I use everywhere else.
I think what bugs me the most is that there's no direct need for the phone. It's reasonable to give my phone number to a doctor's office because I need to hear from them over the phone.
> I have the choice of using a Visa/MC gift card I bought with cash.
Technically you can also pay for a burner service to get temporary phone numbers to receive SMSs for registering to services. Can’t attest if any of them are good or trustworthy. I recently looked into it but everything I found was a subscription and/or shady looking.
That's why we offloaded phone validation to Telegram - it is too costly to send SMS in other countries than our home market and spammers are finding ways to get phone numbers for free from different VoIP providers. We need to implement complicated SMS sending limit logic to avoid abuse
At my work we use Capistrano for PHP projects.
It does not matter in which language project is written.
You can still use ruby Capistrano and it works good enough
I haven't see any project which feels fast which are written in React. But most important thing for me which is broken (because it is too difficult to catch all edge cases) in all the JS frontends is the broken navigation (browser's back and forward almost never work as expected, bookmarking links are broken because state is in JS etc.)
This can definitely be fixed (it involves making sure the relevant operations in the app manipulate `window.history` and either indicating location state in the browser via the hash portion of the URL or building the server to work hand-in-glove with subpaths), but it requires more work than the default navigation one gets with a multi-page app.
I've seen good frameworks for managing this but I agree that developers tend to forget it.
