f.weber/homebrewery
0
0
Fork 0
mirror of https://github.com/naturalcrit/homebrewery.git synced 2026-03-22 08:58:11 +00:00
Code Wiki Activity

tags discussion redundant now

ericscheid
2024-02-05 12:21:50 +11:00
parent 1da4aefb36
commit c08c6ced8c
1 changed files with 2 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
Published---public---hidden-brews.md

@@ -19,24 +19,8 @@ https://github.com/naturalcrit/homebrewery/issues/697#issuecomment-972366463
>
> Creators could authorize their HB account with Patreon, and when publishing brews could mark them as locked behind certain patron tiers they have.
>
> Patrons would also need to authorize with Patreon, but after doing so could visit the creator's page and see all the content available to them based on their subscription tier with that creator.
> Patrons would also need to authorize with Patreon, but after doing so **could visit the creator's page and see all the content available to them based on their subscription tier with that creator**.
>
> I've worked with the Patreon API in the past and it's currently undergoing a pretty big shift, just noting this for the future if the idea seems nice.
Alternatively, users could maintain a folder for each tier (possibly even a smart-folder to auto-select based on tags), and set a password on each such folder. Patrons with the password can view and access the contents. The creator can change the password monthly to restrict access from unsubbed patrons, although that sounds like a fair bit of fiddly work (but doesn't require any special coding/development).
## tags
When we do get around to tags, and categories of tags .. one such category I'm imagining would be for licensing ..
- `license:OGL`
- `license:Public Domain`
- `license:CC BY-NC 4.0`
- `license:MIT`
- `license:mixed`
- `license:custom`
etc
These various tag categories would be finite and pre-coordinated in the list of categories, and in the tag values within each category. Outside of those categories would be free form custom tags, which are limited only by what characters can be used to form them (probably `[a-zA-Z0-9_-./& ]` (i.e. reserving use of special chars for possible future use, of which `:` is one character obviously already in use).
Alternatively, users could maintain a folder for each tier (possibly even a smart-folder to auto-select based on tags), and set a password on each such folder. Patrons with the password can view and access the contents. The creator can change the password monthly to restrict access from unsubbed patrons, although that sounds like a fair bit of fiddly work (but doesn't require any special coding/development).