**** BEGIN LOGGING AT Fri Aug 09 02:59:57 2019 Aug 09 06:38:12 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? Aug 09 06:41:08 Apparently thirteen days of the archived conversation with one of my contacts on Facebook Messenger is missing. WTF? Aug 09 06:43:08 compare with the website ... Aug 09 06:43:34 I am using the messenger.com Web application. Aug 09 06:44:32 i haven't missed any messages in mine (so far) Aug 09 06:50:13 does messenger allow one to delete a message for himself *and* the other party? if so, maybe that's what happened to you? Aug 09 06:56:09 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 Aug 09 06:56:09 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. Aug 09 07:19:12 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. Aug 09 07:22:36 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. Aug 09 11:37:03 hey hackers! how would I *disable* the touchscreen completely while keeping display and input from slide-out kbd operational? Aug 09 11:37:26 modeprobe -r something? Aug 09 11:38:13 purpose: I want to run N900 xchat in "kiosk mode" Aug 09 11:39:30 bunus points for: whenopening camera door, allow taking photos. When closing camera app or door again, return focus to xchat immediately Aug 09 11:39:39 bonus even Aug 09 11:41:19 Disconnect the cable for the touch panel from the computer/motherboard? Aug 09 11:41:35 nah, too invasive Aug 09 11:41:41 also I need display Aug 09 11:41:50 rm /dev/input/event3 Aug 09 11:41:57 Might need to do that before starting Xorg. Aug 09 11:42:21 Can probably actually just disable it within Xorg Aug 09 11:42:37 I'd *think* I could disable/rmmod the digitizer driver Aug 09 11:42:54 DocScrutinizer05: That is why I said the cable for the touch panel, not the cable for the display. Aug 09 11:42:58 Probably not as long as Xorg has that file open. Aug 09 11:43:12 hehe that's absolutely non-trivial Aug 09 11:44:21 I *might* spoil the calibration so no matter what, each click on touchscreen is in center Aug 09 11:44:24 ;-P Aug 09 11:45:28 but I guess it's way simpler to modprobe -r / rmmod the driver Aug 09 11:45:45 I really doubt that's possible without getting Xorg to close the file. Aug 09 11:45:57 more tricky: the bonus pack Aug 09 11:46:09 since having that file open will be considered a use of the driver, so you won't be able to unload it. Aug 09 11:47:06 need to learn how to bring a window on top via cmdline Aug 09 11:48:06 so whenever something unique indictaes on dbus that camera been closed, bring xchat on top again via dbus-scripting Aug 09 11:49:48 AAAAH WAIT! matan's HD should accept some simulated keypress to activate the only other app except camera again: which is xchat Aug 09 11:50:41 is there xdotool on N900? Aug 09 12:02:41 I think I might know a way to do it. Aug 09 12:05:34 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"')' Aug 09 12:05:41 where $pid is the PID of Xorg Aug 09 12:06:11 * Maxdamantus tries something similar on his desktop. Aug 09 12:10:08 Yeah, that seems to work on my desktop. I imagine it should work in Maemo too. Aug 09 12:10:20 * Maxdamantus doesn't want to have to restart Xorg on his phone atm Aug 09 12:11:34 Actually, don't do that. Aug 09 12:12:21 since it doesn't end up actually closing the fd, so it just wastes CPU constantly reading the EOF. Aug 09 12:24:19 Okay, here's a better way: Aug 09 12:24:41 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"')' Aug 09 12:25:31 That way it just replaces the fd with a pipe that will never have any data to read. Aug 09 12:30:51 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 Aug 09 12:30:57 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"')' Aug 09 14:28:57 some very usual maemo porn: https://termbin.com/jzva Aug 09 15:12:11 DocScrutinizer05: Interesting. Aug 09 19:30:52 👍 Aug 09 19:52:03 just 'echo 1 > /sys/devices/platform/omap2_mcspi.1/spi1.0/disable_ts' to disable touch screen on N900 and 'echo 0' to enable Aug 09 19:52:13 it Aug 09 19:52:46 it's simple as that Aug 09 20:22:40 Unless you use a 2.4 kernel. ;-) Aug 09 20:25:32 I was thinking something similar Aug 09 20:29:25 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. Aug 09 20:33:35 The OS already seems to read/write to that sysfs node, so you'll probably want to `chmod -r` it. Aug 09 20:33:46 er, `chmod -w` Aug 09 20:35:30 rather, `chmod ugo-w` Aug 09 21:21:06 done similar with cam button, change the state and lock it by making the file 444 **** ENDING LOGGING AT Sat Aug 10 03:00:09 2019