indexer: notabug.io
all comments

[]Tree_WL_Exp -0 points

thought it'd be better to have sheet of commands than having to dig through examples

if there's anything i missed or got wrong do tell me

[]go1dfish -0 points

Looks right to me, one interesting thing about unique by content is that it should always include the first occurrence in any given sort. So in top it would include the highest voted but not those that are lower voted.

I stickied this in the spaces space.

[]Tree_WL_Exp -0 points

ah, so that's why in chat it would show the newest one

[]FrontPageGuardian -1 points

You may want to see source code for declarative listings: https://github.com/notabugio/notabug/blob/master/server/listings/declarative.js

[]go1dfish -0 points

Yeah this is where (most of) the logic for dealing with listing source lives.

I'm probably going to build an intermediate step that outputs a formatted understanding of the listing source to be shared between this and the UI code.

[] -0 points

oh yeah, forgot about ups, downs and score

[]Tree_WL_Exp -0 points

added now

[]go1dfish -1 points

Ok now chat topic is a separate setting from submit topic, you can do one, the other or both:

submit to [topic name]
chat in [topic name]

[]Tree_WL_Exp -0 points

okay, updated

[] -1 points

author+curator is all sorts of bad, so use one or the other

[]Tree_Perception -0 points

now you can make 3 spaces for that combination:

Space A:

author publickeyX

Space B:

curator publickeyY

Space C:

listing /user/ownerpublickey/spaces/spaceA

listing /user/ownerpublickey/spaces/spaceB

And you direct users to Space C

π