https://github.com/erroneousboat/slack-term seems more than sufficient to me, and hackable if I find an itch to scratch...
Better yet, would anyone here pay for development of a self-hosted IRC or XMPP gateway to Slack? :P
44 karma · joined June 29, 2012
https://github.com/erroneousboat/slack-term seems more than sufficient to me, and hackable if I find an itch to scratch...
Better yet, would anyone here pay for development of a self-hosted IRC or XMPP gateway to Slack? :P
Someone needs to teach the next generation about ABI compatibility...
Just guestimating, I would need 11 or 12 27" screens to fully utilize the area I can see without moving my head. With gentle neck motion included I think that number triples or quadruples.
My opinion: ...and it should be both disclosed and opt-in.
In case anyone is unaware, LINQ lets you represent queries as a series of function calls which it represents as a series of Expression objects and an in-memory AST.
Maybe you can get away with this for a small scale deployment, but "as long as you can" sends a bit too mixed of a message. You should only defer a service discovery implementation until you get to the point where you have more than one read path in your stack.
IMO, as soon as you go from load balancer -> app -> cache -> database to having a services layer you should start thinking service discovery.
The simplest bandaid is to leverage DNS as much as possible until you get even bigger, and use static CNAMEs.
Nice clean interface, reasonably quick to use.
Doesn't work with 1password.
HTTPS isn't the default, and when requested gives a cert failure (representing *.onmodulus.net)
Email notification should be opt-in? Also should have a toggle for product notifications.
When I click on someone like http://chapp.is/people/hayk/activity the profile link takes me to my profile instead of theirs.
All in all, I'm looking forward to watching this service grow! (p.s. I suggest looking into PostgreSQL 9.3 as a backup plan to Mongo)
After I re-released it on the Chrome Store, now I get emails trying to buy "my" extension from me.
Red-black deploys via AMI changes are one way for sure, but those seem to be usually done via separate scaling groups entirely. Netflix has a lot of automation around this (see Asgard and AMInator)
I assume this is a reference to the charge per 1M I/O requests on EBS.
IMO, the biggest concern for an employee is dilution. Sometimes this happens in non-obvious ways, like on exit what happens to undistributed shares allocated to the employee grant pool?
now I know that using VMs / vagrant is critical to sane server orchestration development workflows though, so there's that.