pwmckenna

Update: forks can have their own issues.

http://programmers.stackexchange.com/revisions/179470/2

actually it turns out you can have issues on your fork, they're just disabled by default (turn them on in the fork's settings). you'll still want to update app/config.json to point to your info. feel free to open an issue if you get stuck. i'd be more than happy to walk you through it.

My blog (http://pwmckenna.net) is built on the same idea. The issue I ran into is that forks don't have their own issues, so its a bit harder to share than I originally thought (you need a seperate repo for the code, and for the issues).

Here's the source: https://github.com/pwmckenna/til

One common interpretation:

Components are "dumb", and just consume props. Views are top level Components, usually rendered by the router, that tie into your fluxy goodness.

have you thought about making this a yo generator?

It should be easy to slice and dice torrent rss feeds, and see other feeds that people have created. These aggregate feeds should themselves be consumable by feedmixalot so people can customize a feed that contains everything they want. Smart feed filters are complex to the point of irrelevance. Thoughts?

You guys are certainly correct. I'd recommend dragging the files on your bubble to the trash can if you're concerned. That will delete the torrent under the hood.

you might be right. its technically feasible to allow a browse before you install, and it might be something we look into. Given that its a demo of the api though, the simpler the better. If someone looks at it and thinks "I'll make a better version", then we're pretty happy about that as well :)

try http://paddleover.com?name=Patrick&cu=OK65EnZh0FpNPNnn&#...

have you tried to share with someone else? if you send someone a link, and they click on it, you'll be able to see each other and share freely