@shawnthroop Not sure exactly what your use case is but if I had to do this from scratch I'd: -Use different patterns for detecting and verifying a link -Use _many_ smaller patterns to build up a final pattern (ex: scheme, subdomain, domain, path, qs, etc.
The Thinking for programmers [channel9.msdn.com] presentation from Leslie Lamport is good. His point: every program should have a spec whether it's a one line comment or some TLA+ model for complex distributed systems—making the spec forces you to do required thinking.
@jeffmueller Makes sense and that definitely happens. But I also think lots of stuff gets bought and shut down _because_ it isn't independently viable. And in the alternative universe where it wouldn't have been bought, it would've shut down anyway.
@jeffmueller For you, is this sentiment mostly: - Fear that something you like will change for the worse? - Disappointment that the company isn't "independent" any more? - Something else? I'm really curious to understand this sentiment.
Developers, the App.net API now lives at https://api.app.net/ (no stream/0!). The old URLs will continue to work forever. Check out the new documentation [developers.app.net] or visit a live API endpoint: https://api.app.net/posts/27972699?include_annotations=1 #rollout