Home Page › Forums › General Chat › 🗯 FEEDBACK & WISHLIST // Request Filling & Posting System
- This topic has 142 replies, 35 voices, and was last updated 8 months, 2 weeks ago by Reza Ardekani.
-
AuthorPosts
-
October 8, 2023 at 1:53 pm #2034463
@lucafeelgood It will be okay from now on 🙂
October 8, 2023 at 7:09 pm #2034600@warrant63 I left a message on this post saying that I will fill it out later, what can I do if someone beats me to it and fills it out first as has happened to me before?
October 8, 2023 at 8:11 pm #2034611AnonymousInactiveRank:Please add a sorting function for requests, a lot of the time I just want to see what new requests are coming in.
October 8, 2023 at 8:14 pm #2034616@bloodhunter666 Currently not much 🙁 We have already made the comments as visible as we can.
October 8, 2023 at 8:14 pm #2034617@surplussstg We are on it 🙂
October 9, 2023 at 11:19 am #2034766I think the worst thing is now I'm requesting stuff I already have from the old request system - lol 🙂
October 9, 2023 at 11:20 am #2034767@itsmenotyou ¯\_(ツ)_/¯
October 9, 2023 at 5:32 pm #2034832AnonymousInactiveRank:I have a suggestion about requests being filled later.
The filler will have the option to continue to provide the file within 48 hours (they can set a point).
Because sometimes I'm late with a request and I don't want to wait days or even a month to get the file.
October 11, 2023 at 9:16 am #2035274I just wanted to say that after using the new Request system at the front of the site, I can easily say it's amazing. Love the work you guys have done. Great job. Makes requesting and filling 100 times easier.
October 11, 2023 at 11:56 am #2035310@surplussstg Like I said before ▶ we are still discussing the "Request close" problem, but the community has conflicting wishes + we have our own limits.
A lot of folks requested the selective option (to exclude a few problematic members during a fill), but at the same time a lot of folks requested to join the request after it was Filled to quickly get a link. First, we will finish our current update milestones, the selective filling and the logbook (to see every offer you made on a sum page) then we will see what we can do 🙂October 11, 2023 at 11:56 am #2035311October 12, 2023 at 5:46 am #2035524I like the new request system, it's much easier to see what has been requested and jump on that. Unfortunately it doesn't fix the post-request black hole. Seems like things don't make it to the main blog for some reason, and people are just left wondering what to do next. It would be good if you could just pay to unlock the link like every other post, with the filled requests.
It is because the folks who are filling them do not want to publicly release them, thus they never get to the main blog. There are many different reasons for this, each different per filler. Some only share with others who also share, and some just want to do private shares, some want to remain anonymous, and probably many other reasons. This results in them never getting to the blog. The site does encourage people to do blog posts, but it is in no way required.
Paying to unlock the link would also not work, because a request fulfillment is not the same as a blog post. When posting to the blog users tend to be putting the file somewhere where it can stay long term. When filling requests it can be a very different situation, with people putting the files into their personal storage for a short enough period of time to allow the people who paid for it to download it, then they remove the file. So it will no longer be there for others to pay to unlock. On top of that it would allow certain people who others do not want to give content to to access it, if they end up implementing a system where you can blacklist certain people.
Right now if a request has been filled and removed from the list, and it is not on the blog, you can just request it again without issue. This allows the original filler to fill it again if they wish once it gets more points onto it.
October 13, 2023 at 1:53 am #2035772It is because the folks who are filling them do not want to publicly release them, thus they never get to the main blog. There are many different reasons for this, each different per filler. Some only share with others who also share, and some just want to do private shares, some want to remain anonymous, and probably many other reasons. This results in them never getting to the blog. The site does encourage people to do blog posts, but it is in no way required.
That doesn't make sense though, anyone and everyone who puts points towards a request gets the request when it's filled. Why not just have it available for anyone afterwards the same way? No need to put anyone's name to it, should be entirely anonymous really.
October 13, 2023 at 11:29 pm #2035925@moonhead
For now, but they are actively looking at a way to be able to prevent certain people from receiving requests. As of right now also, it is not in any way anonymous. You receive a system message generated by the system sent by the person who filled the request. You are correct that everyone who puts points towards a request gets it when it is filled, but the person filling the request now also can see who has requested it and can decide to fill it or not at all based on the people in the list. There are many people who do not want to fill requests for everyone, and the site in general tends to honor the wishes of the people who are filling requests.On top of that one of the main reasons I said also stands. You cant "just have it available for anyone afterwards" because when not posting to the blog people fill requests and then remove the files a large portion of the time after a limited amount of time has passed, so the files would not even be there anymore for other people to purchase, which would open a whole new can of worms to deal with. If the site hosted the files the situation would of course be different, but they do not. Making it an entirely new "Dead Filled Requests" section the mods would have to deal with. The current system is currently setup already for long term supplying of content for those who want to offer it, and it is the check box that says "Schedule blog post" which is checked by default when filling a request. For others they can just make the request again, and it can be filled.
The mods are already having to deal with a lot of issues right now with people filling requests with files being posted from the wrong vendors, or certain people posting fake or broken files, or people posting the link and then removing the file almost instantly. When that happens they have to figure out who did and did not actually get it, they have to reset the filled status on the post, and so on. Adding keeping track of making sure links are still working for future purchases of every single request on top of that is quite a huge ask, especially when it will go directly against the wishes of "some" of the request fillers.
Just my opinion of course, and maybe in the long run it will be implemented, but I see a lot of negatives even though there are of course some positives as well.
October 13, 2023 at 11:34 pm #2035927I have sent this in a message but figured I would post it here as well since this is the section for feedback.
When filling a request there should be some sort of message shown in the interface with some basic information that would hopefully cut down on some of the filling mistakes.
A message that indicates that points will not be paid for 24 hours giving people time to confirm the link is valid, and a notice to check to make sure that the file they are filling matches the vendor that is being requested as multiple different vendors make the same character.
Perhaps some sort of minimum time the link should be left up as well that is also clarified for people putting requests. Such as if you fill a request you need to leave it up for at least 2 days or a week or something so people have time to obtain it.
Would not fix everything, but hopefully it could cut down on at least a few of the people that are filling requests with the wrong models.
-
AuthorPosts
- You must be logged in to reply to this topic.