>Which part didn't you understand? The part where you think that this is the appropriate channel for discussing general IT problems you are having with your computer
> I don't know if it was something in "t x"'s message that triggered it Well you accused him of that pretty much right off the bat... > In any event, if anyone can shed any light on this incident I'd appreciate information. Sure, it can be a number of things. a) a bug in your mouse driver. b) a failing mouse battery. c) dirt on/in the mouse d) a bug in your browser e) a virus on your computer. f) a bug in gmail. All of these are much, much more likely than what you originally suggested. The idea that someone posting to a google group can get a virus through a text email, and that that virus somehow affected your browser, is just laughable. Timothy On Thu, Jan 23, 2014 at 7:34 PM, Cedric Greevey <cgree...@gmail.com> wrote: > Which part didn't you understand? When I scrolled down to "t x"'s message, > after a short delay *something* wrested control of Firefox away from me and > issued a sequence of navigation commands the effect of which was to log me > out of gmail, much as if I'd clicked the little down arrow by my username > and then clicked "signout". > > I don't know if it was something in "t x"'s message that triggered it (if > so, it didn't have the same effect when I viewed it again after logging > back in), but I do know that I do not appreciate having my computer > hijacked. I'm sure you can understand how it's rather alarming to have your > stuff just suddenly start acting on "its own initiative", right in front of > your eyes, when the damned thing isn't supposed to *have* its own > initiative. > > In any event, if anyone can shed any light on this incident I'd appreciate > information. (For example: does an expert on browser security see anything > in "t x"'s post, or any other in this thread, that could have triggered > anything unusual in susceptible versions of Firefox? Should I wipe and > reinstall this machine on the presumption that the seemingly superficial > hijack left it infected with a nasty rootkit of some sort, or was it just a > prank, or even a known software bug somewhere?) > > > On Thu, Jan 23, 2014 at 9:20 PM, Timothy Baldridge > <tbaldri...@gmail.com>wrote: > >> Um........wat? >> On Jan 23, 2014 7:17 PM, "Cedric Greevey" <cgree...@gmail.com> wrote: >> >>> [meta, but about something apparently triggered by the message, from >>> this thread, that I'm quoting] >>> >>> Why did reading this post cause gmail to go bonkers? I saw this thread >>> had new articles since earlier today, brought it up, and read the previous >>> message, then just after I'd scrolled down to this one, leaned back, and >>> started reading it the browser just suddenly began spinning on its own and >>> navigated by itself. Apparently about 10 seconds after I sat back >>> *something* input a click on the little down-triangle in the upper right >>> corner of the page and then clicked "sign out" because it went to the gmail >>> login page. And a second or so before that the chat thingy at the left >>> crashed as a popup there distracted me by appearing suddenly and saying >>> something like "Oops, problem connecting to chat". >>> >>> I don't like having my stuff suddenly go spinning out of control like >>> that. I wasn't touching the keyboard or the mouse at the time. The browser >>> should not have done anything but sit there patiently displaying this page >>> until *I* *CHOSE* to navigate away from it. If there is something in your >>> message that hijacks the browsers of people reading it, then I would like >>> you to know that I consider such a thing to be extremely poor etiquette and >>> in extremely poor taste. Do not do it again. If it was not that particular >>> message then I'd like to know what *did* reach into *MY* computer and start >>> issuing instructions on *MY* behalf *without* *MY* permission, and how to >>> stop that from ever happening again. This is *MY* copy of Firefox and it >>> goes where *I* say it does, when *I* say it does it, and not a moment >>> sooner. Is that absofrickinglutely clear? That is non-negotiable. Anyone >>> who willfully violates this edict *will* be added to my spam filter and I >>> will not see any future post by that author. Is *that* clear? >>> >>> >>> >>> >>> On Thu, Jan 23, 2014 at 7:21 AM, t x <txrev...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> * This is the time I've heard "the one who's feeding the channel is >>>> the one in charge of closing it" -- previously, my channel code was fairly >>>> ad-hoc and agressive (since I need to kill many (go-loop [msg (<! ... )] >>>> (when msg ...)) blocks). >>>> >>>> * I still feel this breaks the "conveyor belt" metaphor -- when a >>>> conveyor belt shuts down, it's understandable that we after we take what's >>>> on the belt, in future takes, we get nothing. >>>> >>>> However, when putting items on a stopped conveyor belt, messages >>>> should not just *poof* vanish into the void. :-) >>>> >>>> * This existing semantics makes debugging annoying (perhaps this is >>>> due to my lack of skill). When something should be happening, and nothing >>>> is happening, I'm basically going around hunting for "where did I do a put >>>> on a closed channel", whereas if it threw an exception of some form, it'd >>>> be easier to handle then this "silent fail." >>>> >>>> >>>> >>>> >>>> On Thu, Jan 23, 2014 at 3:50 AM, Meikel Brandmeyer (kotarak) < >>>> m...@kotka.de> wrote: >>>> >>>>> Hi, >>>>> >>>>> probably the idea is, that the one who's feeding the channel is the >>>>> one in charge of closing it. After all, they know when there is no more >>>>> input available. Do you have a use case where this problem manifests? Or >>>>> is >>>>> that just a vague fear that it might happen? >>>>> >>>>> Kind regards >>>>> Meikel >>>>> >>>>> -- >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Clojure" group. >>>>> To post to this group, send email to clojure@googlegroups.com >>>>> Note that posts from new members are moderated - please be patient >>>>> with your first post. >>>>> To unsubscribe from this group, send email to >>>>> clojure+unsubscr...@googlegroups.com >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/clojure?hl=en >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Clojure" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to clojure+unsubscr...@googlegroups.com. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> -- >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To post to this group, send email to clojure@googlegroups.com >>>> Note that posts from new members are moderated - please be patient with >>>> your first post. >>>> To unsubscribe from this group, send email to >>>> clojure+unsubscr...@googlegroups.com >>>> For more options, visit this group at >>>> http://groups.google.com/group/clojure?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to clojure+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clojure@googlegroups.com >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/clojure?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to clojure+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- “One of the main causes of the fall of the Roman Empire was that–lacking zero–they had no way to indicate successful termination of their C programs.” (Robert Firth) -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
