We create software and hardware solutions for the dry cleaning and textile industry. This includes a cloud-based Point of Sale, mobile apps and machines for automated logistics.

Our customers range from small single store dry cleaners, to larger operations servicing a multitude of consumers or a number of hospitals and hotels. Known as the innovators in this industry, join us in our mission to create the digital dry-cleaning experience of the future.

We are profitable and experiencing significant organic growth, without external capital.

Company website: https://smrtsystems.com

You can email me directly: johan {@} [our domain above]

https://gist.github.com/agh/4e20df0d2d3bfa189477569b77f72e24

Couchbase Mobile is native on iOS, Android, and C#, and compatible with PouchDB and Apache CouchDB. http://developer.couchbase.com/mobile

Here is an example of how General Electric is using our open source platform to power the Internet of things. http://www.couchbase.com/nosql-resources/presentations/offli...

[edit] we've been able to do this, funded by the success of Couchbase Server. Which looks like a high-performance NoSQL database, not an offline mobile database, but it uses many of the same data structures.

Aside: This is why I love HN. Thanks for all of your hard work.

There are also other models, sharding individual databases per user or some other application logic. There are definitely some use cases we dont handle amazingly right now, but its all heavily being worked on.

If I understand correctly pouchdb is an in browser implementation of couchdb and some api's which allow the pouchdb to synchronize with a remote, server side couchdb. It is lightweight, allows for easy set up and integration, and really focuses on the database side of things.

Meteor has this same sort of functionality and one could easily say that Meteor and pouchdb could serve nearly the exact same purpose, with the key difference being that Meteor uses mongo as opposed to pouchdb's couchdb. However, Meteor is aiming to be more than an in browser database with remote server synchronization. It also has a robust server side api with many other built in tools and features. I guess I could list out some of them, but I would suggest instead that docs.meteor.com would do a better job at this (I am not trying to say read the docs, I am just saying, they are well laid out and will be more helpful than me!).

I guess I would say pouchdb is a minimalist solution for those who want to synchronize data from client to server and have an offline solution available. Meteor is a complete, and somewhat picky, client/server framework. Their functionality may intersect in some small areas but they both serve very different functional purposes.

However, PouchDB have been making some serious progress to support complex offline apps with a lot of data, like full support for secondary map/reduce indexes.

That's not really a good solution for all the obvious reasons. (Speed, resource usage, dependencies.) Plus, by that logic every client-side webapp supports being rendered on the server, so that's not even a meteor-specific advantage.

Conversely, React actually does supports true universal (aka isomorphic) apps; you can pre-render the app on the server using node (without needing a headless browser), ship it to the client, and rehydrate it. (Ember is working on shipping the same functionality under the name FastBoot.) Meteor doesn't have anything like that.

I'm sure meteor+react has some advantages over pouchdb+react, but it's not because of server side rendering. :)

(Well, as far as I know. I haven't been paying much attention to Meteor development, so it's possible the story has changed in the last few months. But last I checked, true server-side rendering was easy with react, but not really possible with meteor.)

We're becoming the true Turbo Tax for compliance.

We're fixing the certs now and updating our Key rotation procedures for you all to see in our publicly viewable compliance workbook.

But you're right, that getting Key Rotation Procedures documented is the 1st thing I should have done.

This is good feedback actually because now I know that after scoping the assets in my turbo tax-like tool, the very next thing a person should do is write down their key rotation procedures. Its also easier to write out as a procedure because its such a common yet forgetful practice.

We're putting cycles into this right absolutely now.

Western Union can provide a lot of relevant services: escrow, conversion to obscure currencies (or just general exchange), fraud mitigation, etc.

Ah yes. The fraudsters favorite service for irreversible cash transfers will certainly have an advantage there.

But OK, I'll take the bait :).

Yes, Western Union can provide a lot of relevant services, but so can _anybody_, and there are already a number of Bitcoin exchanges.

To assume that Western Union ought to provide Bitcoin services is like assuming that a horse-and-buggy company ought to start making cars. I mean, sure, it might be a really good idea, but cars are a _revolution_ of the horse-and-buggy, not an _evolution_. Likewise, Bitcoin is a revolution compared to traditional money transfer, not an evolution.

I agree that "if you have to explain a joke, it isn't funny", but not only was I on-topic for the story -- but also for the specific thread.

The implied point was that the good people at Western Union aren't as dumb as the previous commenter stated, and probably are excited about a (possible) reinvention and embracing of bitcoin.

Forgive me for injecting some levity into an otherwise boring story, but my point was clear and remains valid.

I suppose I should have just called the previous poster a troll and stated "they're probably excited". Oops. I'll be more confrontational next time.

(Also, not on reddit, just would rather attempt to use humor to get a point across. Maybe I watched too much Monty Python as a kid...)

My friends trying Coinbase have raised concerns about the long delays as well, and I have a bitcoin transfer to my personal wallet that's been pending for multiple days. This needs to be resolved quickly to keep Coinbase and Bitcoins reputation.

This is an existential flaw in their business. Why don't they just reject transactions at expired prices? (If they wanted to be slightly more evil, they could do this in one direction only.)

I'm just responding to metaverse's reasonable hypothesis here. Coinbase ought to diminish speculation by providing information, unless there are legal reasons for them not to do so.

Using a business model entirely dependent on the best case scenario would not be wisest play they could make. Even if BTC did stabilize, we now know market prices like this are not guassian but fractal/power-law based. Infrequent but sudden unexpected extreme volatility is a natural characteristic of such systems.

A better idea would be to develop a business model that at least expects that and does not fail when it happens, or at best exploits it.

Bitcoin's reputation has survived much worse. Mt.Gox hacking, Bitcoinica hacking, and several others. Bitcoin has intrinsic value independent of the private company infrastructure that springs up around it, no matter the foibles of the latter.

Coinbase's reputation on the other hand, is another matter.

  This is probably as good a time as any to mention 
  that if you are in SF and are an awesome software 
  engineer, we’re hiring: https://coinbase.com/jobs

I'm wondering if this has bitten them really hard during the runup.