<- Previous Log Select Different Log Next Log ->  
Log from 2019-03-20:
[01:11:33] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 257 seconds)
[01:27:00] *** Joins: physkets (~physkets@unaffiliated/physkets)
[01:32:47] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[03:59:17] *** Joins: AmarokNelg (~AmarokNel@unaffiliated/amaroknelg)
[03:59:17] *** Server sets mode: +cnrt 
[04:00:02] *** Quits: Armanelgtron (~AmarokNel@unaffiliated/amaroknelg) (Ping timeout: 245 seconds)
[06:19:50] *** Quits: physkets (~physkets@unaffiliated/physkets) (Read error: Connection reset by peer)
[08:56:01] *** AmarokNelg is now known as Armanelgtron
[09:52:03] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[09:52:19] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[09:52:48] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[09:57:48] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[09:57:49] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[09:59:56] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:00:25] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:01:24] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:01:51] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:02:35] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:03:43] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:05:54] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:05:54] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:13:10] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:13:11] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:13:51] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:13:51] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:14:03] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:14:36] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:15:24] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:15:58] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:17:22] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:17:22] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:18:47] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:18:47] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:19:29] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:19:29] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:20:58] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:20:58] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:22:35] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:23:04] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:43:14] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:43:53] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:44:36] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:46:46] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Excess Flood)
[10:50:23] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[10:54:59] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 268 seconds)
[10:59:58] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[11:04:51] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 268 seconds)
[11:48:57] *** Joins: physkets (~physkets@unaffiliated/physkets)
[11:57:46] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[12:48:46] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Read error: Connection reset by peer)
[12:48:52] *** Joins: lukedashjr (~luke-jr@unaffiliated/luke-jr)
[12:53:22] *** lukedashjr is now known as luke-jr
[12:54:59] *** Joins: lukedashjr (~luke-jr@unaffiliated/luke-jr)
[12:58:55] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 246 seconds)
[12:59:39] *** lukedashjr is now known as luke-jr
[13:08:48] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 268 seconds)
[13:09:21] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[13:15:17] *** Joins: lukedashjr (~luke-jr@unaffiliated/luke-jr)
[13:16:03] *** Quits: luke-jr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 244 seconds)
[13:21:13] *** Quits: lukedashjr (~luke-jr@unaffiliated/luke-jr) (Ping timeout: 244 seconds)
[13:24:31] *** Joins: luke-jr (~luke-jr@unaffiliated/luke-jr)
[14:45:49] <Lucifer_arma> Good authors of fiction can't be trusted, for they are skilled at telling stories that aren't true
[15:27:37] *** Quits: physkets (~physkets@unaffiliated/physkets) (Quit: physkets)
[16:10:10] <Z-Man> But aren't thy only good ones telling stories that MIGHT be true given the circumstances? It's much harder to take a bit of reality and tell a lie from it that still sounds like it might me true.
[16:10:27] <Z-Man> Unless you're Trump and just don't care how believable whatever you say is.
[22:07:20] *** Joins: Z-Man- (~Z-Man@p5B326216.dip0.t-ipconnect.de)
[22:07:20] *** Quits: Z-Man (~Z-Man@p4FE3EC9A.dip0.t-ipconnect.de) (Killed (verne.freenode.net (Nickname regained by services)))
[22:07:20] *** Z-Man- is now known as Z-Man
[23:27:00] <Lucifer_arma> actually, the first rule of lying is to stick to the truth
[23:27:25] <Lucifer_arma> see, the second rule of lying is to believe it when you say it, and it's much easier to do that when there's a fair amount of verifiable truth in what you say
[23:28:32] <Lucifer_arma> it's also easier to keep the story cohesive the more truth is in it
[23:29:26] <Lucifer_arma> now, on a different note, I have a lot of different ways I can take this UI, and I'm having difficulty distinguishing between what can be done vs what should be done
[23:30:15] <Lucifer_arma> example:  I have a list of sound effects for a user to choose to use for their alarm.  If they choose more than one to use, do I always play them randomly?  Do I shuffle them and play them (in which case there are no repeats until the entire list is played)?
[23:30:26] <Lucifer_arma> do I offer a way for the user to sort them into a particular order to be played?
[23:30:59] <Lucifer_arma> ultimately, I want to have an "expert" mode where a user could potentially chain various actions in particular orders, but right now I want something that works reasonably well and can be built for android
[23:31:36] <Lucifer_arma> I think I'm going to go with shuffle for now, because that's the quickest and easiest thing to do
[23:31:53] <Lucifer_arma> next up: how do I present to the user that this is, in fact, what will be happening?

View entire month
DISCLAIMER: These logs of public chat may contain some content which may not be appropriate for all audiences. Use at your own risk.
Logs from 2006-2009 pulled from wrtlprnft
Format changes at: 2015-08-25, 2017-02-20, and 2020-03-23. Times (2015 and later) should be Eastern.


 
 
 ArmaNelgTron.tk
 © NelgTron 2014-2021. Made for . [About this site] [Credits]