mjstahl

Yep sure is. Just call the number. Everyone gets 60 mins for free.

Service: https://hellonotes.net

Try it out: tel://+14355629028

Example output: https://lnk.hn/g8tx95K

https://www.cbs46.com/news/lawmakers-hear-bombshell-allegati...

Why did you create Elementree?

Elementree is really just an exercise in constraint. I am tired of spending my time in front-end framework documentation. I wanted something that didn't rely on odd templating syntax, proprietary data shapes, multitudes of library imports. Therefore I needed to create something where the entirety of the library could be held in my head, which I might note, hasn't had a memory upgrade in some time. I wanted a library to celebrate the code of the problem domain as opposed to the framework.

Why local view state?

Local state jives with my brain. I have never been fearful of encapsulating state with an object and subsequently mutating that state. I understand the pitfalls and I do my best to work around them when they present themselves. I view local state vs a system like flux/redux a lot like I view procedural vs functional programming. My brain works better with recipes than mathematics, just like it works better with state mutations than reducers.

Why Proxies?

Proxies gives Elementree objects the appearance of everyday JavaScript objects and yet perform specific semantics when mutated. This is just another case of doing my best to decrease the API foot-print, making the entire library easier to process and quickly be productive with.

Why not use a templating engine like lit-html?

I was exceptionally excited about lit-html when I originally saw it. But over time additional 'syntax' has made its way into the library for things like boolean attributes and event listeners. Don't get me wrong, the people working on that project have a whole lot more time and brains than I do, so I am sure it is for good reason. But I went with nanohtml because it didn't do anything special. It makes all Elementree's template look just like HTML with interpolated values. It is the right tool to meet the design goals of Elementree.

I got tired of having to remember how I set a project up each time, so I figured I would turn it in to its own repo.

It is opinionated and doesn't cover every need, but I figured this would save some time for others making their way into ES6.

Feel free to offer any feedback or pull requests.

The current link points to a page that doesn't exist.

Here is the updated URL: https://www.voxxed.com/blog/2015/07/akka-streams-and-http-1-...

I would also recommend the follow-up book entitled "The Design of Design" also by Frederick Brooks

From what I have been able to determine.. the "Searching... " and blocking of the browser (tab) is because that site does not exist in punkSPIDER's index. Eventually the site stops blocking the browser and "No results found!" is displayed.

From the article the only use case of punkSPIDER mentioned explicitly is where a consumer could use the site to determine how many "known" vulnerabilities exist at that site before they go entering sensitive information.

http://thomas.loc.gov/cgi-bin/bdquery/z?d113:h.r.2495:

http://thomas.loc.gov/cgi-bin/bdquery/z?d113:HR02495:@@@L&su...

To see the earlier work by Rob Pike on the ideas that would eventually turn into golang take a look at this paper:

http://www.cs.bell-labs.com/who/rsc/thread/newsquimpl.pdf

A good overview (of CSP) document is written by Russ Cox:

http://swtch.com/~rsc/thread/

Both the above articles are more focused on implementation as opposed to theory.

The IRS document used as source material for this article can be found at:

http://www.irs.gov/pub/irs-drop/n-14-21.pdf

MIT's introductory engineering course used to teach Scheme to the students using the excellent SICP text. I believe they now teach their beginning students Java or Python. I am not sure if there are blog posts or papers detailing the benefits of using Scheme in the class room.

I don't know how I personally feel about HFT. I don't have a high enough view of the system as a whole to make a determination if HFT is or will be a problem.

But the mention (http://www.cnbc.com/id/100809395) of Reuters selling data to customers 2 seconds before the conference calls (which occurr 5 minutes before the public receives the data) unsettles me a bit. Two seconds isn't a long time except when you consider that HFT operates in milli, micro, or maybe even nano seconds.

I am not sure whether I would go as far as to consider it insider trading, but I do think the conference call and the data meant for HFT should all be released at the same time as the public data.

I agree with both of you.

Do either of you have recommendations for services that will help me integrate the accepting of Bitcoin? Or do you have any positive or negative comments concerning Coinbase?

Yes. Being that I implemented this very quickly. I am still reviewing more anonymous payment options.

I figured that the most immediate approach was to use Stripe's client library, and not accept any name or address.

I use the Stripe client library to send the customer details to Stripe and I receive a 'user id' which is used to process the payment and then thrown away (much like the email address provided).

On one hand, the information on individual users can not be requested from directly, but could be requested from Stripe.

I wonder if a Visa pre-pay card would work.

Actually I think they are related to backlift.

If you look at the demo video at 0:44, you can see a 'Our support email:' section on the page that is generated. The email in that section is 'support (at) backlift.com'.

I think the convenience part is very interesting. I would be more curious to see how they plan on monetizing it.

I really liked the design and example graphics. But I don't know how it actually works because I am blocked by a request to sign-in using Twitter or Facebook.

I also think the site itself is beautiful, but I feel that I need to provide some constructive criticism.

* On the main page, there are links to for Twitter and Facebook, each link to their respective PHP page in the under beta/. The Facebook link works exactly as I would have expected (redirects me to a page at facebook.com). The Twitter link (infogr.am/beta/twitter.php) redirects me to "infogr.am/beta". I was expecting it to redirect me to a page on Twitter that allows me to authorize your application to access my data. I have to click a second link for that. All in all, I think this is just a small bug.

* With text like "it's super simple, just try it!" I really was expecting to "just be able to try it", but when I clicked the "Start Now!" button I was greeted with the need to sign in using either Facebook or Twitter. Having to log in is not the same as "starting now". Definitely not what I was expecting.

My recommendation is to change the wording so that it is completely understood that to even try the service I need to log in with my Twitter or Facebook account, or allow me to just use the service, and when I wish to save something, prompt me to login. Personally, I recommend the later.

* Concerning the use of social media sites as login providers. There was no mention in the "Making infographics is very simple!" section that I can use my Twitter or Facebook data to create these infographics so why does Infogr.am need access to who I follow and my tweets?

Now if you are using Twitter and Facebook as login provides because its easy, I completely understand. Then do the user a favor, on the "/beta" page, let me know right up front what you are going to access, what you are not going to access, and why you need anything you are accessing. I say this because clicking on Facebook login button redirects me to a Facebook login page that doesn't even tell me what you want to access.

If you want access to my data, be completely up front and honest with me. Twitter does, but do I really need to click through two pages to find this information out?

All in all, I really like the idea, and look forward to trying it, but I am going to wait till I don't have to use my Twitter or Facebook account to log in.