Hacker News new | past | comments | ask | show | jobs | submit | damir's comments login

I believe tiddlywiki stores PNGs as base64 strings, so image is always there.

Yes, the file can grow large with many images, but it's a single file containing everything... even scripting!


Yes, it embeds all attachments as base64.

TiddlyWiki is great until you want to add a structure to your Wiki. I was using it like mad, then I found out that linking pages took more time then writing notes, and I pulled the trigger and moved to Obsidian.


If you run the node.js server version it can handle images properly, as separate files. That also gives you the practical ability to use many large images and videos.


And little by little we get closer to being Lisp-like...


Would love to know more about the tech stack and the idea behind the site. How it started, and why...


Looking at the source/mod log/etc. it very much looks like it's using lobsters - https://github.com/lobsters/lobsters


Out of curiosity, I checked and got bot hits from 20k+ unique IPs just in the last 10 days... Can easily set up bot IP lookup API...


High frequency state-change propagation don't scale well on APIs. In such setups, one ends up paying for the connection setup/tear-down, and handling clients concurrency gets expensive.

Usually, a per-user access token with a 5 download limit per day is good enough, and can be scripted into peoples blacklist generation cycle.

Keep in mind, some ban-lists take awhile to compile and remove redundant subnets etc. It is important to hit the proxy/tor exit nodes first, than the usual country codes for nuisance traffic from users.

Have a nice day, =3


Actually, I did take some content from wikipedia regarding HEX/RGBA/HSL/etc colors and stuff it all together into one big variable. Then, on each sub-page reload I generate random content via Markov chain function, which outputs semi-readable content that is unique on each reload.

Not sure it helps in SEO though...


Hey, maybe you are right, maybe some stats on which bots from how many IPs have how many hits per hour/day/week etc...

Thank's for the idea!


6 positions, each 0-F value gives 6^16 options, yes?


You have 6 hex characters.

The first has 16 possible values;

The second also has 16 possible values for each of those 16, so now we have 16 times 16.

etc.

So it's a choice from 16, repeated for a total of 6 times.

That's 16 times 16 times ... times 16, which is 16^6.


Welp, you got me scrolling your HN thread to see where the "two-trillion-something" number came from. Between this and your experiment site, you have a knack for drawing attention.


If you think 3 positions, each 0-1, gives 3^2 options, then please show us the 9th three-bit number. Even simpler is the case of 1 position that is 0-1. Does that give 1^2 or 2^1 options?


1 byte (8 bits) is 2^8 (256 unique combinations of bits)

3 bytes (24 bits) is 2^24 (16777216 unique combinations of bits)


Not really.

When numbers repeat, the value is the same. E.g 00 is the same as 00.

So the possible outcomes is 6^16, but unique values per color channel is only 256 values.

So unique colors are 256^3 = 16.7M colors.


256^3 == (16^2)^3 == 16^(3*2) == 16^6


Yes.

16^6 is not 6^16.


Yes, each possible 6^16 outcome is it's own subpage...

/000000 /000001 /000002 /000003 etc...

Or am I missing something?


You are missing something. How many two-digit decimal numbers are there from 00 to 99? Obviously 99+1 = 100: 10 options for the first digit times 10 options for the second digit; 10 in the form 0X, 10 in the form 1X, etc. up to 9X, a total of 10 * 10 = 10^2.

So how many 6-digit hexadecimal numbers from 0x000000 to 0xffffff? 0xffffff+1 = 16777216 = 16^6. 16 options for the first digit, times 16 options for the second digit, times 16 for the 3rd, times 16 for the 4th, times 16 for the 5th, times 16 for the 6th is 16^6. Or go to bytes: 3 bytes, each with 256 possible values is 256^3 = (16^2)^3 = 16^6. Or bits: 2^24 = (2^4)^6 = 16^6.

It's also pretty trivial to just count them. Run this in your browser console:

  count = 0; for(i = 0x000000; i <= 0xffffff; i++) { count++; } console.log(count, 16**6, 0xffffff+1, 6**16)


16^6 == 256^3 == 2^24 == 16,777,216


You have it backward. There are 16^6 URLs, not 6^16.


you mean 16^6


99.9% of traffic are bots...


Yeah, each generated page has link to ~20 "similar" colors subpage to feed the bots :)


You mean adding 2 hex values at the end of the 6-notation to increase number of sub-pages? I love it, will do :)


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

Search: