You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a very straightforward issue but please take a look at the code to see if it is even achievable. in this task you are simply expected to set an additional rule that filters the posts that are displayed under #ulog on ulogs.org.
current behavior
#ulog of ulogs.org currently pulls and displays every post published onto the steem blockchain whether through ulogs.org or through any other condenser, that has chosen #ulog as one of its tags.
expected behavior
being that we want to use ulogs.org also as our curation and moderation interface for #ulog, we want to now make sure that under #ulog (on ulogs.org) only posts that select #ulog as their first tag are pulled and displayed under #ulog on https://ulogs.org. This rule should apply all accross #ulog whether trending, active, hot or new.
Basically, if a post doesn't have #ulog chosen as its first hashtag, it shouldnt be displayed on https://ulogs.org under #ulog
The text was updated successfully, but these errors were encountered:
This is a very straightforward issue but please take a look at the code to see if it is even achievable. in this task you are simply expected to set an additional rule that filters the posts that are displayed under #ulog on ulogs.org.
current behavior
#ulog of ulogs.org currently pulls and displays every post published onto the steem blockchain whether through ulogs.org or through any other condenser, that has chosen #ulog as one of its tags.
expected behavior
being that we want to use ulogs.org also as our curation and moderation interface for #ulog, we want to now make sure that under #ulog (on ulogs.org) only posts that select #ulog as their first tag are pulled and displayed under #ulog on https://ulogs.org. This rule should apply all accross #ulog whether trending, active, hot or new.
The text was updated successfully, but these errors were encountered: