Profile

Cover photo
Kevin Reid
Works at Google
Attended Clarkson University
247 followers|73,260 views
AboutPostsPhotosYouTube

Stream

Kevin Reid

Shared publicly  - 
 
 
Holy crap, this musical marble machine is amazing!

Have been watching various videos of the guy building the machine over the past year.  First became aware of it when he emailed me asking questions about gearing a long time ago.
25 comments on original post
1
2
Add a comment...

Kevin Reid

Shared publicly  - 
 
 
Introduction [link]. The prepper culture begs to be taken with a grain of salt. In some ways, it has all the makings of a doomsday cult: a tribe of unkempt misfits who hoard gold bullion, study herbalism, and preach about the imminent collapse of our society. Today, we see such worries as absurd ...
1 comment on original post
1
1
Add a comment...

Kevin Reid

Shared publicly  - 
 
OK, there is no way this is not a gross abuse of the SMTP spec. But it leverages an awesome quirk of +MantisBT's email reporting plugin.

I craft a message with a particular MessageID, and in that message, I included a References header that references...that same message ID. So, the message can be said to reference itself, which, while not explicitly disallowed by the RFCs, is definitely not what you're supposed to do with it.

This message I crafted? Pass it into Mantis. Mantis will create a ticket. Pass it into Mantis again, mantis will take the second copy and add it to that existing ticket as a bugnote. Keep passing it into Mantis, and you'll keep getting notes added to that ticket.

Close that ticket, and the next time a message with that same messageID and References header shows up, and Mantis will create a new ticket, mark it as related to the old, and future messages with that same messageID and References header will get added as bugnotes to the new ticket.

So, what's the upshot? Let's say you have an NMS that emails your bugtracker whenever a particular trigger is hit. You configure things so that those messages have a messageID that's only as unique as the trigger is; future triggerings of the same condition would produce the same message ID. So, now, if you have a flapping trigger, or if your trigger goes off from time to time without a clear indication of root cause, any future messages sent by the same trigger will get filed under the same ticket, and you build a history of the events. If you think you've got it licked, you close the ticket. Next time the trigger fires, a new ticket gets opened, marked as related to the old ticket, and you can walk back the ticket history for that trigger for a historical perspective, if you wish.

And your ticket bookkeeping and cleanup gets grossly reduced, too.
5 comments on original post
1
Add a comment...

Kevin Reid

Shared publicly  - 
 
I was reviewing my internet router/modem configuration, and found this menu setting in my WiFi access point:

     IPv6: Disabled

That's silly. Fixed. Now my entire home network has IPv6. Does yours?
1
Kevin Reid's profile photoRob Meijer's profile photo
3 comments
 
There could be a different reason behind it related to an annoyance I have with my current router. Given that I only have a single IPv4 adress at home, I tend to only run sshd on my VMs using IPv6. When I first got my current router a few years back I was puzzled by the fact that while I apparently still had IPv6 connectivity, I was unable to connect to any of my VMs. Turned out my router had some kind of TCP firewall that disallowed all incoming TCP connections on IPv6.  And worse, there was no way to turn it of globally. When I queried the manufacturer about this 'bug' they claimed it was a security feature as it allowed users the same level of security that IPv4 with NAT did.  

I could imagine a similar line of reasoning would make other manufacturers opt to just turn of IPv6 by default. The idea that home users who are used to being behind NAT will run services on their machines and that they don't expect these services to be made accessible through the internet when they upgrade to a dual stack router and/or ISP.
Add a comment...

Kevin Reid

Shared publicly  - 
 
(Not “FTL is probably impossible but necessary for stories”.)
Writing science fiction – especially hard science fiction, where you're expected to keep to what modern science believes is possible, rather than inventing force fields, lightswords, faster-than-light-drives, or other accoutrements of space opera – is a demanding task.
3
Rob Meijer's profile photoKevin Reid's profile photo
2 comments
 
+Rob Meijer​ I'm tempted to disagree with your analysis, but, like I said, the topic isn't FTL.
Add a comment...
Have him in circles
247 people
Kris Kowal's profile photo
Tad Morgan (W7TAD)'s profile photo
Fred Spiessens's profile photo
andrea Bertolotti's profile photo
Zooko Wilcox-O'Hearn's profile photo
Ben Laurie's profile photo
Walter Connor's profile photo
Gleki Arxokuna's profile photo
Chris Patti's profile photo

Kevin Reid

Shared publicly  - 
 
In software-defined radio, there are well-established ways of visually representing the entire received bandwidth, to see all signals within it. Here is a way to hear them as well, with caveats.
3
Add a comment...

Kevin Reid

Shared publicly  - 
 
The Museum of English Rural Life got a surprise on Wednesday — a 155-year-old mousetrap there managed to catch a mouse: So, this retired rodent had managed to sneak past University of Reading security, exterior doors and Museum staff, and clambered its way up into our Store. Upon finding itself there it would have found …
1
Add a comment...

Kevin Reid

Shared publicly  - 
 
He said thinking about infinities gave him headaches, so I suggested he see a doctor of philosophy.
1
Add a comment...
People
Have him in circles
247 people
Kris Kowal's profile photo
Tad Morgan (W7TAD)'s profile photo
Fred Spiessens's profile photo
andrea Bertolotti's profile photo
Zooko Wilcox-O'Hearn's profile photo
Ben Laurie's profile photo
Walter Connor's profile photo
Gleki Arxokuna's profile photo
Chris Patti's profile photo
Education
  • Clarkson University
    Computer Science, 2010 - 2012
Contact Information
Home
Email
Work
Employment
  • Google
    Software Engineer, 2012 - present
  • Google
    Software Engineering Intern, 2011 - 2011
Basic Information
Gender
Male
Looking for
Friends, Dating, Networking
Relationship
Single
Other names
kpreid
Links
YouTube
Contributor to