** All Wayfinders ** Don't use Upload Later UFN
DracFury-PGO
Posts: 146 ✭✭✭
I've posted in the report bug section about this and yes, it has been put under investigation. In the mean time, me and a dozen others have now got bjorked nominations. The main photo is the supporting photo and vice versa. I was gutted when I batch uploaded 5 of my latest nominations to then realise this. Since then I have requested for then to atleast be frozen 'in queue' until the problem is fixed OR ofc have the photos swapped back to their correct places. Me and several others have been trying to get attention of any admins regarding this fix or freeze, with no luck. So I've come to this thread for better luck.
You would think the core of all this , with finding POI etc would be top of the agenda. Who knows how many people have lost out on perfectly good nominations over this. :(
I'd like to see some due diligence and admins come to our rescue, not to have people lose out on this cycle.
Thanks
Comments
Worth posting on the Reddit wayfarer and TSR to let potential players know
I believe the feature is only on Pokémon GO currently. Hopefully it’s fixed before it goes on to Ingress.
In the meantime, level up to 10 on Ingress if you haven’t already.
level up to 10 on Ingress if you haven’t already
No. I refuse to accept that Niantic withholds critically important functionality from some of its games. I will not be bullied into downloading and playing a game I am not interested in just to be treated as an equal.
You seriously think the uploading later ability is a "criticaly important functionality" ?
I wasn't only talking about the upload later functionality. I was responding to the whole idea of "play Ingress if you want to be able to nominate properly".
But there is (or at least, historically has been) critically important functionality locked behind Ingress: the map of all Wayspots, many of which are completely hidden from PoGo players, but still affect our nominations.
Intel is an Ingress-based utility that exists in the game for gameplay reasons, including field planning. It's been usurped as a public utility by submitters in Wayfarer, true, but its main function was never Wayfarer-based. I only wish it required a higher agent level to use: maybe then Niantic would have been compelled to release a Wayfarer map earlier.
Its original function isn't Wayfarer-based, that's true. However, one of its main current functions very much is.
No, it's not - especially with the move to Lightship. Intel is VITAL for Ingress gameplay and its value can only be truly assessed by players of that game.
Edit - just to keep things on-topic, thanks for the heads-up: I've passed it along to my fellow local Pokemon Go players just in case any of them were thinking of trying out the feature.
I'm not questioning its importance to Ingress gameplay. I can appreciate it without playing Ingress myself, thank you.
All I'm saying is that it has gained another main function as a map that tells you whether your nomination candidate already exists in the system.
Looks like I've just reviewing an "Upload Later" nomination, then.
So what should I do if I encounter such nominations?
Reject them for photo quality. Even if it's not the nominator's fault, it's just not acceptable this way.
Reject, I guess... I see no other possible action. It cannot be approved as it is.
Niantic should fix and reset the reviews of the affected nominations, but I kind of doubt they will do so.
@NianticTintino @NianticDanbocat any thoughts on what we should be doing with these nominations? I don't want to waste my own or other reviewer's time, or waste the submitter's nomination.
This situation kinda sucks.
This explains the nomination I just reviewed, where the supporting photo was so good and the main one was so bad.
As for Ingress, the answer is no. Not because of critical infrastructure access or whatever the other reason given was, but because when I tried it I didn’t have fun.
If those broken nominations are already in review, it seems that if you want to be fair to fellow wayfinders you should take a break and stop reviewing until Niantic fixes the problem.
Otherwise you're rejecting nominations due to a Niantic's bug.
@NianticTintino
if only there were a member of The Team who could suggest a special rejection comment for these, or something -anything- that might help us help you unsnarl this mess.
The problem wouldn’t even exist if there was any semblance of testing before new stuff went Live, but even with the toothpaste already out of the tube, mightn’t there be something you can tell us that will help with damage control?
It’s the weekend. I wouldn’t expect a Niantic response until late Monday.
Problem was reported by end users on the 23rd.
It could have been found and fixed in-house during internal code-review, alpha testing, or beta.
Noantics doesn’t appear to have any of that, but they still had/have a chance to reduce or minimize the damage.
They often have somebody covering this site over the weekend, so I took a sh0t in the dark.
I'm inclined to approve otherwise good nominations made under this bug, now that we know it's a thing. Very few people are going to know about it, and I was just about to fall victim to this myself, with an upgrade wasted. Like anything else, the photos can be updated later, but I'm not going to **** someone in the foot just because Niantic can't get the job right.
I think this is going to be a "do what you feel is right" issue. Players certainly don't deserve to be penalized for doing nothing wrong.
Thanks for all your comments. I've had to essentially explain Niantics 'leg in the air' in my supporting info to reviewers... About the situation. I highly doubt now from the lack of response by ANY admins that I will get my nominations repaired OR reimbursed....
I would agree with others and say reject for low quality photo and they can resubmit when it’s fixed.
Great idea, if it's still In Queue: edit the supporting info, to say Niantic currently has a bug that swaps the pictures. With any luck, the bug is only how it appears in Wayfarer - and the wayspot will be created with the correct picture. Or, even if it's created with the wrong picture - when Niantic fixes the bug, they'll probably fix the waypoints too.
If all else fails, you can download the intended primary picture from your Nominations page, and upload that to the wayspot.
I would not vote against these because of the picture. There are so many possibilities for it to be fixed.
**** Please note - Due to a BUG, my photos have been swapped over while using "Upload Later" feature. This is being looked into, so please take that into consideration as the photos ARE being swapped back if they havent already by reading this. Thank you. ****
Is what ive put at the start of my supporting information. It seems stupid to reject a nomination just because of some coding balls up. All my nominations are sound apart from that. I would still like some sort of update or feedback from the admins. Even just keep stuff in queue until its fixed/photos swapped back.
Unfortunately I would still reject for low quality photo, that's not a slate against you personally, just my understanding is that if we all reviewed with the mindset that "this title/description/photo can be changed later", then there's no reason to have those as rejection reasons, since we could just accept literally anything and change it later, making rejection reasons completely redundant.
“We can all review with the understanding that this is a bug and will be corrected by staff if necessary.”
This is not at all equivalent to the sentiment that we should just allow any photo/title/description since somebody can always fix it later. In this latter case, a Wayfarer was lax or in error.
We know the explanation this time: it’s a bug. We know that if the bug persists through publishing, The Team or their corporate overlords should implement a mass-fix to ensure the integrity of their data.
The onus is on Noantics. If they don’t test their stuff before release, they have to fix their database to compensate for the error.
Yeah. Rejection reasons are generic, canned statements meant to reflect a more sophisticated judgement of the reviewer. They are not meant to be gospel, independent of circumstance-specific issues. Just like a "tree" as a waypoint category doesn't mean that all trees are acceptable, the existence of photo rejection criteria doesn't mean they're meant to be a default bin to automatically throw things in, if you know better than what you see at face value.
I would personally rather not view these submissions through a stovepipe and pretend that the bug isn't a thing that exists. As a reviewer, I have that ability to apply what I know and to make those judgements. If you can reasonably tell someone's been bitten by this bug, I wouldn't punish them for it. That just seems unnecessarily vindictive, especially when there's not a single thing they can do about it. We have enough upgrade issues as it is, and you've all seen how easy it is to lose upgrades on valid waypoints even without a bug. I'm going to give the user the benefit of the doubt. It doesn't hurt me or Niantic to do that. Niantic can fix what they've broken, whenever they get around to doing it.
We don't know how Niantic will handle this, because as usual, they are nowhere to be found for comments.
A lot of people are assuming they will just fix these nominations, but they may in the end say they just can't identify the affected ones, or maybe that swapping the pictures is too risky for the integrity of the database... Or they may fix and reset these nominations, what I see as the best solution by far.
If you have a nomination that was affected, I would try to avoid getting it upgraded at all costs. Even if people that know about the bug may consider approving them, most reviewers won't know about the bug at all.
I would never use that as an excuse for using a poor photo OR doing a shoddy job at nominating just to push through a nomination. You can clearly SEE that the photos have been swapped over IF you were reviewing. The fact that his bug exists and is costing me my time and other nominaters time to have to go out again RE nominate a perfectly good sub... I've just clearly explained the situation, to the reviewer. I've lost 5 perfectly good nominations over this poor "coding", where clearly batch uploading was not tested enough under real conditions. And its going to sadly annoy many of us that put our personal time into doing the nominations. Luckily for me, i now find it as a small hobby. I am very eager to see what Niantic have to say about it, when indeed they do come out from behind the curtain. To be continued...
Ugh!!! I was just coming here to whine about this. I submitted 6 via the “upload later” feature and they are all borked with the supplemental as the main pic. I’m going to be a sad panda when they all get rejected for “bad photo”. Grrr.
I thought that since I normally submit through Ingress that I just didn’t pay enough attention to the order of pics needed (ie in pogo it was different). I’m mildly relieved it wasn’t my mess up, but is instead a bug. Still really annoyed that they’ll all likely get the big red “reject”.
Niantic will say that they're sorry but they can't really do anything about the nominations that have already been submitted. The best I expect is them offering upgrades as compensation.