didn’t want to hijack the jams topic so i thought i could open an topic here and ask for some feedback (!)
That sounds like an awesome plan!
I found myself thinking about the petname thing again and again the last days…
… Basically it wouldn’t be too hard… You just need a file with mapping information from your petname to the unique public name
basic thoughts
-
everyone participating in the ALIAS-System has a public container with e.g. the handy name _____sharedAliases_____ (and optionally a private container _____privateAliases_____)
-
if i want to have the alias ‘jams’ directing to safe://jams.demo i just store this alias in my public container - and whenever i type in jams in the address line of peruse and hit enter this gets resolved to safe://jams.demo
-
if i want to show this safelet to my friend @happybeing i tell him that theres an awesome site i called jams and he needs to check it out! - my public alias is riddim → he just enters jams@riddim into peruse and hits enter → the name now can get resolved through my public alias container to the full safenet address
-
another friend of mine has the name @hunterlester in RL but sadly there was someone else faster with getting a public alias at the safe network … so his public alias is hunterlester1841 - i now could add hunterlester as alias name for him for all apps resolving aliases → i myself still could go with jams@hunterlester → only if he wants to share a globally valid link to his onlineshop (he created through a service and therefore is located at safe://buyAt.awesomeshops/hunterlester) he needs to publish safe://shop@hunterlester1841
privacy and my stored/shared aliases
- If the key for the mapping is the hash of my alias and the public name is encrypted by the petname too i could just publish the mapping without people seeing my pets (if they don’t bruteforce them) … when including my public name into the hash that would make different hashed for same aliases … but what if i have more than 1 public name …? (and would that make any sense at all …? if i really don’t want anyone to see the alias/website i use i could just make it a private alias …)
what do you think about this alias system? makes sense? too complex/many traps for the user?
On first view implementing this doesn’t look any difficult to me. Sadly I didn’t find the time to play with the Safe Network Playground yet and have no Idea how I would write a small library (and where I would publish it) so that others can just drop it into their safelets
do you see more problems here? have additional thoughts on this topic?
Which version of npm and nodejs are the currently used ones …? does one of you have a link to a good resource on publishing a library for nodejs?
(sorry for asking this dull - i do know how to google - and i will do it anyway when i start testing this idea [if no-one else is faster - i wouldn’t mind that too - no clue how long this endeavour will take me ] … just thought if one of you does have a great starting point for me it would make sense to enter there and get a steeper learning curve
)