Jailbird

Thanks for the link. I had never looked into it but had always just assumed it was fiction in the first place.

That is decidedly abnormal in the NYC area. Eat as you wish, but you may find it more enjoyable our way!

Perhaps all that will be implemented is character cell windowing systems.

And Doom. Definitely Doom.

Did you find anything for the golang part?

OK, I was hoping others had perhaps found something I'd not, even though I'd tried to read whatever documentation I could. Thanks, though.

One nice thing the Asus firmware has is nice grouping of devices for family members which can show monitoring, overall usage and even quick shutoff controls if necessary. Does the Unifi stuff have the equivalent, even if a huge pain to set up?

That could enable collusion between remaining players and defeated players, possibly defeated on purpose.

Ah - yep, I've betrayed I'm not as familiar with gorilla as I might like to be. Yet.

The way you've described things is how apps I'm familiar with do it (the latter way.) Thanks for clarifying.

without reference to this project -

Perhaps you meant storing all session data is a bad idea versus just an ID? (If so, I'm with you)

If not - how would you identify an authenticated user? Or, how would you look up all their relevant session data in the DB?

Really? In my experience, across (software/tech) in multiple industries - people (work friends, and work friends who you keep as real friends) help each other out if they're leaving (again, assuming we think well of each other and the references are honest) We don't assume interviewing equal disloyalty. A fair bit of caution is required, of course - but I see this happen all the time. Heck, I've had executives who will help you if want to leave (again - it's not disloyal), and I've carried that same approach to those who reported to me.

This may seem obvious - but yes, consult others before using them as a reference. At a minimum, you'll want to know they're happy to give you a good reference. One would hope you've developed a strong enough relationship with some colleagues as humans (i.e. beyond the confines of the "employee" relationship.) Humans don't always stay at one company forever.

Trust comes first - the rest follows rather easily.

Since reading Dune, I have been waiting for mankind to get around to making this. It was just a matter of time.

It's guides, all the way down.

A nice read -

Just a minor nit: s/peaked/piqued/

-A

Same issue here but I have set a reminder for every 2 weeks and luckily haven't missed.

I have my parents' old router set to use this - and really have no good way out.

I guess I give 'em money. Oh well.

On the assumption that aside from publishing some useful information, the blog post is also meant to drive awareness for Periscope...

even a small landing page with some expected features or more information about the product-to-be would be a good idea.

(I saw the one-liner at the bottom of the post but would suggest a bit more to pique the interest of more people. If I missed it, my apologies.)

Any metrics you can share about the team size, any esoteric skill sets found to be crucial, or overall cost? Some sense for those who wonder "what would it take to create or recreate something like this?"

That counts as ageist for me.

I guess I was thinking it'd be used for much more than just jQuery, and fast. Then for anything that any site wanted cached, some other site could essentially grab it if all they had was the hash.

Would this allow some kind of mine-by-SHA cross-site attacks? (sidenote: I've not thought this through, this is just an off-the-cuff thought.)