Rixfeed is built from a large combination of systems.
I've discovered a very unique, yet useful consequence of the interactions of these different systems.
I can leverage it solve a problem that has plagued me from the start.
I've found it very difficult to design a tagging and categorization system that I like.
I had been heading some posts like so:
And "tagging" them like so:
There's a few obvious problems with this.
Sometimes I want to tag something, but not have the tag included as actual text on the post.
Sometimes I want to write an article, but I don't want to title it.
If it's ever the case that I want neither a title nor a visible tag, then I have to surreptisiously inlcude the tag within the context of the article in order to make it work.
Instead, we take advantage of a characteristic of markdown.
The syntax above is designed to be used for a markdown citation footer.
The citation footer is hidden from the final rendered view because it is only a user convenience for the editor of the plain text markdown.
This means I can leverage this to create hidden tags for your content, should you ever want to not include the tag in your content.
This also means I don't have to have a separate or extra additional tag gui.
We'll see.
We'll have to see how this feels on mobile and the non-vim editor.
I could always make a button to drop in tags that does the correct syntax under the hood.
That's it for now.
Note that the tag for this article is "rixfeed-dev-log" and the post is tagged with that syntax, you just can't see it when you render the content as markdown.
If you're looking at this in plaintext, the tag is at the top of the file, if you're curious.
You now find items with this tag at: rixfeed-dev-log
Note you can put any string with no spaces where I put the 1 and it will be hidden. You could use this to denote page numbers or priority, or subtags, perhaps.
// This should be a separate article at this point.
Hell, you can even do this:
Which may be very interesting to leverage. You could use this to set hidden "properties" that are text searchable.
Then we could allow users to write filters like this:
Which would then be converted to an algolia query.
I haven't sounded out all the potential incongruincies or knowledge gaps in this design yet.
Holy shit, what if you could use this to control feeds and groups, too?
Like you can namespace tags??
Only users with permission to use [@patrick--*] or [@patrick--memes]
may use them. Perhaps, anyone can use [@patrick].
This means users can mention @patrick, but not use tags
in their namespace unless some permission grants
it.
As a result, I could create this tag:
Which anyone can use, and then @patrick can monitor for quality submissions.