Closed 0x0ade closed 7 years ago
You're the best
I will need the dat
in portal.json
for something I have brewing
Please don't, use resolveName :) or portal.archive.url if you're looking for your own. I was thinking about adding an index.html page to the client repo with on boarding instructions, what do you think?
If you've already got a portal instance, just use its .dat
- it's basically a cached result of resolveName
:)
I welcome a index.html page with on boarding instructions... but I'm wondering: Is it possible to modify the DatArchive created by DatArchive.fork(url)
? If so, we could just create a "create portal" button that
This would make the process to create your own portal:
It won't teach the user how to use the edit
command, though.
I wish, that would be such a new feature for 0.78 @pfrazee.
I just checked myself - we already can! Throwing together an ugly (unstyled) "new portal" concept index.html in my repo
I've been summoned.
I welcome a index.html page with on boarding instructions... but I'm wondering: Is it possible to modify the DatArchive created by DatArchive.fork(url)
Yes, you can edit any dat that you create, either by .fork
or .create
. Was that what you were talking about @neauoire ?
If so, we could just create a "create portal" button that
I already made something like this (doesn't modify the svg atm). Got caught up with work and never announced it: dat://af5ef11cdb370a641bf9a95854b74f42bf445e84969c05968f5385f7cde7487d/
I'll work on adding an svg upload today.
Moving the discussion out of this PR so others can see it more easily #117
Personally, I'd just love to see your launchpad integrated into rotonde-client, or at least being referred to from louis' guide :)
Related discussion on Twitter, linking to thread tail: https://twitter.com/lechd/status/929056891409453056
The
dat
field inportal.json
is just causing issues and @neauoire told me aboutDatArchive.resolveName
, which is preferable for every use case in rotonde right now (except for when someone wants to "update" their portal to a new dat).This makes
portal.hashes()
(used in f.e.is_known
, mention / whisper checking) effectively return the result ofresolveName
.dat
inportal.json
is now useless (can't find anything using it anymore), but it's still being kept as old client versions use it.