Global Feed Post Login
Replying to Avatar Silberengel

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.

Avatar
MichaelJ 10mo ago

Points 2 and 3 make sense.

Given nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku's comments on search efficiency, I think symlinks as currently defined will work well. Clients will need to discover symlinks by searching for tags, but that's not hard to do.

Reply to this note

Please Login to reply.

Discussion

No replies yet.