**** BEGIN LOGGING AT Fri Nov 22 02:59:57 2019 Nov 22 07:28:49 At least on x86, Windows 10 and Windows Server 2019 can still be installed and run on a computer using BIOS instead of EFI but apparently you are discussing Windows NT 10 for ARM, not x86. Nov 22 07:31:31 Regarding what I said about the apparent demise of non-EFI motherboards somewhere after Nehalem, according to https://en.wikipedia.org/wiki/Template:Intel_processor_roadmap there are “no more non-UEFI motherboards” beginning with or after (?) Sandy Bridge. Nov 22 08:08:12 does any of you use any one drive client in linux? Nov 22 09:02:14 gmail's spam filter sucks. outlook's one is way more accurate. hope these instructions actually work for disabling gmail's filter, https://c-command.com/spamsieve/help/turning-off-the-gmail-s Nov 22 09:02:55 i don't know if you guys saw this, https://arstechnica.com/gadgets/2019/11/google-outlines-plans-for-mainline-linux-kernel-support-in-android/ Nov 22 09:44:49 sicelo: Every time I register a new account for something that will or may email me I usually create a new filter in my Google Mail account that says to never mark mail from the new sender for the new account as spam because otherwise ham ends up in spam because of false positives of the Google Mail spam filter. Nov 22 09:51:12 Not that it matters because I rarely play any computer game at all any more, never mind recent demanding games, but would a desktop computer with a Core i7 920 model of CPU, one of the original models of Core i7 from 2008 November, still suffice for running something like, say, Overwatch with an SSD and a somewhat recent video card? I think I have still never even tried running any local/native (not Web-based) game full-screen since I upgraded to a Nov 22 09:51:12 3840×2160 4k UHD video monitor. Nov 22 10:20:09 I ask because apparently a refurbished desktop computer with Core i7 920 CPU, 16 GiB of main memory, 480-GB SSD, Wireless LAN controller, DVD±RW drive, some unspecified ATI video card, apparently a genuine licence for Windows 10 Professional for x86-64 sells for only 299 CAD excluding taxes but including shipping to Canada: Nov 22 10:20:09 https://www.amazon.ca/dp/B07RQW1PH6/ref=sspa_dk_detail_1?psc=1&pd_rd_i=B07RQW1PH6&pd_rd_w=9oPCr&pf_rd_p=4b7c8c1c-293f-4b1e-a49a-8787dff31bcb&pd_rd_wg=EW9h2&pf_rd_r=FRPKZVB4FJYJBCGJV6MN&pd_rd_r=acbd0125-8703-4104-b98e-a7f40b44e1ec&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEzN05PTlpERjBJQ1Q0JmVuY3J5cHRlZElkPUEwMzMwNTcyUklINlFQOFlMTzlXJmVuY3J5cHRlZEFkSWQ9QTAxNzEzMTMxQUU4SklJV1M2TVFUJndpZGdldE5hbWU9c3BfZGV0YWlsJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ== Nov 22 10:43:42 Yes, unfortunately it probably has at least one or two fans. It is my father, not me, who is shopping for a “new” computer. I would still rather have a fanless x86-64 computer because having a literally silent computer is awesome when you are used to always hearing a fan in a computer. Nov 22 10:44:52 Well, considering that the TDP rating of the CPU is 130 W, I guess it almost certainly has a fan on at least the CPU heatsink. Nov 22 10:48:44 fanless 130W cpus , haha Nov 22 10:50:54 buZz: Well, a 100 W incandescent light bulb is used without a fan. Nov 22 10:52:34 those are illegal here nowadays Nov 22 10:54:23 Because of the energy consumption or the fire risk? Nov 22 10:55:42 The energy consumption, surely. Nov 22 10:56:10 * Maxdamantus suspects LED bulbs would generally be a greater (though still fairly insignificant) fire risk. Nov 22 10:56:25 actually, nvm, that's probably not true. Nov 22 10:56:35 actually, dunno, it might be. Nov 22 10:57:54 because afaik LED bulbs usually just rectify the mains power, and if you end up with arcing, it's more likely to pose a fire risk on DC. Nov 22 10:58:29 but the arcing would likely have to result from a short circuit, since they obviously don't normally use much current. Nov 22 10:59:15 brolin_empey: energy, yeah Nov 22 10:59:21 afaik they are still legal as heat sources Nov 22 10:59:24 but not as lights Nov 22 11:04:14 Does a self-ballasted compact fluorescent lamp have to convert the AC from the lamp socket to DC? Or does it only use AC? Nov 22 11:05:27 I think fluorescent lamps use high-frequency AC. Nov 22 11:11:22 If a fluorescent lamp uses alternating current, does that mean that a computer with a display with a fluorescent backlight, such as old computers with an integrated LCD that uses a CCFL backlight, has to convert the AC from the mains power supply unit to DC used by the power input connector of the computer only for the fluorescent backlight to convert the DC back to AC? Imagine if you use an inverter to power such a computer from a vehicle: the DC from the Nov 22 11:11:22 vehicle gets converted to AC by the inverter connected to the vehicle power outlet, then the computer PSU converts the AC back to DC, then the display backlight inverter converts the DC back to AC. :-D Nov 22 12:17:58 This is the reality of making devices compatible with the worlds infrastructure. Conductor materials are expensive it's a way of using less materials to the load. Nov 22 12:18:46 Also ICE vehicles have AC and DC supplies Nov 22 19:36:20 synchronizing tasks with syncevolution & radicale works, but it's a bit useless. not sure why, but Android thinks a task meant for tomorrow is due today. beats me why DAVx5 gets the date wrong, because i can see in the syncevolution logs that the date is correct, and inspecting the vcal as stored in radicale also has correct date. Nov 22 19:54:11 n900 applies correct date for an event created on Android/DAVx5, just doesn't show an alarm, etc. which is to be expected. Nov 22 20:05:29 why? Nov 22 20:06:23 DAVx5 is working fine for me, but KOrganizer doesn't like recurring events.. Nov 22 20:15:33 here is a task i created on N900, http://paste.debian.net/1117506/ Nov 22 20:16:23 please try to import it into KOrganizer, sync with DAVx5, and see what date DAVx5 shows for you. maybe something's wrong at my end Nov 22 20:30:03 i think i see what's wrong here .. so N900 does not include (1) timezone info in the task file, and (2) in the DUE-DATE field, leaves the time as 00:00, since that's in the alarm, defined in an X-field. DAVx5/Android on the other hand seems to expect a timezone, and a time to be in the DUEDATE field. my timezone is UTC-2, so DAVx5 says the event is due at 22:00 the previous day Nov 22 21:30:18 sicelo: sounds like a N900 bug Nov 22 21:30:39 obviously without a timezone specified everything should assume UTC Nov 22 21:35:25 ahoy! 2do on Android is happy with the N900's tasks. so i'll use that. yay Nov 22 21:36:06 now if only there was something to sync Notes from calendar (radicale calls it Journal. DAVx5 doesn't support it) Nov 22 21:55:35 $ date --date="00:00" Nov 22 21:55:36 Sat Nov 23 00:00:00 NZDT 2019 Nov 22 21:56:52 also, I think it's fairly typical for log files to just use the local time without denoting the timezone. Nov 22 22:02:34 and funny enough, Android's built it calendar has no problem reading the time from N900's vcal files, even though they also don't include timezone info. but on this device (Galaxy S7), the native calendar can't do Tasks, hence OpenTasks, which was suggested by DAVx5 Nov 22 22:03:58 also, I imagine if anything were to not use a particular timezone, it would be an alarm. Nov 22 22:04:18 since in general, you just want the alarm to go off at a consistent time in whatever timezone you happen to be in. Nov 22 22:07:09 indeed **** BEGIN LOGGING AT Fri Nov 22 22:21:56 2019 Nov 22 22:31:26 I love it when Android's calendar just like completely fucking fails to notify you of an upcoming event, spontaneously Nov 22 22:32:11 can you tell I have missed a few appointments because of this? >:( Nov 22 23:13:04 i want to test this on iPhone 5C in the morning. curious to see what'll happen on it **** ENDING LOGGING AT Sat Nov 23 02:59:57 2019