beef-wellington

Activity Graph

Page 1 of 1

2015-09-04

[18:06:01] beef-wellington: has joined #ruby
[21:12:55] beef-wellington: Ping timeout: 272 seconds

2015-08-24

[00:35:00] beef-wellington: has joined #ruby
[01:40:07] beef-wellington: Ping timeout: 240 seconds
[14:29:37] beef-wellington: has joined #ruby
[19:59:05] beef-wellington: Ping timeout: 244 seconds

2015-08-23

[14:16:10] beef-wellington: has joined #ruby
[14:52:21] beef-wellington: Ping timeout: 252 seconds

2015-08-22

[03:58:48] beef-wellington: has joined #ruby
[04:19:12] beef-wellington: Ping timeout: 252 seconds
[21:32:01] beef-wellington: has joined #ruby
[21:39:34] beef-wellington: Ping timeout: 256 seconds

2015-08-21

[21:55:05] beef-wellington: has joined #ruby
[22:00:43] beef-wellington: Ping timeout: 260 seconds

2015-08-17

[13:46:36] beef-wellington: has joined #ruby
[16:18:31] beef-wellington: Ping timeout: 240 seconds

2015-08-14

[18:46:00] beef-wellington: has joined #ruby
[21:20:07] beef-wellington: Ping timeout: 240 seconds

2015-08-05

[01:11:30] beef-wellington: has joined #ruby
[01:50:52] beef-wellington: Ping timeout: 250 seconds
[14:03:45] beef-wellington: has joined #ruby
[17:35:17] beef-wellington: Quit: WeeChat 1.2

2015-08-04

[17:32:48] beef-wellington: has joined #ruby
[21:58:24] beef-wellington: Ping timeout: 244 seconds

2015-07-30

[14:30:35] beef-wellington: has joined #ruby
[18:31:57] beef-wellington: Ping timeout: 250 seconds

2015-07-29

[14:06:07] beef-wellington: has joined #ruby
[22:34:16] beef-wellington: Ping timeout: 252 seconds

2015-07-28

[18:29:56] beef-wellington: has joined #ruby
[22:07:59] beef-wellington: Ping timeout: 244 seconds

2015-07-27

[17:08:47] beef-wellington: has joined #ruby
[21:45:30] beef-wellington: Ping timeout: 265 seconds

2015-07-15

[14:02:40] beef-wellington: has joined #ruby
[16:18:56] beef-wellington: Ping timeout: 246 seconds
[16:45:01] beef-wellington: has joined #ruby
[18:37:30] beef-wellington: Ping timeout: 256 seconds

2015-07-14

[14:00:21] beef-wellington: has joined #ruby
[21:50:58] beef-wellington: Ping timeout: 255 seconds

2015-07-13

[10:08:59] beef-wellington: has joined #ruby
[10:13:35] beef-wellington: Ping timeout: 248 seconds
[13:56:27] beef-wellington: has joined #ruby
[21:26:40] beef-wellington: Ping timeout: 255 seconds
[22:06:58] beef-wellington: has joined #ruby
[22:11:40] beef-wellington: Ping timeout: 252 seconds

2015-07-12

[03:03:17] beef-wellington: has joined #ruby
[04:29:18] beef-wellington: Ping timeout: 240 seconds
[18:21:07] beef-wellington: has joined #ruby
[18:27:36] beef-wellington: Ping timeout: 256 seconds

2015-07-11

[00:26:17] beef-wellington: has joined #ruby
[02:33:44] beef-wellington: Ping timeout: 256 seconds
[13:47:23] beef-wellington: has joined #ruby
[14:29:42] beef-wellington: Ping timeout: 256 seconds
[18:15:26] beef-wellington: has joined #ruby
[18:20:04] beef-wellington: Ping timeout: 256 seconds
[21:58:55] beef-wellington: has joined #ruby
[22:15:14] beef-wellington: Ping timeout: 256 seconds

2015-07-10

[21:24:27] beef-wellington: has joined #ruby
[21:38:18] beef-wellington: Ping timeout: 264 seconds

2014-10-24

[17:53:11] beef-wellington: Is there a way to force rails console to be 100% read-only so that devs can dig into issues to gather data without any fear of modifying production data accidentally?