Hacker News Reader

wesleytoddon An off-grid social network

Also, because Paul has awesome projects, and deserves some attention when a project of his makes it to the top of HN but doesn't even mention him, he is working on a browser for the distributed web called Beaker (I am using it to write this now), and it is awesome.

https://github.com/beakerbrowser/beaker

wesleytoddon An off-grid social network

Since the author didnt mention it, the original creator of the patchwork project is https://github.com/pfrazee

When I used it, which admitedly was a long time ago now, the biggest setback was lack of cross device identities. So I ended up having two accounts with two feeds, `wesAtWork` and `wes`. Maybe they have solved this by now.

ps. Does patchwork still have the little gif maker? Because that was a super fun feature.

wesleytoddon JavaScript-Stack-from-Scratch tutorial V2 released

The need for things like this often make me sad, despite recognizing/accepting how complicated the landscape can be.

I almost always think tutorials like this make things more complicated than they need to be. Usually by including too many pieces under the "guise" that it is the "modern JavaScript stack" when many projects/companies often do not have nearly this many pieces.

wesleytoddon Show HN: Q8, an In-Browser VM for Learning and Visualizing Bytecode Programming

Really neat! Is there a list of the full instruction set somewhere?

wesleytoddon Let's start using DuckDuckGo more often

Already have been!!!

Started using Beaker Browser as my main browser, DDG as my search, and am working on moving the rest of my life off google (read: gmail).

Also have been messing with doing more work on a raspi tablet rigged with a bluetooth keyboard/trackpad combo.

wesleytoddon Insecam: Large Directory of Unsecure Cameras

You are probaly referring to https://www.yubico.com/

I just bought one the other day for personal use, pretty cheap, cant say more becuase I have yet to receive it, but I have high hopes.

wesleytoddon Beaker – An experimental P2P browser

> No, thankfully! I've been working with GitHub via PRs. They added the feature most needed so far, proper process-level sandboxing, so hopefully a fork won't be necessary.

Do you have a link to the issue where this was fixed/discussed? I searched for it last week and couldn't find it.

wesleytoddon DeepMind and Blizzard to release StarCraft II as an AI research environment

I would probably watch that

wesleytoddon Apple says no fun allowed on the Touch Bar

"Don't be creative with this new tool we made for creative people" -Apple

Typical Apple restricting the ecosystem. Guess we all knew what we were getting ourselves into.

wesleytoddon State-Driven Routing with React, Redux, Selectors

Agreed, but it is still smaller than the competitors. I would love to reduce it even more, but there is very little concern for file size in express' router since it is server side.

Also, I believe it can be made smaller with one of the other bundlers. Browserify is not the most size conscious choice, it just happens to be the one I have the most experience with.

wesleytoddon State-Driven Routing with React, Redux, Selectors

Also, forgot to mention, nighthawk also solves the edge cases mentioned toward the end:

* ctrl-clicking to open a new tab

* shift-clicking to open a new window

* alt-clicking

* non-left-clicking

* target attribute in <a>

* mailto: in href

wesleytoddon State-Driven Routing with React, Redux, Selectors

> Anybody can write some HTML with some anchor tags and tie it to some routes declared in a server-side routing file. The back button will work. History will work. Refresh will work. Copy-and-pasting the URL into an email will work. It's so easy that even I can do it.

The solution I use[1], and disclaimer also wrote, was targeted directly at server rendered SPA's to follow closely with these ideals. Layers over native anchor tags, just barebones handles the link clicking and uses Express routing which is obviously back end compatible.

[1] https://github.com/wesleytodd/nighthawk

wesleytoddon Why I Don't Use React Router

I guess I just assumed everyone understands that no team will have the ability to cover all your needs. So you actually need to judge when your team cant deliver, then pick the dependency to pull in.

wesleytoddon Why I Don't Use React Router

Yep, this is a thing I push with my team all the time. Always vet your deps. In the long run is is WAY worth it. In the short run the cost is rather minimal unless you have devs that cannot actually deliver on the needs the dependency covers.

wesleytoddon React Router v4 FAQ

If you have a hammer everything looks like a nail?

wesleytoddon React Router v4 FAQ

See above: https://news.ycombinator.com/item?id=12514798

wesleytoddon React Router v4 FAQ

