your application has been sent to the council
— ubq323
- joined
- a very long time ago
recent posts
out of interest, on what page did you originally encounter johnvertisements?
hi btw. I'm ubq, I am the one who hosts this website, and I'm also partially responsible for GEORGE.
this is implemented in the permissions feature.
this is implemented in the permissions feature
this is due to the slightly odd way "last activity" works throughout apioforum. in some places it's stored as a separate column and updated whenever that thing is updated, and in some places it's not stored and is instead calculated when needed. in general it is slightly a bit of a mess, and needs a bit of tidying anyway. this can then be fixed when that is done.
i agree this would be a lot better if this was fixed though
in its most basic form, needs to keep track of the most recent post each user has read in each thread, and display how many unread posts there are in a given thread.
for usability there could be an option to subscribe or unsubscribe from a given thread, "mark as unread" back to a given point, mute threads or forums etc. maybe there could be a "notifications" page that shows you all unread posts on threads you are subscribed to.
this needs to also support being notified of new threads somehow.
assigned to: no one
fossil branch: n/a
currently "sort threads by" dropdown exists and works, but it looks very ugly (css needed!). should be small and float to the right, probably.
implementation of the rest should not be too hard in itself, the ui is probably the more difficult thing about this.
add "sort threads by" and options to filter threads by tag to the view threads page.
"sort threads by" has options "last activity (newest first)", "last activity (oldest first)", "created (newest first)", "created (oldest first)". forums can also specify have a default sort order for threads in that forum.
not sure how much control the "filter by tag" part needs. a simple "show threads with this one tag and not threads that don't have this tag" (only one tag at a time) would meet most use cases, i think. if not, a more complex "show all threads with any of these tags, don't show threads with any of these tags, don't care about other tags" system (or indeed, arbitrary boolean expressions) could be implemented, though the ui would be trickier and the advantages of this are unclear.
assigned to: no one
fossil branch: thread-filtering
separately to threads, each subforum should have a wiki. a wiki consists of pages, each with a name and content. the page content is rendered in the same way as content of posts in threads, which is potentially more convenient than using a different wiki with a different markup format to store persistent information.
ideally, past revisions of wiki pages will be stored.
access to wiki and ability to edit wiki pages is controlled via permissions system. this means that this feature can't be fully implemented until permissions is done. however, most of it probably can be.
assigned to: no one
fossil branch: n/a
administrators of forums should be able to manage threads (change tags, title, potentially move threads to another forum they control) even if they are not the creator of that thread.
this is fairly minor so it's probably not worth thinking about this until we have permissions done so that we can actually use this feature.
part of: permissions
moderators should be allowed to delete posts that are bad, delete threads that are bad (thread creators should be able to delete threads normally too probably), etc.
once we have permissions there could probably be a "moderation" permission. alternatively we might decide that moderation (deleting actually bad things etc) and management (other administrative stuff) should be separate. we do currently have a global "site admin" boolean on each user which doesn't actually do anything; maybe this could be expanded and turned into this.
part of: permissions
once we have permissions working, there should be a "configure webhooks" page on each subforum, accessible to people with a "p_webhooks" (or something) permission set. for now, probably just make it configurable by manually editing the database.
in order to encourage people who habitually use discord to engage with things on apioforum, it would be useful to have a feature whereby happenings on apioforum (thread creation, posts to threads) can be relayed to a discord channel via a webhook. this should be settable per-forum.
in its most basic form, setting a webhook on a forum will broadcast everything that happens in that forum to that discord channel. if it turns out that more granular control over exactly what is sent where is needed, then this could be added later (so implementation should make adding this feature somewhat easy)
supporting non-discord webhooks could be useful, possibly (for purposes of integrating arbitrary other things with apioforum), but i don't believe there are currently any use cases for that.
assigned to: no one
fossil branch: n/a
the role system allows permissions to be configured per-forum, and will support inheritance of permissions into child forums and things like that. it also allows administrators to exist per-forum.
assigned to: citrons, ubq323
fossil branch: bureaucracy
oh, vaguely important technical note: the display colour of an option is generated based on a combination of the text of that option and the index of that option within the list of options. so if an option is the first in the list and has the text "yes", then it will have the same colour as any other option #1s with the text "yes" (seemingly some sort of olive green), but not necessarily the same colour as another option in a different position with the text "yes", or a different option #1 with text other than "yes"