- This topic has 26 replies, 15 voices, and was last updated 1 year, 4 months ago by
.
-
Posts
-
"🔸 The request will be deleted after 48 hours."
Not sure I follow. Is this to say that all filled requests will be deleted (from the new request page(s)) after 48 hours, or?
...If one isn't around for weeks at a time, and didn't see or join in a request where the filler chooses not to post to blog, how does one know what they're missing or missed?
(Probably misinterpreting the statement.)Logistics questions:
Transferring/translating of current (forum) requests to New Requests section - I see that currently (as of this post) there are 19 assets on the new requests section/page(s). Are these new and/or duplicated requests created by mods only to test the new section? Or are members already able to test and use the new system? (There is no identification of the original requester in the new system request posts, it seems. Intentional? Interesting.)
Who is doing the transferring/translating of archived (forum) requests to the New Requests section? Will they actually all be transferred at some point? Good lord, that's doing god's work for sure.In the previous announcement, the tags and protocols format is clear and inclusive of SKU, Vendor's name, New Request or Old Request; yet none of this information is listed in new request postings. Is this information strictly for categorization by system or mods, or future updates? How will such reference items be searchable by us mere mortals?
In this new system of SINGLE item requests, it would seem that MULTI-REQUEST threads or systems are ended. Is this correct? Other than posting several same-vendor requests in succession, chronologically and quickly for example, is there a way to group several same-vendor assets together in a check-off style anymore? Or are those kinds of multi-request approaches basically just over?
All very interesting and seemingly promising.
"🔸 The request will be deleted after 48 hours."
Not sure I follow. Is this to say that all filled requests will be deleted (from the new request page(s)) after 48 hours, or?
...If one isn't around for weeks at a time, and didn't see or join in a request where the filler chooses not to post to blog, how does one know what they're missing or missed?
▶ No, you got it right. I think the request delete is Ok, because it wouldn't contain the Filler's name anyway, but a basic archive list would be handy 🙂Transferring/translating of current (forum) requests to New Requests section - I see that currently (as of this post) there are 19 assets on the new requests section/page(s). Are these new and/or duplicated requests created by mods only to test the new section? Or are members already able to test and use the new system? (There is no identification of the original requester in the new system request posts, it seems. Intentional? Interesting.)
▶ Everyone can use it from today. The request starter will be in first place on the offerer list 🙂 As a "promotion" I've added the new releases to the new system and to the forum too (with a ⚠ FYI This request is also available in the New Request Filling & Posting System: (XYZ link) to crosslink them)Who is doing the transferring/translating of archived (forum) requests to the New Requests section? Will they actually all be transferred at some point? Good lord, that's doing god's work for sure.
▶ Sadly it's fully manual and up to everyone, but in the next month I will check the still open requests and slowly add them 😉In the previous announcement, the tags and protocols format is clear and inclusive of SKU, Vendor's name, New Request or Old Request; yet none of this information is listed in new request postings. Is this information strictly for categorization by system or mods, or future updates? How will such reference items be searchable by us mere mortals?
▶ New Request or Old Request tag is already there (if someone forget to add it, I will add it), it would be searchable but currently, the Request search bar is searching the blog and not the Requests, so that's the problem 🙂In this new system of SINGLE item requests, it would seem that MULTI-REQUEST threads or systems are ended. Is this correct? Other than posting several same-vendor requests in succession, chronologically and quickly for example, is there a way to group several same-vendor assets together in a check-off style anymore? Or are those kinds of multi-request approaches basically just over?
▶ Yes, every request is SINGLE item request, and you need to add every addon etc as separate request like these:
(https://zonegfx.com/requests/d-force-costume-dress-for-g8f-and-g8-1f/)
(https://zonegfx.com/requests/diverse-for-d-force-costume-dress/)
Currently, the best solution is to add the Vendor's name to the request's tag line and later with a search (when it's working :D) it would give back an easy list in chronological order 🙂I love the new system. One of the reasons I don't fill requests as much is because of the hassle of notifying each individual requester, keeping track of how much each one offered, not to mention in practice I never really track who really transferred and who didn't (and I know for a fact some users never do, sadly). Oh and add to that having to create a new scheduled blog post after all that. Now everything is automated.
Would it be possible to get the images in the request page smaller, that way you can have more requests to a page. I know there's a search feature, but sometimes I don't know I want something until I check it out.
I think we should really bump up the time for the receivers from 24 hours. Receivers has 24 hours to review a link (I know some people don't visit this site daily). If there is anything wrong with the link then we need to also reach out to admins for a manual dispute. Thats probably less than x amount of time for said admin to respond to the dispute at the time the receiver sends the email.
@hioushi I love the new system. One of the reasons I don't fill requests as much is because of the hassle of notifying each individual requester, keeping track of how much each one offered, not to mention in practice I never really track who really transferred and who didn't (and I know for a fact some users never do, sadly). Oh and add to that having to create a new scheduled blog post after all that. Now everything is automated.
▶ 😎❤ and more features to come 😉
@yanoma Would it be possible to get the images in the request page smaller, that way you can have more requests to a page. I know there's a search feature, but sometimes I don't know I want something until I check it out.
▶ I 100% agree with this, added to the wishlist 🙂
@sleepysheep I think we should really bump up the time for the receivers from 24 hours. Receivers has 24 hours to review a link (I know some people don't visit this site daily). If there is anything wrong with the link then we need to also reach out to admins for a manual dispute. Thats probably less than x amount of time for said admin to respond to the dispute at the time the receiver sends the email.
▶ I'm not sure if it's necessary, because ~95% of the requests have multiple offers, and only one participant needs to contact the Mods that there is something wrong with that Fill 🙂 and obviously, if the problem gets to the Mods after the 24h mark, the point transfer would be reversed anyway, so the "fake" filler can't escape 😀I can't seem to find this information under the "What If" scenarios, so I'll ask here.
Do the old request rules still apply for this new request system? I'm asking mainly over the two requests per 24 hours thing. I have a decent amount of old requests I'd like to move over to the new request system, but don't want to go breaking the rules.
Also, if we're the creators of the original request in the old request thread, should we ask for that thread to be closed?
@yanoma Do the old request rules still apply for this new request system? I'm asking mainly over the two requests per 24 hours thing. I have a decent amount of old requests I'd like to move over to the new request system, but don't want to go breaking the rules.
▶ This rule was never really enforced 😉 If you are transferring old requests into the new system, I would say 10x per day can work 🙂 Just please wait a few days, till we collect the feedbacks and the feature wishes - The one month test period will only start after that 😉Also, if we're the creators of the original request in the old request thread, should we ask for that thread to be closed?
▶ It's up to you, but IMO it's not necessary 🙂 I would only ask you to add the ⚠ Warning at the top of your thread, like this: (https://zonegfx.com/forums/topic/void-lurker/)I am carefully reading the new rules, I hope I don't make a mistake or do something wrong that will punish me =S, thank you very much for the work to improve zonegfx =)
I'm all for this idea, but personally, I've got some worries that others have already brought up. One is about how easy it'll be to keep track of what's been requested and what hasn't. And the other thing, like others have said, is having a system that lets latecomers see what they missed and maybe make a bid on something, which would link to my first concern of keeping '(FILLED)' posts for a little time, like in the forum, until they get eventually posted.
@lulukawaii One is about how easy it'll be to keep track of what's been requested and what hasn't. ▶ A summary list is in the works, which will show all of your offers on the requests, it will be much more manageable 🙂 To see if something was requested or not, you need to search the requests (just like the forum) - so I don't think that this would be very different from the current method. Obviously, till both section is working there will be "problems", but I try to crosslink every request in the new system and in the forum. Also, the size of the request grid will be probably a bit smaller to see more items (this was in the top3 wishes).
And the other thing, like others have said, is having a system that lets latecomers see what they missed and maybe make a bid on something, which would link to my first concern of keeping '(FILLED)' posts for a little time, like in the forum, until they get eventually posted. ▶ At some point the system needs to close the request, which is currently at the time when the Fill happens. We don't store the links etc so it's not really possible to hop in a request after the auto PM was sent out. Currently, we are thinking about creating a simple "FILLED" list with the Item's name / URL / FILL time, so everyone can see what happened in recent days 🙂
- The topic ‘⚠ (CLOSED) Request Filling & Posting System // Closure of the Request Forum’ is closed to new replies.
