133 karma · joined March 19, 2009
https://akl.io/
https://www.seattletimes.com/business/technology/google-plan...
Even if only one person (or no persons) ever log in, the machine is capable of running processes under multiple users and it is best practice to maintain this so that all users do not share the same level of privilege.
In the ideal case, you might have a quality man page that provides usage information and links to more detailed documentation (that would include tutorials, implementation info, etc.) on the web somewhere.
My anecdotal experiences with GS4 vs my Fitbit One shows the Fitbit One to be superior, but I'm more likely to forget my Fitbit than I am to forget my phone.
It'd probably go a long way if you guys considered making an easily-discoverable security page with information on who to contact, how you prefer that contact to take place and how long they should expect to have to wait to hear back from you.
If your terminal is broken, there are plenty of ways (reset, stty sane, whatever) to fix that. I'm also not sure why having an extra binary on my system is a good safety guard against a broken keyboard.
The ajax term case is valid I guess, though I'm not sure how common that is. I was in a case like that a year or so ago and ended up using cat and sed to get the thing back on the network.
I think I'd have a different opinion if they'd bothered to reply to any of my multiple emails to them at the time.
https://www.facebook.com/jonathanscard/posts/176232239115101
The second link shows this as a formerly valid command:
pr <"sort input"< >opr>
Ouch!http://www.reddit.com/r/apple/comments/eaqm5/its_this_kinda_...
The points about directing people to their store over other stores and minimizing the secondary market are probably the main reasoning behind offering engraving.
https://www.cloudkick.com/accounts/signup/developer/
CK sent me a text message as soon as my host went down earlier, which gave me time to file the ticket against Linode.
Only caveat - they don't provide a signed RPM, which can cause some administrative hardship for linux users using rpm-based distributions (most of the yum operations require you to add an extra cli option to allow working with unsigned rpm's), but it's a minor complaint given that their agent isn't mandatory and doesn't need a lot of updates.
Certainly not the best protocol ever invented, but I have fond memories of figuring out how it worked.
Running sshd on a nonstandard port isn't in itself a bad idea (other than the potential difficulty of logging into the server later if you forget the port or something), but it shouldn't be considered a strong security measure at all.
(or so this book said: http://www.amazon.com/amazon-com-Inside-Revolutionary-Busine...)