Overclock.net › Forums › Overclock.net Forum › Bugs and Technical Issues › [CONFIRMED] I cannot upload a picture or a screenshot!
New Posts  All Forums:Forum Nav:

[CONFIRMED] I cannot upload a picture or a screenshot! - Page 18  

post #171 of 175
@ENTERPRISE Like I said before I believe the fact it is happening between 11PM and 6AM in their timezone means people are not monitoring it during the time the problem happens, therefore they do not see it happening, therefore they do not find the issue and therefore do not find any 'problem' and cannot formulate a possible resolution. Sure OCN was not functioning at all they would be up and working on it. It's a case of the squeaking gear gets the most oil. If we don't 'squeak' loudly they don't aggressively try to find the problem. I'm sure you realize there are many other users having problems uploading images than are reporting them. wink.gif At least 10 and quite possibly 100 for each one who has posted in this thread. Some who did report it in the beginning turned and ran when the huddlers' with their 'better than us' tech to user attitude posted images saying system was working fine during times the system was working fine .. mocking us with their afternoon (our time) hours, then when we jumped back edited their posts and replies and locked the thread .. all of which was scurbbed out of theead in it's fors few pages. tongue.gif
I consulted several developer friends and aquantances.
I know for many users this is only a little inconvenience, but for some of us who are quite active before noon each day, often posting advice and information to users using custom drawn images to explain things it is a major inconvenience. Posting without the images makes it hard for users to understand and requires much more in-depth descriptions in English that is not as easy for people for whom English is a 2nd language. And the time it takes to upload image to an online image server, then move it to post means no image is posted.

@TheCautiousOne Yeah, makes sense you would rarely have the problem. Being between 7am and 2pm BDT which is between 1am and 8am your time.
post #172 of 175
Quote:
Originally Posted by doyll View Post

@ENTERPRISE Like I said before I believe the fact it is happening between 11PM and 6AM in their timezone means people are not monitoring it during the time the problem happens, therefore they do not see it happening, therefore they do not find the issue and therefore do not find any 'problem' and cannot formulate a possible resolution. Sure OCN was not functioning at all they would be up and working on it. It's a case of the squeaking gear gets the most oil. If we don't 'squeak' loudly they don't aggressively try to find the problem. I'm sure you realize there are many other users having problems uploading images than are reporting them. wink.gif At least 10 and quite possibly 100 for each one who has posted in this thread. Some who did report it in the beginning turned and ran when the huddlers' with their 'better than us' tech to user attitude posted images saying system was working fine during times the system was working fine .. mocking us with their afternoon (our time) hours, then when we jumped back edited their posts and replies and locked the thread .. all of which was scurbbed out of theead in it's fors few pages. tongue.gif
I consulted several developer friends and aquantances.
I know for many users this is only a little inconvenience, but for some of us who are quite active before noon each day, often posting advice and information to users using custom drawn images to explain things it is a major inconvenience. Posting without the images makes it hard for users to understand and requires much more in-depth descriptions in English that is not as easy for people for whom English is a 2nd language. And the time it takes to upload image to an online image server, then move it to post means no image is posted.

@TheCautiousOne Yeah, makes sense you would rarely have the problem. Being between 7am and 2pm BDT which is between 1am and 8am your time.

 

Indeed, some of it comes down to prioritization. While the uploader issue was definitely an annoying one, it was not 100% consistently failing at all times. With this in mind it was a of a lower priority but was still being researched, again to further exacerbate issues it was happening during closed office hours at the Devs end which made it hard to track. 2 Of our developers actually stayed up late through the early hours of the morning to track the issue, it was only then that they were able to identify anything which is odd as usually speaking this type off issue you would usually expect to find the cause somewhat easier than they did.

 

Issues can be unique and only people at ground zero who are familiar with the software are in the know. You can consult as many developers as you want, but unless they are familiar with the software or are at ground zero...they are not in a position to really evaluate the situation.

 

Alas, the delay in finding the fix can be attributed to a a couple of factors as indicated.  It was annoying and frustrating for all and we can appreciate that.

 

The good thing is that we are on to it now :)

post #173 of 175
Quote:
Originally Posted by ENTERPRISE View Post

Indeed, some of it comes down to prioritization. While the uploader issue was definitely an annoying one, it was not 100% consistently failing at all times. With this in mind it was a of a lower priority but was still being researched, again to further exacerbate issues it was happening during closed office hours at the Devs end which made it hard to track. 2 Of our developers actually stayed up late through the early hours of the morning to track the issue, it was only then that they were able to identify anything which is odd as usually speaking this type off issue you would usually expect to find the cause somewhat easier than they did.

Issues can be unique and only people at ground zero who are familiar with the software are in the know. You can consult as many developers as you want, but unless they are familiar with the software or are at ground zero...they are not in a position to really evaluate the situation.

Alas, the delay in finding the fix can be attributed to a a couple of factors as indicated.  It was annoying and frustrating for all and we can appreciate that.

The good thing is that we are on to it now smile.gif
I hear an echo. tongue.gif

My statement seems to be spot on. After doing little or nothing, developers monitored the system during the hours issue was happening an identified it.

My reference to consulting others was in reference to removed or changed post with no history of the changes. All readily agreed it was indeed generally not a big deal to do this at their access level .. in other words I most likely did not imagine it happened, but t actually did happen. biggrin.gif

I can understand not aggressively addressing the problem, but spending a month covering it up by saying it was being hard to find is total garbage. All it took was a developer or two spending the time looking for the problem during the time of day it was occurring and you know know it is for real. The fact this was not done for a month while posting up it was being worked on is what I feel was poor handling of the problem. It shows a very poor response by developer to a problem, even if it was not a big problem to most users on earth. In the beginning all we (the users experiencing the problem) wanted was for it to be acknowledged as at least a possible issue, something the the huddlers did not do when it was first reported. This was compounded by a month of being 'patted on the head' and told it was being looked into with statements like
"Seeing as how we're chasing an intermittent problem (as many support posts stated), it's difficult to reproduce on demand, which is what our devs need to fix it."
But doing it at times it was not happeining .. and never doing it during the time frame it was happening in .. while we (the users experiencing the problem) knew for sure it was happening every day during the time frame we kept saying it was happening. .. and only then (a month later) was it really looked at and found .. in the first 6 hour period developers finally monitored it in the time frame it was occurring and finding the issue.

So why were we told it was being 'worked on' when it was not? Why did it take a month of these 'miss-information' posts about it being worked on before it was actually looked at?

I for one feel we were strung along. That this 'miss-information' we were told is offensive. That we deserved to know it was not being worked on instead of being placated with 'miss'information'.

I can accept the developers being too busy to address the problem.

I do not accept being treated the way we were. mad.gif

Respect is a two way street, and I do not feel this two way respect was exercised here. mad.gif
post #174 of 175
We will have to agree to disagree on this occasion as the developers were actively trying to remedy the issue and I see no mis informstion here but again, thanks to all who helped to track this issue smile.gif

I consider this a closed case. Should the issue return please PM me.

Regards,
E
post #175 of 175
This Bug has now been reproduced 100% by the team and a fix is now being created and will be deployed ASAP.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Bugs and Technical Issues
This thread is locked  
Overclock.net › Forums › Overclock.net Forum › Bugs and Technical Issues › [CONFIRMED] I cannot upload a picture or a screenshot!