Hacker Newsnew | past | comments | ask | show | jobs | submit | psnehanshu's commentslogin

Warnings are ignored. It's much better to fail fast.

There's also React Native Web

I'm sorry what

I find it is a good idea, it allows developers to cleanly define how to structure elements without random divs sneaking in.

It requires a strong design system and it probably makes it harder to use some web APIs but those can be reasonable tradeoffs


Speaking of which, is there a Tailwind CSS equivalent for React Native? I find passing `style` objects around (ala CSS Modules) to be a pain after using Tailwind for so long in web projects.

EDIT: Found one that's going v5 soon, looks nice. https://www.nativewind.dev/


In case you want to use React to make Web sites as well.

They should make a version of that runs as an app on a phone

They have one, it's called React Native Web Native

Twitter is built in React Native Web

Or atleast should have been Hack

TCP ensures what gets sent on one side gets received on the other side. TLS just encrypts the data. So even without TLS, random corruptions won't happen unless someone does MITM attack.


No it does not. I've had this happen in legacy systems myself. The checksums of TCP/IP are weak and will let random errors through to L7 if there are enough of them. It's not even CRC and you must bring your own verification if it's critical for your application that the data is correct. TLS does that and more, protecting not only against random corruption but also active attackers. The checks you get for free are to be seen only as an optimization, letting most but not all errors be discarded quick and easy. Just use TLS.


I saw myself years ago that Verizon injected marketing tracking headers into http traffic. My ISP was the MITM.

https://www.eff.org/deeplinks/2014/11/verizon-x-uidh


It is already possible using the Host header and TLS SNI. But traffic still flows through port 443.


You can't. It's only supposed to be used for a limited list.


Well that's how SPAs work (single page applications)


I see no downside in using sqlite as an application file format.


The only "downside" is that the format is an open spec, which allows anyone to modify the contents without going through the specific application. And it's only a downside if you are using the format as an obfuscation to prevent third-party compatibility/reverse engineering, or to lock in customers.


Yup. You can strip headers from the file though and keep them in your application though, to keep the file from being easily usable. And/or encrypt it.


SQLCipher + a hard-coded or generated key in your app.


I even forget which word means what, "open", "close"


What if it was proxied through mobile network on an unsuspecting user's phone? You risk of blocking a whole city or region.


I admit, my approach was rather nuclear but it worked at the time.

I think an evolution would be to use some sort of exponential backoff, e.g. first time offenders get banned for an hour, second time is 4 hours, third time and you're sent into the abyss!

Still crude but fun to play about with.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: