HN user
Excel uses IEEE 754 double precision which stores up to 17 significant digits but the Excel UI itself only displays up to 15 significant digits.
[0] https://en.wikipedia.org/wiki/Double-precision_floating-poin.... [1] https://www.mrexcel.com/excel-tips/17-or-15-digits-of-precis... [2] https://www.youtube.com/watch?v=WZfjmbEDbfI
Tab separated is a bit better than CSV. But can’t store tabs and still has issues with line endings, encodings etc.
There are three main variations of tab-separated-values files: 1) Those that don't allow tab and line endings. 2) Those that replace tab and newline characters with escaped values (\n for newline, \t for tab, \r for carriage return, \\ for backslash). 3) Those that follow the CSV convention of quoting fields as defined in RFC4180
The third option is by far the best and is what Microsoft Excel uses. Microsoft Excel has a save file type called "Unicode Text (.txt)" which saves the data as a tab-separated file using RFC4180 quoting/escaping with the UTF-16LE character encoding. In older versions of Excel, "Unicode Text (.txt)" was the only way to export any values containing Unicode characters since the "CSV (Comma delimited) (.csv)" export format uses the ANSI encoding(Windows-1252 on Western/US computers) corrupting any characters not contained in the ANSI character set. In late 2016, Microsoft finally added the "CSV UTF-8 (Comma delimited) (.csv)" option for exporting a CSV file containing Unicode characters.
Encoding your email address to hexadecimal may prevent some less sophisticated crawlers from capturing your email address.
mailto: -> mailto:
abc@gmail.com -> abc@gmail.com
Then instead of:
<a href="mailto:abc@gmail.com">abc@gmail.com</a>
Use this:
<a href="mailto:abc@gmail.com"> abc@gmail.com</a>
Or this ("mailto:" also encoded):
<a href="mailto:abc@gmail.com"> abc@gmail.com</a>
Using CloudFlare workers to clean up the URLs is neat but it seems like it would be really easy to reach the limits of the free tier.
https://workers.cloudflare.com/docs/reference/runtime/limits...
You get 100,000 request per month and up to 1,000 requests in a 10 minute timeframe. So if you have a page with 10 images on it and you get 100 people visiting that page within a 10 minute timeframe, you will use up all of your free tier and all new visitors will get a 1015 error.
For paid plans you must pay at least $5 and get 10 million requests included and additional requests are 50 cents per million.
me too
Note that for some reason, Cloudflare charges substantially more for .io domains than other registrars. Cloudflare charges $45 whereas Dynadot charges $26.99 and Porkbun charges $28.97.
https://community.cloudflare.com/t/io-domain-price-not-whole...
I checked and New Zealand actually uses a comma as the separator, not a semi-colon. You can verify this by going to Control Panel -> Region -> Change to: English (New Zealand) -> Additional settings... -> List separator
A semi-colon is generally used as the default list separator when the region/locale uses a comma as the decimal separator for numbers. For example Dutch (Netherlands) uses a comma for the decimal separator (ex. 3,14) whereas in English (US) we use a decimal point (ex 3.14). If comma were used as the default list separator in such a region then all floating point numbers would need to be quoted (ex. "3,14") which would make the size of the CSV file larger and also make the file less human-readable
Liliputing is quite good for tech news: https://liliputing.com/
would love an invite if anyone has one to spare. Going to be launching my startup soon.
it looks like Groove will be releasing a mobile app any day now (expected release early March 2017).
https://help.groovehq.com/knowledge_base/topics/does-groove-...