search

dracidoupe / graveyard

Open Source reimplementation of https://www.dracidoupe.cz/
https://nove.dracidoupe.cz/
MIT License
6 stars 4 forks source link

Tavern #210

Open Almad opened 3 years ago

Almad commented 3 years ago
Nathaka commented 3 years ago
  • [ ] Table list
    • [ ] Go directly to tavern table (ID input)
    • [ ] Listing options *1
    • [ ] New tables *2
    • [ ] Forget (?) *3
    • [ ] Ignore (?) *4
    • [ ] [N] (redirects directly to notice board, i think it shows in red when there are changes)
    • [ ] Amount of comments & new comments since last visit
  • [ ] Table details
    • [ ] Display comments and move pages - would be nice to have a button for "show all" instead of putting a high enough number in and clicking next page to bypass it
    • [ ] Related tables
    • [ ] Admin functionalities
    • [ ] Name-description updates
    • [ ] Co-admins/moderators
    • [ ] Access allow/denylist & read-only/write allow list
    • [ ] Switching reputation setting
    • [ ] Give up table *5
    • [ ] Merge tables (leave for later, i don't expect many new tables)
    • [ ] Request section (owner can request the table to be put into a specific section, innkeeper can see the requests but i don't remember where, can approve)
    • [ ] Moderator: mass comment delete (still needed? not vital)
    • [ ] Sending new comments to email (later?) *6
    • [ ] Deleting table
    • [ ] Book / unbook
  • [ ] Ankety (table-specific polls)
  • [ ] Nástěnky (notice-boards)
  • [ ] Statistiky (table/topic statistics)
  • [ ] Sekce putyky (sections)
    • [ ] Privé (private section)
  • [ ] Archiv putyky (archives)
  • [ ] Možnosti hostinských (innkeeper options)
    • [ ] Částečný přístup (partial access) (when entering tables without access or private tables the innkeeper doesn't see the content but can access the admin features and change sections, useful for handling privé and "smart" owners who lock their tables from the innkeeper)
    • [ ] Seber (takeover) - innkeeper can take the ownership of the table (when absolutely neccessary can approve his own access to see the content - not sure if bug or feature)
    • [ ] Moderátor (moderator) - has moderator rights everywhere
    • [ ] Editace sekcí (section management) - can edit, delete and create sections and change their order
    • [ ] Zařazování stolů do sekcí (section approval) - can approve owner requests or just move tables around the sections
    • [ ] Výpis hostinského (innkeeper's list) (can be dropped, only good thing is showing activity which should be done for everyone)

@Almad Full reaction here. Changes are in italic, couldn't find a way to edit it any other way.

1) Listing options currently only offer "all tavern tables"/"all booked"/"all without ignored", either with or without sections or "Sections only" listing (surprisingly effective). It's ¨nice to offer more listing and sorting options, mainly by activity (list of tables sorted by last comment is a minimum, then again maybe it's sufficient). After opening the Tavern the user should be able to quickly find new activity. Using colors from the inkeeper's list is an option, but the colors are bad for design (skins) so I would skip this. But we should also encourage users to see more tables and start new discussions even on old inactive ones, which is why I think making the Tavern smaller is rather important. If that happens shortly after launch, the listing options are actually not that important because then everyone can keep track of everything. Another option (already discussed a lot) is to implement new tavern activity (both new tables and new discussions) into Newsfeed (which is part of a bigger Newsfeed rework and is so important that I would advocate for this to be implemented before or shortly after launching new version) This seems duplicate to tavern filters but I think its good to have some options integrated into tavern as well. 2) New tables show on top. They go into "Potemnělá předsíň" by default, after review the innkeeper either deletes them or moves them to a different section. 3)+4) From Discord - making the table forget your visit is double-edged but potentialy useful for innkeeper/moderators. For users the main reason to use this is to stop tables from showing new comments (otherwise whenever they enter Putyka and see the table it shows new comments from their last visit). Ignore is potentialy useful as well, but maybe it should be merged with booking, so instead of being a separate mechanic we could have "books" and "ignores" and then you can still list only booked tables or all tables without ignores (but also all ignores only so you can actually see what tables you have ignored in the past which is pretty much impossible now). This also moves the [ig.] button next to Book (Oblíbit) (from Tavern interface to Tavern Table). To clarify, my proposition is to make the Forget function work only for new comments (not to erase your visit) and to make Ignore a counterpart to Booking tables (with added benefit of not displaying ignored tables in Newsfeed?). 5) i think skip entirely, wild privatisation was always a bit weird and potentially dangerous (i remember some occasions when even moderators dropped their admin tables, it's a miracle alfik or snorch never got to them - and you and Suk were worried I would do something like that btw) Innkeeper should be able to keep track of unwanted tables (even own them in the meantime) and find new owners, in case there are too many we can have a "dummy" user for safekeeping *6) I would actually say that sending comments somewhere else (be it email or discord) is kinda nice considering how often you visit the web, might bring more people to react?

Nathaka commented 3 years ago

Also fun mechanic - do you know where to create a new table? And do you want to keep it that way? :D

Almad commented 3 years ago

I do know and I am not sure. I think that depends on:

If the answer is yes, than I think that yup, it makes sense to make it not ready for "impulsive table starting", or at least subject to voting.

Almad commented 3 years ago

@Nathaka

1) Makes sense 2) Let me think about that one, I am not sure what is the proper visualization and if it makes sense. I'd maybe skip in lieu of newsfeed. 3/4) yup 5) Agreed, maybe not dummy user but "unmanaged", up for Innkeeper to take care of them and find them new owner ASAP...or maybe tables that will be in the unmanaged state should go into the archive by default? 6) I am thinking that this should be part of a more holistic activity tracking feature. My thinking about it: #232

Nathaka commented 3 years ago
  • Do we prefer people to pick tables out of archive?
  • Do we want owners to commit to maintenance?

This is hard. On one hand, continuity is nice, on the other hand, I think "new" Tavern should have tables with broader topics to prevent both inflation and inactivity. Right now I would say "leave the old tables in the archive to rest" - where there is continuity and activity (14 dní, PJP, Studnice nápadů) we should move the tables to the new tavern, where there is not, there should be history and place for new tables to arise (or maybe we can even do some design choices and create the basic topics by ourselves). Impulsive table starting can be solved in other ways than hiding the button somewhere else, for example only azure levels or higher could do it and if there is a new user he needs to convince someone to do it for him (which would be fine by me). Then again, we might just leave it as another gimmick.

Agreed, maybe not dummy user but "unmanaged", up for Innkeeper to take care of them and find them new owner ASAP...or maybe tables that will be in the unmanaged state should go into the archive by default?

  • archive by default is not a good idea, unmanaged status is fine but dummy user is less programming for you and basically does the same thing as unmanaged status. (And you can see the unmanaged tables in the Unmanaged dummy user stats.) your choice
Almad commented 3 years ago

but dummy user is less programming for you

Please don't make development assumptions :)

Nathaka commented 3 years ago

but dummy user is less programming for you

Please don't make development assumptions :)

my mistake, i based the assumption on the old version where users and ownership are already done and unmanaged status would be a new feature, didn't realize in new version everything is a new feature. :)