boltstream
pqm
boltstream | pqm | |
---|---|---|
2 | 3 | |
1,737 | 15 | |
- | - | |
1.8 | 1.3 | |
almost 3 years ago | about 1 year ago | |
Python | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
boltstream
-
Amazon's Twitch to Cut 500 Employees, About 35% of Staff
Several years ago I cobbled together all the pieces to make a live video streaming website [1] like Twitch.tv, et al. It's impossible to actually run at any kind of scale without being an ISP or Google-scale peer. Not to mention the enormous amount of DMCAs when people are trying to stream live sports, Pay-per-view, etc.
It was fun to play with it for a couple months. But there's no business here. Twitch.tv is also finding that out.
[1] https://github.com/benwilber/boltstream
-
Ask HN: Show your failed projects and share a lesson you learned
I built Boltstream [0] over the course of a couple years and got burned out. I wouldn't say it was actually a failed project because in the back of my mind I never really had any intention of trying to turn it into a Twitch/YouTube/Facebook Live competitor anyway. And it's proven to be somewhat popular on Github. The project was fun to build and learn about but ultimately it was impossible to actually run it as a consumer-facing website. The problems were never the actual software/video streaming tech, but rather the extreme bandwidth costs of live video streaming, and the content itself. I launched it several times under different site names/products and it always just turned into a cesspool of pirate streaming live sports and other copyrighted content. The DMCA notices were regular, but were never really that onerous to deal with. Just turn the stream off, ban the account, and then reply to the email. But it just got too annoying. I built a little mobile web app so I could just do it from my phone while I was out at dinner. After awhile I just decided that it was time to give it to someone else to play with. So I did a big code dump on Github and haven't touched it since.
I've actually started working on it a little bit more recently since it seems that "self hosted video streaming" is still pretty in-demand. I'm probably not going to be spending too much time on the actual features and functionality since that's pretty much done at this point. Mostly just packaging it up so it's easier for people to run it themselves and hack on it.
[0] https://github.com/benwilber/boltstream
pqm
- A better/faster JavaScript library for physical math
-
Ask HN: Show your failed projects and share a lesson you learned
I made a spreadsheet add-on similar to the pint library for python (dimensional analysis) based on my own open source JS library (https://github.com/GhostWrench/pqm). Website is still up: https://ghostwrench.net/convertplus.html.
To me it seemed like the perfect way to get a solo app up and running because Google was going to run all the sever stuff and I could just cash in. The app never really got off the ground and by the time I realized that Big G really doesn’t want to make it easy for any schmuck to run a profit generating app using their servers and their technology and it wasn’t worth the maintenance effort to keep up with the constant requests to update the app. I think it is no longer available on the GSuite store as of a few months ago. I think my biggest mistakes were as follows:
1) I needed a business/marketing oriented co-founder. I underestimated how difficult that job is and overestimated my ability to do it.
2) I wanted to charge too much for the app. I didn’t want to undersell myself and get caught in a trap of not making enough to keep up with maintenance. I went too far the other way. I think maybe a $50-$60 on time charge would have been appropriate, instead of requiring a subscription. This is an easy fix, but I would had to re-do my marketing effort and see #1
3) Built before I tested the market. I convinced myself that just asking a few of my engineering friend would use it was enough. Again, this is probably a symptom of #1
4) I was mentally unprepared to deal with failure and I lost motivation to keep working on the project when things didn’t go as I expected.
5) I underestimated how much people actually use spreasheet add-ons. There really isn’t a thriving market and most of the really popular apps are a utility attached to another popular standalone project.
6) Probably should have targeted Excel rather than Sheets, because the market is simply bigger.
I think if the stars align, I would like to give this project another go. I don’t think it has totally failed rather than just gone dormant, but I need a better strategy for round 2!
-
GNU Units
There are heaps of libraries for all languages because it is a fairly fun and straight forward project. I personally created this one because I was frustrated with how slow and clunky the existing javascript libraries were:
https://github.com/GhostWrench/pqm
Also, I open sourced just the unit database (in JSON format) for anyone interested in making their own version:
https://github.com/GhostWrench/unitdb
What are some alternatives?
rtti
unix-v6 - UNIX 6th Edition Kernel Source Code
Flythrough.Space - Top down space captain RPG
Ruby Units - A unit handling library for ruby
Marten - .NET Transactional Document DB and Event Store on PostgreSQL
lasercrabs - Abandoned hybrid singleplayer/multiplayer shooter project formerly known as DECEIVER
Unitful.jl - Physical quantities with arbitrary units
gnu-units - GNU Units (mirror)
uom-se - JSR 363 - Implementation for Java SE 8