04:42 | <rdead> | yooo |
04:46 | <rdead> | staying one step behind there heels got me here......whatever i can do to help |
08:09 | <annevk> | sideshowbarker: answer there seems pretty good, but added a comment |
08:09 | <annevk> | sideshowbarker: weird that both the person asking and answering have such a weird username, but perhaps that's the result of some API outage |
08:48 | <sideshowbarker> | annevk: thanks for commenting But about the usernames — those auto-assigned/generated ones — quite a few people never actually change those |
08:53 | <sideshowbarker> | hmm, but one thing I notice now: the OP paid out a 300-point bounty for that answer — which seems a bit unusual given they only have 578 left… |
08:55 | <sideshowbarker> | …and especially also given that the question isn’t a how-do-I-fix-this-problem question but instead a “why?” question, paying out 300 Stack Overflow points on that kind of question seems pretty odd |
08:55 | <sideshowbarker> | still, it’s a pretty good question |
08:56 | <nicolo-ribaudo> | StackOverflow points laundering 👀 |
09:35 | <annevk> | Yeah, it's weird but it also doesn't seem like a straightforward copy-and-paste case given all the references and dates. |
13:45 | <annevk> | Hmm, Response.error() seems like a mistake. It's the only way you can get at a network error in the API whereby it's not a TypeError exception. |
13:45 | <annevk> | I suspect blame points to me. :-/ |
14:43 | <annevk> | Well, I wasn't alone: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26731. Very surprising oversight now. |
17:18 | <rdead> | So I see now,....but it didnt autogenerate my usernane, buuut anywho <' -'> |
23:46 | <susanjessy> | https://t.me/+PEc8FSRwFiFiYzc0 |