Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Silyus
1
The Illustrious Idea / Re: Suggestions
« on November 14th, 2017, 04:08 AM »
Quote from Akylen on November 14th, 2017, 01:13 AM
but the offer still needs to be directed towards the user.
Yeah, that's the point.
As for now, I can only offer game A for game B to a specific user.
I'd like to set an open offer about my game A for game B to anyone that might be interested.
At the same time, I'd like to see for my game A what offers are available, namely what games can I get trading my game A.
As for now, I can only see, for my game A, which people are interested in it, and their tradable list, and I can only make an educated guess on what they might want to trade for my game A.
2
The Illustrious Idea / Re: Suggestions
« on November 13th, 2017, 06:40 PM »
Dunno if this thread is still active, however I think that a good way to lure more users is to offer a truly unique feature.

An idea should be the open trade offer.
When I propose a trade, I don't really care who is the person that close that deal (save for a minimal rep requirement).
A nice feature should be to make an open offer, where I state the game I offer and a list of games I'd like to trade it for, and publish it in a sort of open market.
This should be coupled with the possibility to select one of my game and see what I can get out of it (in the open market), with the possibility to create a quick offer if something catches my eye.

Server-side, all the open offers and the searches should be matched automatically (using hash tables pretty much as the normal matching is done).
I think that most of the procedures required are, in face, already implemented in the project.

Correct me if i'm wrong, but I have never seen such feature anywhere, and it could really came handy, especially because I can discover games - potentially out of my wishlist - that are 1-click away to be traded.
3
The Noble Talk / Re: What's up at Lestrade's?
« on April 3rd, 2017, 09:19 PM »
Quote from Lestrade 尚 on April 3rd, 2017, 04:35 PM
Quote from Silyus on April 3rd, 2017, 01:48 PM
I'm sorry for the slight OT, but is there any ETA for the export feature for wishlist and tradables?
Export feature? I have no plans for this in the near future. I'm sure @theemu- will write a user script if he feels like it, though ;)
Yes, it's basically just a parser and it should be very useful (I used that a lot with barter)
Quote from Lestrade 尚 on April 3rd, 2017, 04:35 PM
Quote from Silyus on April 3rd, 2017, 01:48 PM
Also I can't find a way to point to my tradables list with an unique url (useful to directly show my list to random internet guys and also indirectly promote letstrade).
Should I add a 'permalink'..? Just go to your profile, and in the lower left, you'll see a Wishlist link, just use that, it's your permalink. (Same for all list types.)
Was unable to find it, however I noticed that my profile is accessible via https://lestrades.com/@silyus so I figured out my links by guessing:
https://lestrades.com/@silyus/wishlist
https://lestrades.com/@silyus/tradables

Seems to work, but please add a permalink notice on every list so it's more visible.
4
The Noble Talk / Re: What's up at Lestrade's?
« on April 3rd, 2017, 01:48 PM »
I'm sorry for the slight OT, but is there any ETA for the export feature for wishlist and tradables?
Also I can't find a way to point to my tradables list with an unique url (useful to directly show my list to random internet guys and also indirectly promote letstrade).

Apologies if either or both these features are already present and I'm just too dumb to see them.
5
The Illustrious Idea / Re: Barter features to consider adding?
« on March 26th, 2017, 02:13 PM »
I'm not exactly the biggest fan of barter out there, many ideas were very counterintuitive, and I mostly used it for the trusted community.

However there's a thing that I really loved about it and I can't find here.
When I look for matches I'd love to see if I've already sent an offer (and which offer) to an user under the match box.
This prevent me to spam the exact (already declined) offer to the same guy over and over again.
For now I'm taking 2 tabs open, one with the offers already sent and the other with the matches, checking every user in a (mostly) O(n^2) fashion (I know, I got a terrible memory).
6
The Noble Talk / Re: What's up at Lestrade's?
« on March 23rd, 2017, 05:16 PM »
Quote from Nao 尚 on March 23rd, 2017, 02:56 PM
I'm only trying to think of the far future. If we end up having millions of previous trade offers, with an average of 5-6 games per offer that'd mean quite a lot of rows in that table... Meaning potentially slower trade feature, too (although at this point I can either remove trades from over a year prior or something).
That's the reason I was suggesting to prune every offer older than a week. In this way you'll have only to deal with the number of trades done in a week, which will hardly reach 1M.
I was also suggesting to keep the trade history in a separate table so you don't have to load it every time an user want to look at their tradables (most of the time), but only when he wants to check his history (fairly rarely).
To be crystal clear, I'm just telling this only to defend the solution I proposed, not to push you in a specific direction.
Frankly I really appreciate the work you've done so far, also only you know how things are implemented, so feel free to implement the solution you think it's best (even considering how much more effort you want to put in this project).
7
The Noble Talk / Re: What's up at Lestrade's?
« on March 23rd, 2017, 01:26 PM »
IMHO option 2, but keep everything in a separate table, which stores only transactions already made, and purge it (on daily basis) of the transitions older than a week or so.
The tags should be useful to resolve troubles from the people involved in the trade which, in case, should arise early after the trade is done (hence the pruning after a week).
I can assume that the trade history is accessed only rarely (compared to other actions made by the user) so an overhead introduced by this solution shouldn't be a problem.