501–510 of 617 posts
In 2013, I started https://webtorrent.io the first torrent client that runs in a web browser. It’s open source here: https://github.com/webtorrent I built it to make torrent technology more accessible to the masses. We’re still actively building it and we even have a slick desktop app that uses the same engine for streaming. WebTorrent also powers https://wormhole.app an end-to-end encrypted file sending service that…
- https://github.com/rcarmo/pngcanvas because there was nothing similar that ran on Google App Engine
- https://github.com/rcarmo/imapbackup because I needed a migration tool from Sun IMS to Exchange
- https://github.com/rcarmo/rss2imap because it helped me survive well beyond Google Reader for a long time
- https://github.com/piku/piku because it enabled me to automate away 99% of my non-Docker deployments and is a lot more fun than Kubernetes on low-end standalone boxes
There’s also my blog engine (https://github.com/rcarmo/sushy), but that is in a state of flux right now and I haven’t published the new source yet.
The problem I found with most existing providers is they require you to create an account and often subscribe before you can use their services. For a quick test that's excessive overhead.
Until recently I was using prism[1] to run the mock server locally, but it's very limited when it comes to configuration and you have to install and run it locally, which again it's an unnecessary overhead when you want to run a simple test.
I've been using microapis.io for a few months now with my clients and it's proving a life saver to run integration tests and to help the frontend and the backend teams to work separately while ensuring they both comply with the same API specification.
I created https://microapis.io to make it easier to launch API mock servers in the cloud with one click, no signup or login required. The problem I found with most existing providers is they require you to create an account and often subscribe before you can use their services. For a quick test that's excessive overhead. Until recently I was using prism[1] to run the mock server locally, but it's very limited when it…
[1]: https://github.com/dukeofharen/httplaceholder
Edit: after looking through the comments, I found some 5 other HTTP mock server implementations XD Not that it's bad, just seems to be a problem that is tackled very often.
I tend to worry about criticism and whether my things are actually useful enough for others to be worth the trouble. So I've never actually published anything. When I was a teenager I made a bunch of games for which I created level editors and the like. This was before there were free alternatives that I knew of which fit my needs. When I started with graphics programming I made a library with OpenGL helpers for sett…
I encourage you to publish some of the things you’ve worked on. One way to reduce some of the concerns you mentioned would be to publish it using one or more anonymous accounts. So long as your readmes have reasonable keywords, someone may just stumble on your project. If they don’t like it well it still won’t be attributed to you and you don’t even have to respond. Either way, the practice of releasing and dealing w…
At work I routinely make things which I know are used by millions of people and I've never had a problem with that. In fact, I'm quite proud of my work. And I've long since gotten over worrying about others reading my code. I'm also a big proponent of code reviews.
But the code being public still feels really scary, even though there's so much worse code out there which doesn't get sneered at.
Last year I built Recut[0], a native Mac app that helps speed up video editing by automating the rough-cut process. It finds silence, gaps, and pauses and removes them, creating a cut list that you can import into editors like ScreenFlow, Final Cut, Premiere and Resolve. Here’s the Show HN [1] from a couple months ago. I built it because I was making screencasts and cutting out silence + mistakes was 90% of my editin…
In 2013, I started https://webtorrent.io the first torrent client that runs in a web browser. It’s open source here: https://github.com/webtorrent I built it to make torrent technology more accessible to the masses. We’re still actively building it and we even have a slick desktop app that uses the same engine for streaming. WebTorrent also powers https://wormhole.app an end-to-end encrypted file sending service that…
I wanted to make a drop-in replacement for code review on GitHub that made reviews much more structured and focused while not requiring nearly as much clicking around and loading.
I built this over the last year or so, mostly on nights and weekends but I do hope it can become a full time thing eventually.
(Since we're talking about building here I'll mention that the app is 100% Vue 2 backed by Firebase. It's such a lovely dev stack and never keeps me up at night)