reconbot

They don’t say as much but it appears they’ve been dropped by their payment processor. I have trouble believing they’d invalidate every single card with 5 days notice if they had a choice.

I love these proposals and while it probably makes sense for me to learn more about the languages that already implement it there's no denying that having them in JS is a win. =)

I wish I knew about python's [itertools](https://docs.python.org/3/library/itertools.html) before I started making [streaming-iterables](https://www.npmjs.com/package/streaming-iterables#api) for example.

I'm starting to use privacy.com with all my online accounts. If I really have trouble leaving deleting the vendor locked credit card I used to sign up is an easy way to go that gets the job done.

If you run `npm install` again it does detect the conflict and resolve it. https://docs.npmjs.com/files/package-locks#resolving-lockfil... But in practice I haven't found any changes that have been untenable to understand with a diff.

I had no idea what dragonofly is, it looks to be an experimental BSD based OS https://www.dragonflybsd.org/release54/

    DragonFly belongs to the same class of operating systems
    as other BSD-derived systems and Linux. It is based on the
    same UNIX ideals and APIs and shares ancestor code with
    other BSD operating systems. DragonFly provides an
    opportunity for the BSD base to grow in an entirely
    different direction from the one taken in the FreeBSD,
    NetBSD, and OpenBSD series.
    
    DragonFly includes many useful features that differentiate
    it from other operating systems in the same class.

in the real sense of the word

I was having an argument over 1password's 2fa support not being a second factor. (I don't think it is.) However, it is so much safer than not using 2fa. In similar terms U2F is amazing and keeps you from being phished and has a great challenge/response protocol, if that was implemented in 1password (or browsers themselves thank you!) we'd all be a lot safer than not using it at all.

In 2018 I'm using an app to take screenshots of QR codes to generate one time codes. It's a sad state of the art, we need to do better.

Faked and discovered to include fake reactions that were then removed, are different situations. Mark has been producing high quality educational and entertaining videos that encourage kids to get into science. I have personally watched kids go nuts over his Fluidized air bed experiments, and convince their parents to try it out. https://www.youtube.com/watch?v=My4RA5I0FKs

It sucks there was fake content in there, but the device was real and the fake actions removed.

This is really awesome. For NYC what data is actually real time?

yes!

I would love to, but not all node versions and not all streams support async iteration yet! Also theres is a lot of utility to some of the stream types in bluestream. Concurrency for one thing. I've been working on an async iterator version of this but haven't yet started using it in production yet.

https://github.com/reconbot/streaming-iterables

Hi I built this little stream processing library so I could write things like;

  const stats = await pipe(
    Nodes.scan({ fields: true }),
    map(generateStats),
    tap(() => count++),
    reduce(mergeGraphStats, {})
  )

Hope you find it as useful as we do.

Nope, appsync came out a long time after we were in production and while it's very powerful, it's would require a full rewrite of our application. It's an application service/framework upon itself.

The Bustle stack looks like Redis/Elasticsearch => NodeJS Lambda GraphQL API layer => (sometimes api gateway) => NodeJS lambda render layer => api gateway => CDN. We're working towards removing all the api gateway usage if possible with smarter CDNs like cloudflare workers and Lambda at edge, but it's not currently possible.

This setup gets us an average of 70ms api response time and less than 200ms worst case rendering time. Higher than 90% of cache misses never gets the worst case as we can serve stale content in those cases. Lots of room for improvement too. =)

This was an April fools joke but hit's every good policy idea NYC could do spot on. https://pedestrianobservations.com/2018/04/01/new-york-area-...

From a local controlling agency, from unifying our commuter rails, from joining with the path. All these things would be good for the city and people who live here but I cry because I'll never see a sliver of it in my lifetime.

Easy to avoid. Use Lyft, Use Juno, Use anything else and compare prices.

I've built a cloudwatch metrics stack that reads out of lambda's logs. There's no other way to get data out of your lambda for "free". XRAY is an option but not everything you'd want.

They don't seem to offer rights or license checking in their apis. Am I missing something?

Sure lets trust a for profit cooperation. Their motives could be anything really?

I think destroying competition is something wrong. "Trust us completely forever while we ruin your ability to function without us" isn't something anyone should everyone should have to do. The tax breaks offered to them for their new headquarters (that could "pay for themselves" in 10-20 years and will bring "lots of jobs") are insane, and they don't come close to completely controlling all the markets they operate in. I shudder to imagine what they'll look like when they do. But are they abusing anything now? Lets look into their lobbying, their warehouse temporary workers, their deals with the USPS, and what it's like to be one of their delivery drivers. It sucks to work for Amazon.

I know when trying to bring "Amazon Fresh" to NYC, they failed because the only terms they'd offer truck drivers were crazy high risk and low pay and NYC is a big enough market they could collectively resist. That's not going to last forever.

I'm not against innovation, I'm not against your margin being my opportunity, I'm against living in an Amazon controlled world.

I found it lowered our server cost incredibly for a high volume read heavy site. It allowed us to scale in response to increased traffic (not instantly that's a lie, spikes in the thousands of requests a second are not handled well, but over a few minutes it catches up without issue) and not have to provision and spin up servers. We were constantly over provisioned before and now it's a much lower but moving margin.

It can fold if you indent the text, not ideal but hardly a dealbreaker. I'm happy to say the VS Code is how I started with orgmode and I'm excited to see what's missing/coming, it's great!

They seem to be using https://www.eternum.io to "pin" the file (keep a copy of the file alive). Since eternum is a paid service they might unpin after a while but it's up to them. If they didn't do that, the file might only be available as long as your browser is open.

The speakers in this video series give great overviews of their products and their uses. This lecture series reminds me of an in depth meetup, which is nice.

It's weird and a little tone deaf but a common older brand of humor. The speakers (in general, I only skimmed a few of the videos) don't seem to share it.

Very cool, also very cool it speaks git. Kinda like they made a specialized distributed closed source database.

I was able to get in on the kickstarter and while I'm far from the target market I've found this a lot fun to play with. It's like an arduino with decent bluetooth and a tiny form factor.

I know some people on the team, they're great. But I also have a long history of working with microcontrollers in a semi educational setting (http://nodebots.io) and these are by far the least frustrating way to use wireless anything I've come across.

Some of the links are bad but this is a great list of things to keep in mind when seeing where your work is with regards to security.

Does anyone have any favorite tools for visualizing very large graphs?

I'm thinking 200k nodes and 2 million edges? Graphviz segfaults graphs a fraction of the size and even at that scale a node by node representation isn't super helpful without being able to zoom out and look for patterns.

IPFS solves the addressability, availability and decentralized storage for this kind of thing.

I'm not so sure about that. They change up things a lot. Search is only part of the equation however, people can still buy an add to show you anything they like. So these practices aren't going away, they're just pushed into an arbitrage situation.

We learned from Java and Google that you can't patent and API. It's not forked from React it's an alternative.

We still use Ember and fastboot on a few applications but it's being replaced for the user side of bustle. I believe we did it because we were able to get faster and smaller server side renders and a smaller js payload. I spend more on the infrastructure side so I can't speak to the exact reasonings.