If you are interested, that link I posted above, Nighthawk, actually is a port of Page.js for its dom and pushstate handling wrapping the Express router, so it is just as simple. Here is the bulk of the code taken from page.js: https://github.com/wesleytodd/intercept-link-clicks/blob/mas...

wesleytoddon React Router v4 FAQ

That middleware is actually just a isomorphic render method, which uses express's render on the backend and react's render on the FE.

So that middleware actually requires a solution similar to what Nighthawk provides. The point was to keep the routing and the rendering separate, unlike what react router does.

wesleytoddon React Router v4 FAQ

> So what benefit would I get from authoring the logic of URL-change handlers in JSX?

I don't get it either. I thought we were over describing program behavior in XML?

wesleytoddon React Router v4 FAQ

https://github.com/wesleytodd/nighthawk

My team uses this, we built it in response to most of us not liking the React Router methodology, and already using Express, it seemed like a good route.

wesleytoddon React Router v4 FAQ

https://github.com/wesleytodd/nighthawk

^^ This is the one we developed on my team. No view coupling, uses industry standard underlying components (Express Router), and layers on top of existing applications seamlessly (aka, no view tie in points, just anchor tags).

wesleytoddon React Router v4 FAQ

We did something similar that uses the Express router: https://github.com/wesleytodd/nighthawk

The one thing we didn't do was layer on top of a flux solution. Seemed more future proof to not tie to anything other than a routing style. If you wanted to do that with our solution it would be as simple as writing an action to do the url change.

wesleytoddon React Router v4 FAQ

My team uses this: https://github.com/wesleytodd/nighthawk

Basically it is just the Express router wrapped with logic from Page.js for catching link clicks and what not.

We do universal rendering with a simple middleware and share all our middleware, rendering and route definitions on both the FE and BE.

wesleytoddon React Router v4 FAQ

If you are interested, this is what my team uses and it works REALLY well for us. It uses the standalone Express 5.0 router, so any pattern that works in Express works here.

https://github.com/wesleytodd/nighthawk

wesleytoddon React Router v4 FAQ

This is one of the major reasons I try to stick with more well established libraries when I can. For example, when choosing our teams universal routing solution, I used the Express router instead of going with the NEW SHINY react router.

Of course this did mean wrapping it for use on the FE, but that was as easy as copying code form Page.js (another old school project).

https://github.com/wesleytodd/nighthawk

wesleytoddon The commit that broke your build

This is the thing that should NEVER be done: https://github.com/jsdoc3/jsdoc/blob/master/package.json#L26

wesleytoddon Ask HN: How do you handle DDoS attacks?

I guess some people just really hate kittens :)

https://www.stream.me/kittendorm

wesleytoddon Ask HN: How do you handle DDoS attacks?

https://www.stream.me/

We have some controversial users...

wesleytoddon Ask HN: How do you handle DDoS attacks?

One other thing to add:

If they attackers are persistent, there is really no way to guarantee zero down time. THEY WILL FIND A WAY. Just make sure your stake holders know you are doing everything in your power to resolve the issues, and then actually do those things.

An anecdote:

We had been seeing DDOS attacks for a few weeks, so we had most everything locked down and working. But then suddenly one of the most important parts of our site started going down under load. That part is a real time chat system. We looked for which chat room had the load and it was one which did not require a user be registered. We switched the room into registered users only mode and thought we had solved it.

About 5 minutes later the attack came back with all registered users. We were amazed, becuase there is no way the attackers could have registered that many accounts in 5 minutes because of our rate limiting on that. Turns out that they had spend the past week or so registering users in case they needed them :)

wesleytoddon Ask HN: How do you handle DDoS attacks?

My startup's site gets DDOS'd about once a week. We have seen a huge range of attacks from UDP floods, to wordpress pingback attacks, to directed attacks on our services.

We have many layers of protection:

* We run iptables and an api we wrote on our ingest servers. We run failtoban on a separate set of servers. When fail2ban sees something, we have it hit the api and add the iptables rules. This offloads the cpu of failtoban from our ingest servers.

* We block groups of known hosting company IP blocks, like digital ocean and linode. These were common sources of attacks.

* Our services all have rate limits which we throttle based on IP

* We have monitoring and auto-scaling which responds pretty quickly when needed. And has service level granularity.

* Recently moved behind cloudflare because google cloud did not protect us from attacks like the UDP floods which didn't even reach our servers.

EDIT: formatting