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

Looks like they were notified of this miss

> please contact them at support@supercardsapp.com and they will respond in a reasonable time.

https://supercardsapp.com/privacy-policy/privacy


Well that turnaround is pretty confidence-inspiring.


What was the original business model that Honey had? I only know of the current Honey approach, inserting themselves into the checkout page, did Honey work differently before? More like a coupon search engine? That’s the only way I can imagine “first click” makes sense.


I totally agree! I really liked https://lets-go.alexedwards.net which walked you through creating a web api with a database. When I did it, I decided to use SQLite instead of what was in the course, which meant I could follow along but still had to understand and choose the right dependency etc myself.

(I’m not affiliated, just a happy customer)


I wasn’t aware that WKWebView granted the app such power. Is there a way for me as a user to figure out if WKWebView or SFSafariViewController is being used if I have a web page open? Although I don’t use FB, I do use the web view of other apps and don’t want them to be able to do this either.


SFSafariViewController is less customizable visually so the standard "sheet coming up within the app" that looks always the same regardless of the app (at least in most apps and of course not Meta's apps) is that one.

Having said that, since WKWebView is just a view that can be customized visually, nothing can stop someone to create a WKWebView-wrapping view controller that looks exactly like the "safe" Safari one anyway.


Certain features are not available to WKWebView.


Yes, there are ways to distinguish between them as a user, for example you can check to see if your browser plugins are available. I also went through some of the most popular iOS apps and created a list of which app uses the correct SFSafariViewController vs the potentially malicious WKWebView.

- https://krausefx.com/blog/ios-privacy-instagram-and-facebook... - https://krausefx.com/blog/announcing-inappbrowsercom-see-wha...


Reading the “How Does it Work?” section of the readme, I interpret it as WebUI being a way of embedding a web view into your existing program, being a sort of proxy for the existing browser of the system.

https://github.com/webui-dev/webui#how-does-it-work


Don't frameworks like Electron (and Tauri) already allow us to do this today?

I couldn't tell from their docs what makes their project unique compared to these existing and more popular solutions.


Electron bundles a full installation of Chrome into every application.

WebUI uses whatever browser (or browser component) is already present on your system.

That's a big difference!


We got your point the first time you posted this. You come across as someone who tries to keep the monopoly for themselves.


In addition to what the others have said, make sure you have a CI and don’t review the PR until that’s showing green. The CI should ideally include tests, linting according to a common code standard and other “grunt tasks” that are unnecessary in a PR review.


Indeed similar to all Big Tech companies laying off the past year.


I’m using QuickScan on iOS for this, which has customizable favorite export locations so that you with one press after a scan can upload to specific folders in google drive etc.


Your examples with even numbers in feet and odd in meters tell me that is what you’re used to.

I can counter with that saying 180 cm is a lot easier than 5 feet 10.86 inches. No one says that, similar to that no one would say 17.78.

What’s convenient with metric is that there isn’t any difference between saying 180 or 179 cm. You just say, “one seventy nine”, not “one hundred and seventy nine”. Here I am showing what I am used to.


Well my point with the examples was not the ".78" part, it was the "7" vs "17".

In your counter example, I would just round the imperial units to 5 feet 11 inches or 6 feet in everyday conversation. My point is that whether it's 180 vs 18 vs 1.8 all of those powers of ten are just a little bit less ergonomic because they do not fit nicely onto my two counting hands. 5 and 6 do fit nicely on my hands (and in my head) and so are just a tiny bit nicer to use every day.

To be honest, if the meter was closer to the size of a foot the metric system would have the same advantage. The powers of ten part is the good part of the system, not necessarily the absolute sizes of the base units.

I agree that if I grew up with it I would think it is fine. It is just what you're used to. I'm just expressing an opinion, I don't know why everyone needs to downvote me, I keep saying that metric is better.


When was the last time you, uhh, tallied up someone's height with your fingers? I don't understand what you're getting at here?


As I understand, the starting point looks to be that you most often deal with single digit numbers of imperial units, but in metric it's less often the case, and that's inconvenient. While I'd generally agree that a single digit is slightly easier to deal with mentally, I'd be skeptical on whether imperials are that much better covering convenient ranges. For distances similar to inches, feet and yards you have centimeters, decimeters and meters, which are pretty close, but still with added benefit of simplicity and uniformity.

Metrics allow to look into much large range inside the same system, which allows quick mental estimations; converting parts of an inch into feet or yards are less convenient. Then we can talk about areas and volumes, where metrics multiply nicely, but with imperials there's a whole set of special units.


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

Search: