Nostr View

Laeserin @Laeserin - 5d

NEP dropping soon. nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqyw8wumn8ghj7argv43kjarpv3jkctnwdaehgu339e3k7mf0qydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpz3mhxue69uhkzmr8duh82arcduhx7mn99uqzpnl53esemxvsvja4szvxscla6xn7zwxduga2347v7nm4ugfstv7qq40gzm

2
1
3

Laeserin @Laeserin - 5d

💪

0
0
3

Eric FJ @EricFJ - 5d

Nostr Extension Proposals are the way! nostr:nevent1qvzqqqqqqypzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqqsyefys7jlx75h6a78uspae53aw9vc9vk9pp7z36t0wxqx84jel00clzxy5s

0
1
3

Silberengel @Silberengel - 5d

Here it is. https://wikistr.com/nkbip-04*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319

3
0
3

Silberengel @Silberengel - 5d

Here is the njump version, if your wiki doesn't do Asciidoc. https://njump.me/naddr1qvzqqqrcvgpzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqpphxkcnfwqknqdqj7ujh7

0
0
3

Silberengel @Silberengel - 5d

Grateful, for any constructive feedback, including suggestions on a different method for performing something similar.

0
0
3

Silberengel @Silberengel - 5d

The background story is that I was supposed to write a story for an #Alexandria grid-view of the 30040 indexes and immediately saw a fileserver explorer in my head.

0
0
3

Silberengel @Silberengel - 5d

I like data structures and version control.

0
0
3

Silberengel @Silberengel - 5d

Yes, @Beave is on us to go ahead and expand it with public and private/encrypted options, but I want to check the basic scaffolding, first. It's an interesting concept because you can, of course, share these virtual drives with other npubs, copy or fork drives, etc. And because you can replace everything in the scaffold, you can move events around, add-or-remove events, etc.

1
0
3

Silberengel @Silberengel - 5d

Should be nostr:npub1q6ya7kz84rfnw6yjmg5kyttuplwpauv43a9ug3cajztx4g0v48eqhtt3sh , sorry. Typo.

0
0
3

Laeserin @Laeserin - 4d

Versions have an eventID. We can compare that and fallback on the `a` tag, otherwise, and display an info.

0
0
3

Laeserin @Laeserin - 4d

Yeah, the possibility of filepaths. Like Drive/30040/30040/30041 ?

0
0
3

Laeserin @Laeserin - 4d

Okay, update symlinks to add the context-level and allow for targeting non-30040 events. nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn nostr:npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4

0
0
3

Silberengel @Silberengel - 4d

1) If the drive contains a reference to the symlink, rather than the other way around, we should maybe just skip the symlink. Otherwise, there's redundancy and you would have to constantly change the drive, anytime a symlink is changed. The size of the drive is then limited by length of drive event, as well. You would have a max number of syms. 2) There doesn't seem to be a purpose to a predefined order, so I wanted to make that explicit. But maybe we should make it ordered, to match. Devs can always choose to ignore the order. Changed it. 3. 30043 is the drive and the root. I didn't want to overload 30040s with root attributes and functions.

0
0
3

Silberengel @Silberengel - 4d

nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku

1
0
3

Silberengel @Silberengel - 4d

Yes, permissions are missing. I don't understand the second point.

0
0
3

mleku @mleku - 4d

tag lookups are as fast as all the others in a filter except the search field good quality key/value stores maintain sort order in the blocks of the data once it has done a compaction pass, so it really is just finding the start point and simple iteration i haven't thought about the implications of the tree structure of these 30040/1 events though, you should maybe read up a little on filesystem architecture theory to help evaluate what ways you can do things... filesystems are not quite the same as key/value stores, similar, but a filesystem can be highly branched where a key value store is like a (mostly) sorted index

0
1
3

Silberengel @Silberengel - 4d

Yes. Any event with 3xxxxx is replaceable.

0
0
3

Silberengel @Silberengel - 4d

What is being versioned here? The entire tree structure?

0
0
3

Silberengel @Silberengel - 4d

Couldn't metadata be in the drive event, analog to 30040s?

0
0
3

Silberengel @Silberengel - 4d

Can't relays choose to version them (or not)? Histories is outside of the scope of this NEP.

0
0
3
Showing page 1 of 1 pages