4 ms·
As always, I propose something like a non-for-profit DNS for storing pairs of codes and urls so all apps can access that site for free. And a simple nomenclatu
by Kilimanjaro 14y ago
As always, I propose something like a non-for-profit DNS for storing pairs of codes and urls so all apps can access that site for free.
And a simple nomenclature like:
@ for places like @eiffeltower to http://wikipedia.com/eiffel_tower
# for products like #mbair565 to http://apple.com/macbookair
* for everything else like *google to http://google.com
I propose google or wikipedia to take the initiative.
* Or to make it simpler, just use square brackets as scanning delimiters [eiffeltower] [mbair565] [google]
- mmcnickle 14y ago[google] does this go to http//google.com or http://wikipedia.com/Google http://wikipedia.com/Google? URLs are as expressive as they need to avoid these namespacing issues. A custom system like yours is going to run up against naming collisions very quickly.