Loading Profile...
Responses not being updated
New responses are not being updated on the timeline even after refresh. Each plurk has to be checked individually to see if responses have been made. The numbers of responses are also being misreported.
I’m frustrated
20
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Sorry about this. We are working on some changes to the notification system at the moment.2 Comments
Add a comment
This solves the problem
-
Thanks for letting us know... -
How long to you anticipate it taking?
-
-
Inappropriate?similar problem in mobile version, its printed 0 responses (bold) that sign there is new responses. I must follow the link, and there is responses inside.
I’m unconcerned
-
Inappropriate?I hope that plurk going down for maintenance is a sign that things are actually going to be fixed soon. It has been pretty damn annoying for the past 6 or so hours.
I’m frustrated
-
Inappropriate?It's a day later, and it's still occuring. Is there any update that we can get, rather than a "we're working on it". We've had nothing but non-stop problems lately, and no updates or anything. Even Twitter is better at giving answers than this.
I’m frustrated
2 Comments Add a comment
This solves the problem
-
Are you still experiencing this problem now? If so, what is your plurk username so we can take a look into it.
-
it's still happening to me, too. my plurk username is 'bunneh'
-
-
Inappropriate?at the time of this writing, it is still happening to me. plurk username: bunneh
I’m frustrated
-
-
Inappropriate?Still borked, and no response, as always.
Can you guys PLEASE respond?
And still getting random responses from users who don't exist.
PLEASE FIX!
And yes, now I'm getting rude and yelling, but FFS, this has been going on for a week (new plurks and response problems), and the claims of "it's been fixed" is getting stupidly ridiculous.
I’m pissy
1 Comment Add a comment
This solves the problem
-
We're testing out a new response system. Please let us know if you experience any bugs. Hopefully this new response system fixes the problem.
http://www.plurk.com/p/ak5me -
Inappropriate?I'm not able to respond to people in my plurks in a timely manner since I don't get notification that they've responded!
I’m very sad
-
Inappropriate?the problem is only partly fixed.
the little boxes on each plurk now update properly, but the unread count notifier is still being misreported. clicking on it only reveals a small fraction of plurks with unread responses.
any news? thanks.
I’m sad
1 Comment Add a comment
This solves the problem
-
now the bug seems to be back in its original form (more or less)-- response counts on individual plurks are wrong and not being flagged as unread
-
Inappropriate?As of this morning I'm no longer getting any "N new responses [View]" box at all, even though manual scrolling shows lots of new responses. This on two different machines at different IP addresses, after page refreshes too. One FF2 and one FF3.
I’m bemused
-
Inappropriate?I'm having the same experience -- no new message reported, but red blocks nonetheless. Not what I want from my plurk experience. Both issues in IE an FF3. (dwivian)
I’m sincerely disappointed
-
Inappropriate?Plurk response counts are also WAY off. One plurk said "10" and then you click and there are 46. :(
I’m getting seriously pissy because it's taking so long to fix this issue, with no responses from staff at Plurk.
1 Comment Add a comment
This solves the problem
-
Yes, this is exactly the issue I'm having too - no notifications of the updates and far more responses than indicated.
-
Inappropriate?I don't get updates for private plurks and the numbers aren't correct either for the number of responses.
-
Inappropriate?Oh, and now, new plurks are having responses marked as read, before I even have a chance of seeing them. I only noticed because I check them before I go to unread responses, since when you hit new plurks, it doesn't automatically register in the unreads.
I’m frustrated
-
Inappropriate?The last response from the team was 7 days ago. Could you quit fuckin ignoring us?
I’m pissed off
2 Comments Add a comment
This solves the problem
-
I've tried to be nice and polite, but man, this has to be the first time I agree with you, :)
-
We are not ignoring you. Please be patient. I can tell you we've been working hard to get this fixed.
-
Inappropriate?thanks for finally saying a word @ryanlim. That's really all it takes. Letting it slide for 7 days only generates ill will no matter how hard you are working.
-
Inappropriate?ryanlim, do you need any information from us? When and how it is happening, and what type of browser we are using?
I'm noticing that comments that I haven’t read are appearing as read, the number of responses next to a plurk is not the same as the number of responses, and this just may be my layout, but I’m finding that there is a lag from my typing to the letters appearing on the screen.
Also, I've asked people to help identify issues, and they are pointing out that we not getting any new updates or new responses, even when we refresh.
I’m anxious
1 Comment Add a comment
This solves the problem
-
Hang in there. Amir is working up some code changes that may see improvements.
-
Inappropriate?Just replying to say it's happening to me too.
No "x new responses" in my timeline.
No red boxes next to plurks to indicate new responses.
Numbers next to plurks are not updating when there are responses (For example, I see a plurk with 5, click in and the number changes to 7)
When I refresh my screen, any updates I saw by clicking plurks (issue #3) revert back to the number it was before I clicked into the plurk.1 Comment Add a comment
This solves the problem
-
Thanks arik_peterson! I've verified this and we're working on it.
-
-
Inappropriate?I think we may have this bug fixed now. Could you see it works for you?
Thanks for your patience on this with us.9 Comments Add a comment
This solves the problem
-
OK, I'll ask people to check it out.
-
OK, I had time to test this, and all of a sudden my unread plurks disappeared. (I'm pretty sure I didn't hit the "m" button by mistake.) And now I have plurks that show the wrong number of responses, and when I click on them, they suddenly update to the correct amount. When I F5, they go back to the wrong number. I’ll see if I can get someone to post some responses and see if they show up.
-
the response count will auto-correct itself when a new response comes in next time. For now, you will still see the number discrepancy if you do the reload+click plurk thingie on old plurks without new response.
-
I’m seeing new responses, both on private and public plurks, and new plurks. I also left a plurk open and saw when someone responded on it. However, someone else said that they went to another profile, and when they came back all their unread plurks were gone. I believe that is what happened to me before. Let me know if I can be any more help.
-
Not working. Number of responses on individual plurks not auto-correcting, and the total number of new responses is either way low or like, 80% of the people in my timeline have died. (Normally I see >250 new responses overnight; now I'm seeing 30-40).
-
Hi @Panns, could you try clearing your browser cache and reloading plurk?
@bc: I think you are seeing less than usual responses because some plurks were not auto-corrected (nobody replied to those plurks). Could you report back if this isn't the case? -
Still seeing way less than usual new plurks and responses. I understand what you're saying about existing plurks not auto-correcting without new replies, but it still seems way off. A typical weekday morning I see hundreds of new plurks and responses. I just checked - after roughly four hours away - and I had 55. Normally that would be well over 250.
-
My issue is still not resolved either. I'm alerted to new Plurks, but not new responses.
-
This comment was removed on 12/18/08.
see the change log -
Inappropriate?based on our internal stat, looks like the daily response statistic has resumed to normal level (in fact we could very well break a new record today :-) ).
there seem to be isolated incidents where the problem still persists, according to some of the reports above. we need more detailed report on how to reproduce some of these bugs.
a thing to keep in mind is that the notification is not exactly real time - there will seconds delay between your friend posting a response to you actually getting the notification.2 Comments Add a comment
This solves the problem
-
I'm not sure what to provide in terms of how to reproduce the issue. None of the plurks in my timeline are updating to show when new responses are posted. I've tried closing my browser, logging out, clearing my browser cache, eliminating all my plurk cookie, and checking from alternative computers to validate that it's not a client side issue.
When I dig into the http request/response history, I'm seeing a bunch of 200 status codes on the AJAX requests.
I understand that it's not updated in real time...but when I click into a plurk, I see responses that have been added since the last time I was in the parent plurk. That can be 5 minutes, or a half hour.
Anything else I can provide to help, let me know... -
@arik_peterson: Yep. We're debugging this at the moment. Just thought I'd let you know.
-
Inappropriate?Also, might be another symptom of same problem but - that number of responses (50 something) I noted several hours ago? When I opened a browser and loaded my timeline a few minutes ago, it had dropped into the 30s without my viewing any or marking as read since the earlier check. -
Inappropriate?like i said before. maybe u can trace my plurk now. In my desktop/ajax plurk there is no responses notification, but when i look in mobile version there is "0 responses" that is printed in bold.
usually there is responses there. I try to not view this plurk, until you (developers) inspect this.
I hope it can help to fixed response problem.
I’m thankful
4 Comments Add a comment
This solves the problem
-
mobile version of plurk does not have auto-plurk notication because most mobile browsers do not support javascript/ajax implementation. If you refresh your mobile page, you should see an updated response count. hope that clarifies things.
-
Alvin, are you saying the responses problems are supposed to be fixed in non-mobile view?
-
yep. all our internal stats indicate that response activity has returned to normal level. So far it's running stable as far as stats and the support emails we've received are concerned, minus a couple isolated issues. Is it still not working for you?
-
@Alvin I know that mobile version doesn't have auto-plurk notification. I just want to show you that there is something wrong on that plurk. In mobile version it printed bold '0 responses', this is an abnormal situation, bold but 0 responses.
In ajax version there is no response label and (off course) no response notification. You can see at www.plurk.com/shidec
Then i try to look at this plurk without login. Yes, there is one response on this plurk. Its still like this until now.
So I think there is relationship between response bug in mobile version and ajax version.
Again, i hope you can inspect this plurk and fix the problem.
Thanks before. -
Inappropriate?Alvin, there's definitely still something wrong with new plurk and/or response handling. At a minimum, responses are getting marked as read without being seen. I have two screen shots that show exactly what I mean.
I left my browser open for a while and accumulated 90+ new responses. Here's a screen shot:
Note the number in the lower left. First problem indication is that number dropped by 30 when I closed and re-opened my browser (see next pic). I didn't view any plurks or mark any as read, yet the number went from 90s to 60s in less than two minutes. I took the first screen shot, closed the browser, re-opened, browsed to plurk, clicked "My plurks" and took the second screen shot. Somewhere in that process I lost 30 unread plurks/responses. That's a problem.
You can see the first "My plurks" view shows four plurks with new responses, while the second image shows only three. I didn't click on that plurk or mark as read, yet its "new" responses went away. This is repeatable behavior, and unless this arbitrary marking as read is supposed to be some kind of feature, it's a problem. :)2 Comments Add a comment
This solves the problem
-
Actually - simply put, it seems like Plurk is now capping new responses at 50 when the page loads, and marking excess as read. Is that by design?
-
Hi bc
We keep a list of 200 unread plurks and updating it. It's maxed at 200 and uses the FIFO principle (First in, first out) to purge the list. Now if you follow a lot of people and have a lot of Plurks muted, your unread list will bet purged rather quickly. We may increase this in the future, but currently it's an optimization issue.
Regards,
Amir -
Inappropriate?Amir, thanks for explaining.
-
Inappropriate?I suspect this is related to my experience—for the last week or so, Plurk has routinely marked recent threads with unread responses as read to the point where it's unusual for me to see more than forty or fifty responses overnight. Closer to one hundred is more normal for my timeline. I've scrolled back and messages barely a few hours old with responses that I know I have not seen before are being marked as read.
I realize this is a free service, but the service's growing instability is killing this user's experience. I'm starting to hope people on my timeline will migrate to other social services so I can keep in touch with them.
I’m really, really frustrated!
-
Inappropriate?It's happening again. Everything was fine until last night/this morning with the "updates"
I’m frustrated
-
Inappropriate?I'm having this problem since December and was hoping it's gone after my holidays. As long as I keep the Plurk-site open and check it every few minutes, I don't miss anything. But after two weeks only 90something plurks? Most annoyingly I have to search for replies on plurks I replied to, even my own. I have over 350 contacts and mute plurks a lot, but still want to "scan" them all. I hit "mark all as read" now, which I hardly ever did before...honestly this is taking the fun out of plurk for me. Hope you guys are still "working on it".
I’m sad and frustrated.
2 Comments Add a comment
This solves the problem
-
We will improve things as we move on, but currently we do it because it's better to put a cap on number of unread plurks than to have load issues.
Kind regards,
Amir -
It's your service to do with as you please, but the complete lack of announcement of this sudden change is a prime example of how frustrating using Plurk has recently become. PLEASE take steps to inform your customers of this kind of substantive change to the service! As it stands right now, the bulk of users probably assume that their messages are disappearing because the system is fundamentally broken. Keeping people in the dark about changes of that magnitude is not a way to keep customers happy or around. You're obviously bright, clever people; you should be able to find a fairly simple and direct way of addressing the public relations disaster you're currently mired in.
-
Inappropriate?you are right. We should have been more communicative with our community about this. My apology.
for everyone's information though, we have always had cap, even from the first day we launched. It's just that recently we decided to tweak it a little bit based on the general pattern of our users usage behavior.
Most (~98%) of our total users won't even notice the changes. But I do understand there are rare cases like some of the people in this thread that are being affected by it.
I hope this clarifies the confusion.3 Comments Add a comment
This solves the problem
-
I remember at the beginning the counter started capping at 250, but added more unread after a refresh back to 250 until all unread messages were really read. At first marking all as read just meant those 250, later it meant really all (more than 250 shown).
On my time-line I read a lot of anger and confusion about dissapearing messages, no replies etc. pp.. It would be nice to know the pattern if it's meant to stay like that. So I know when I log in...I will only see the freshest 90 messages, all others are lost. Also it would be lovely to understand what it's doing when I hit "blah new plurks - update" with the new messages, this number is going down if it went up to high. I guess there's no way that at least the tabs (my plurks, private and responded) are not capped? Maybe I have to many contacts and that makes me one of those unlucky 2%. -
I remember at the beginning the counter started capping at 250, but added more unread after a refresh back to 250 until all unread messages were really read. At first marking all as read just meant those 250, later it meant really all (more than 250 shown).
On my time-line I read a lot of anger and confusion about dissapearing messages, no replies etc. pp.. It would be nice to know the pattern if it's meant to stay like that. So I know when I log in...I will only see the freshest 90 messages, all others are lost. Also it would be lovely to understand what it's doing when I hit "blah new plurks - update" with the new messages, this number is going down if it went up to high. I guess there's no way that at least the tabs (my plurks, private and responded) are not capped? Maybe I have too many contacts and that makes me one of those unlucky 2%. -
you are correct, Tarissa. That's how it used to work :). Like amir said, we will definitely reevaluate the cap as the system stabilizes. Maybe even upping the cap for private plurks. But at this moment, we, and I'm sure our users as well, want a stable site than being able to read all the plurk responses. It is rather unfortunate our users have to share this growing pain with us, but atm, this is the best we can do. :|
-
Inappropriate?Unfortunately, 80% of my plurk friends are falling into the unlucky 2%, too. -
EMPLOYEE
EMPLOYEE
