Hacker Newsnew | past | comments | ask | show | jobs | submit | plunchete's commentslogin

No more VACUUM then?


Vacuum is still there. Though in some cases it is significantly faster.


I think buttons adds a new whole of opportunities to Slack integrations, straight forward interactions.


Is the pricing public?


Not yet. We're working it during our early access program. Well be looking for lots of feedback from customers.


Thanks! Looking forward to be able to try it :)


I find it funny that the article repeats several times the amount of data that square. Do you know who has more data? The bank where the business has its account ;)

That being said, the current process from banks seems old and not really clever to me


Square gets item level data on each merchant. That means exactly what was sold and when. Plus, they get info about who bought it and can see things like a buisness suddenly getting huge numbers of new buyers as opposed to returning, etc.


The real question is how much does that level of granularity really matter?


Its not worth a banks time, with their current set-up, to process loans under $50,000.


But at least with Square we have relatively more transparency about their activities and intentions with such data. So while it may not literally be more, it's like functionally more?


I think the main point trying to be made there was that there is nothing stopping banks from doing something similar. In other words the "data" the article keeps mentioning isn't the advantage that makes this possible for Square.


The problem is most banks don't have the technology to scan a customer's bank account and decides his/her credit worthiness. That's how antiquated banks are and they wouldn't touch anything subprime after 2008 financial crisis.


All of them seem being available for free if you have Amazon Prime (I do). It's pretty awesome!


Great! IMHO the main problem with CodeAcademy was not teaching how to build things. I have several non-tech friends who have done 30 exercises about loops but have no idea when to use a loop.

I think this is the right direction. Give a more complete view and do it step by step so the person learning can be rewarded and keep the motivation.


I love the concept of the middleware to modify the requests. When are you guys going to start sending the invites?


Right now. It shouldn't take more than a day unless we encounter some errors.


Thanks!


What kinds of things would you use it for?


Different API keys in there instead of my app, alerts when the API is down, headers, etc. I think it's kind of nice that I don't have to code them or that I just have configure my app to use 3 different API tools end-points for dev, qa, prod. But I really think that the best usage for them is monitoring


Totally agree with you. Actually I came to comments to say exactly that


Seems like the author forgot to learn the conventions of the language. The site looks like a good reference though


My thoughts to. Indentation was all wrong.


I'm pretty sure that at that time I had tons of music (using winamp) and photos on my computer (scanning was the way at that time).


You must've been somewhere nice that had fast internet. I think most people back then had dialup, and downloading a single song would take at least 20 minutes on their 28.8k modem.


You just waited that long to download music. That was all there was to it. MP3 was mindblowing when it was first released, in terms of how good it sounded for the size.

Obviously many people just ripped their own CDs. Many CD-ROMs didn't support ripping CDs at a data level - so you had to rip in real-time via analog! Crazy.


Most people I knew had 56k modems by 98 (by '99 I had a cable modem), 128kbs compression was the standard you'd find, and getting a song for free by just waiting 15 minutes was still magic

Edit almost forgot about Ethernet in the dorms. I picked my college because of high speed Internet.


As mech4bg said, much or most of people's .mp3 libraries at that point had probably come straight off CD. Napster wasn't even released until 1999, and "Rip. Mix. Burn." was Apple's edgy new slogan of 2001 http://www.youtube.com/watch?v=4ECN4ZE9-Mo .


Wow, that's quite a find. A rare artifact from the pre-iPod, pre-iTunes Store tip of Apple's foray into digital media, and a strong piece from Apple's agency at the time.


You just queue up a bunch of stuff using a download manager[1] and stay connected for longer. Come back the next day (or two or three) and voila! The good managers would even resume partial downloads if the connection dropped (which it always did).

[1] - http://en.wikipedia.org/wiki/Getright


Why download? I simply ripped all my CDs to mp3s.

That was a pretty good collection.


In the good old days, MP3s were generated by ripping CDs or copying from other people's computers during LAN parties.


Audiogalaxy was our savior. Search from any computer and queue up the download to your satellite. When you arrived home 5-6 hours later your music would be waiting for you.


Nobody used 28ks in 1998 unless their phone lines didn't support 56k.


Yes, even if you exclude MP3s of commercially-recorded music as not really personal, it would be very hard to defend the proposition 'iMovie gave birth to the idea of "personal digital media"' or even 'iMovie first made "personal digital media" a reality'. Apple (and MS) had been trying to make consumer video editing a reality since at least 1991 and the launch of QuickTime (an awkward date if you want to centre everything around Jobs and/or NeXT). iMovie and the FireWire iMacs probably were an important step forward in making digital video editing into a mainstream and well-oiled consumer activity though.


Quicktime circa 1991 was not really "personal digital media"-grade technology. It was pixelated, postage-stamp sized videos even on a 640 x 480 screen. It wasn't until 1998 and the Sorenson codec that Quicktime began to approach what we would recognize today as usable video.


People on Hacker News might've, but the general public had a far slower uptake on it.


you're one of the 'very few' then. As was I.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: