Also, consumer protection laws. I smell a pile of fines and lawsuits in their immediate future.
As I understand the charge back process, vendors are generally assumed guilty until proven innocent, and it's not going to be worth Adobe's time to fight these. On the other hand, it costs credit card companies a boat load of money to acquire customers, and failing to issue legitimate chargebacks is a great way to lose customer. On top of that, the bank makes more money from a chargeback than a legitimate charge.
I've successfully issued charge backs against Experian, for example. You can't get much more in bed with the credit industry than they are. (Though the operator at the credit card company did say that Experian was responsible for about 50% of their caseload that year...)
They don't. The business model relies on most people not challenging it or not being aware that chargebacks are a thing.
Similarly, this may not fly in court either, but again the business model relies on most people not escalating all the way up (and in their case, they won't pursue it either, as they'd lose more in legal fees even if they ultimately win the case).
Nasty business models like this won't survive if people stood their ground and knew their rights better.
Researchers usually don't reach to companies since the university owns the IP and they have a licensing office that does this function. Is it a tool for them?
For sure! Researchers can use the platform to find existing solutions or opportunities in the market. If there's a strong match then they could pursue a sponsored research agreement or simply get in touch for feedback and further opportunities.
Newbie here, where's the intersection between object detection and OCR?
For example, if I have images in different pdf files that I want to compare or trying to identify information on the wine label, what are criteria to consider on which method to use?
TL;DR: codat.io is more like Plaid in that they've come up with a single schema for everyone else to build against. hotglue allows you to come up with a schema that works for your product, and gives you the tools to standardize data the way you want it. Because of this differentiation, hotglue is better suited to capture more from each API and can even handle custom data.
I think the easiest way to explain the difference is that codat.io has more closely followed Plaid's model. They standardize all the data upfront to a schema they have come up with, and then give you access to an API to query it.
Although that model works well for simple things like bank transactions where the fields are relatively uniform across different platforms, in something like accounting the fields can be quite different. For example, a journal entry in Quickbooks can have much more data linked to it than what's called a "manual journal entry" in Xero. Because of this, hotglue is designed to give you full coverage of all the data within each platform, rather than limiting you to the data that's available across each one. This becomes even more relevant when users have stored custom data inside of these platforms, which is possible in platforms like Salesforce.
The Tesla charger is more elegant than CCS, although I anticipate the following problems:
1: With CCS, the physically larger connector communicates to the customer that it's a high-speed charger. A lot of people don't understand the difference between slow and fast charging. (You can even see it in this thread where people don't know that they can't plug their Tesla into a CCS charger.)
2: CCS has bigger pins, which means it can carry higher amperage. There's no way to work around that situation with the Tesla connector.
(The bigger pin difference also, ironically, boosts the VHS vs. Betamax analogy. Betamax's biggest problem was that the tapes were physically too small, thus cutting either playback time or picture quality.)
