-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New page/feed/feature: tradeables tagged with gem price #2
Comments
bartervg/barter.vg#35 |
Somewhat of a duplicate of 35, in that it calls for a global value-sortable price list as well. Barter is not the DIG marketplace. Does it want to be? |
It doesn't make it a marketplace, it's just arranging info that already exists into logical tables. |
semantics There is a potential marketplace feature. Rather than have it sort of partially implemented on barter.vg, someone should attempt to fully do it on a dedicated site for it. |
It's up at https://notamarketplace.com/ Don't like it? It's FOSS and the site builds from the Github repo https://github.com/bartervg/notamarketplace |
Haha, you absolute mad lad. |
Out of Barter Scope. Divert related issues to dedicated project https://github.com/bartervg/notamarketplace |
What problem does this feature address?
Tradeables tagged with a gem value are neat, because it makes for the quickest trades ever. There's a set price, you offer it, and you get it. Hence, a big feed or a big table where all the games on the site that currently have a gem price on them, could be useful. Especially if it is possible to sort the table by price, so that people can snag up all those 150 gem games when they are new and just want a lot of games.
Describe a solution
So yeah, basically: I just want a list/table/feed with all tradeables tagged with the Gems trading tag, and sort it by value.
It could also be a Discord feed --> Every time a new tradable is tagged with a gem price, throw it into the Discord feed.
Examples of similar features
The text was updated successfully, but these errors were encountered: