| brolin_empey | If anyone else here uses an official application for Facebook Messenger, have you noticed an apparently significant part of a conversation missing when reading the backlog from months ago? I noticed at least one of these gaps today and am wondering if it is caused by a software defect or if Facebook has intentionally deleted part of my archived conversation and thought I would not notice? | 08:38 |
|---|---|---|
| brolin_empey | Apparently thirteen days of the archived conversation with one of my contacts on Facebook Messenger is missing. WTF? | 08:41 |
| sicelo | compare with the website ... | 08:43 |
| brolin_empey | I am using the messenger.com Web application. | 08:43 |
| sicelo | i haven't missed any messages in mine (so far) | 08:44 |
| sicelo | does messenger allow one to delete a message for himself *and* the other party? if so, maybe that's what happened to you? | 08:50 |
| brolin_empey | The other party is a woman in this case but, regardless, I do not think they would have tried to delete part of the conversation. Skype, at least with the official client, apparently allows a user to change and maybe also delete a message after sending it and have this change shown to the other party but, as far as I know, Facebook Messenger does not have this same capability of historical revisionism in the negative sense. I mostly stopped using Skype | 08:56 |
| brolin_empey | because it became redundant. The reason I mention that the other party is a woman in this case is because I do not think they would use a masculine pronoun to refer to theirself. | 08:56 |
| brolin_empey | Heh, this seems to be Yet Another case of the messenger.com Web application being flaky because the messages that I thought were missing appear to still be there after I reloaded the page. | 09:19 |
| brolin_empey | Well, they certainly were missing before I reloaded the page. I even have a screenshot showing the missing messages because I was considering asking the other person if the same messages were missing for them too. I mean that the screenshot shows that messages are missing; obviously it does not show the messages that are missing. | 09:22 |
| DocScrutinizer05 | hey hackers! how would I *disable* the touchscreen completely while keeping display and input from slide-out kbd operational? | 13:37 |
| DocScrutinizer05 | modeprobe -r something? | 13:37 |
| DocScrutinizer05 | purpose: I want to run N900 xchat in "kiosk mode" | 13:38 |
| DocScrutinizer05 | bunus points for: whenopening camera door, allow taking photos. When closing camera app or door again, return focus to xchat immediately | 13:39 |
| DocScrutinizer05 | bonus even | 13:39 |
| brolin_empey | Disconnect the cable for the touch panel from the computer/motherboard? | 13:41 |
| DocScrutinizer05 | nah, too invasive | 13:41 |
| DocScrutinizer05 | also I need display | 13:41 |
| Maxdamantus | rm /dev/input/event3 | 13:41 |
| Maxdamantus | Might need to do that before starting Xorg. | 13:41 |
| Maxdamantus | Can probably actually just disable it within Xorg | 13:42 |
| DocScrutinizer05 | I'd *think* I could disable/rmmod the digitizer driver | 13:42 |
| brolin_empey | DocScrutinizer05: That is why I said the cable for the touch panel, not the cable for the display. | 13:42 |
| Maxdamantus | Probably not as long as Xorg has that file open. | 13:42 |
| DocScrutinizer05 | hehe that's absolutely non-trivial | 13:43 |
| DocScrutinizer05 | I *might* spoil the calibration so no matter what, each click on touchscreen is in center | 13:44 |
| DocScrutinizer05 | ;-P | 13:44 |
| DocScrutinizer05 | but I guess it's way simpler to modprobe -r / rmmod the driver | 13:45 |
| Maxdamantus | I really doubt that's possible without getting Xorg to close the file. | 13:45 |
| DocScrutinizer05 | more tricky: the bonus pack | 13:45 |
| Maxdamantus | since having that file open will be considered a use of the driver, so you won't be able to unload it. | 13:46 |
| DocScrutinizer05 | need to learn how to bring a window on top via cmdline | 13:47 |
| DocScrutinizer05 | so whenever something unique indictaes on dbus that camera been closed, bring xchat on top again via dbus-scripting | 13:48 |
| DocScrutinizer05 | AAAAH WAIT! matan's HD should accept some simulated keypress to activate the only other app except camera again: which is xchat | 13:49 |
| DocScrutinizer05 | is there xdotool on N900? | 13:50 |
| Maxdamantus | I think I might know a way to do it. | 14:02 |
| Maxdamantus | fd="$(ls -lh /proc/"$pid"/fd/ | sed 's:^.* \([0-9]\+\) -> /dev/input/event3:\1:; t; d')"; [ "$fd" != "" ] && gdb --batch -p "$pid" -ex 'p (int)dup2((int)open("/dev/null", 0), '"$fd"')' | 14:05 |
| Maxdamantus | where $pid is the PID of Xorg | 14:05 |
| * Maxdamantus tries something similar on his desktop. | 14:06 | |
| Maxdamantus | Yeah, that seems to work on my desktop. I imagine it should work in Maemo too. | 14:10 |
| * Maxdamantus doesn't want to have to restart Xorg on his phone atm | 14:10 | |
| Maxdamantus | Actually, don't do that. | 14:11 |
| Maxdamantus | since it doesn't end up actually closing the fd, so it just wastes CPU constantly reading the EOF. | 14:12 |
| Maxdamantus | Okay, here's a better way: | 14:24 |
| Maxdamantus | fd="$(ls -lh /proc/"$pid"/fd/ | sed 's:^.* \([0-9]\+\) -> /dev/input/event3:\1:; t; d')"; [ "$fd" != "" ] && gdb --batch -p "$pid" -ex 'p (int *)malloc(8)' -ex 'p (int)pipe($1)' -ex 'p (int)dup2(*$1, '"$fd"')' | 14:24 |
| Maxdamantus | That way it just replaces the fd with a pipe that will never have any data to read. | 14:25 |
| Maxdamantus | Meant to have an end anchor in that sed command, though shouldn't make a difference unless you have 30 input devices for some reason | 14:30 |
| Maxdamantus | fd="$(ls -lh /proc/"$pid"/fd/ | sed 's:^.* \([0-9]\+\) -> /dev/input/event3$:\1:; t; d')"; [ "$fd" != "" ] && gdb --batch -p "$pid" -ex 'p (int *)malloc(8)' -ex 'p (int)pipe($1)' -ex 'p (int)dup2(*$1, '"$fd"')' | 14:30 |
| DocScrutinizer05 | some very usual maemo porn: https://termbin.com/jzva | 16:28 |
| brolin_empey | DocScrutinizer05: Interesting. | 17:12 |
| esaym153 | 👍 | 21:30 |
| ontime | just 'echo 1 > /sys/devices/platform/omap2_mcspi.1/spi1.0/disable_ts' to disable touch screen on N900 and 'echo 0' to enable | 21:52 |
| ontime | it | 21:52 |
| ontime | it's simple as that | 21:52 |
| brolin_empey | Unless you use a 2.4 kernel. ;-) | 22:22 |
| sixwheeledbeast | I was thinking something similar | 22:25 |
| Maxdamantus | Ah, was wondering if you could just do something like that through sysfs, though I only looked in the directory corresponding to the "event3" input device. | 22:29 |
| Maxdamantus | The OS already seems to read/write to that sysfs node, so you'll probably want to `chmod -r` it. | 22:33 |
| Maxdamantus | er, `chmod -w` | 22:33 |
| Maxdamantus | rather, `chmod ugo-w` | 22:35 |
| sixwheeledbeast | done similar with cam button, change the state and lock it by making the file 444 | 23:21 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!