The results shows as:

  Download PuTTY - a free SSH and telnet client for Windows.
  PuTTY is an SSH and telnet client, developed originally by Simon Tatham for the Windows platform. PuTTY is open source software that is available with source...

On a day off work, I got a cold call to my personal mobile. This salesperson called me by my name and then tried to flog something relevant to my job. Being hugely irritated, I shared my thoughts with the caller demanded to know where they'd found my number. They were at least a little bit apologetic, and said they found it on LinkedIn using a plugin called "Lusha".

Lusha's website has claims about being GDPR compliant, but at the same time being a "crowsourced data community". They do at least publish a "Privacy Policy" and some contact details for a data controller.

I emailed them with a Subject Access Request, which they responded to two weeks later in a very cagey manner. Actually, I did some sleuthing of my own. I found an unlisted link for a broken OneTrust request form. This didn't seem to be linked anywhere on the website and I literally guessed the URL for it. After some poking around in the debugging console, I recieve a more fully furnished copy of my profile.

The data source for my email was... "Lusha's email guess algorithm" - now, one of the downsides of working for a small business and getting a firstname@domain.com is that guessing it isn't particularly difficult.

The data source for my phone number was more interesting. "L.S Mobile Apps Holdings Ltd." a company I'd never heard of, but eventually found an App Store[0] and Play Store[1] listing under a very similar name.

Looking at the apps published by this company, you can immediately see where this is going: a "Caller ID" and an even more transparent "Contacts Backup" app - both having complete access to all your contacts. At this point it becomes clear where my contact information has actually come from: someone I probably work with has created a contact in their phone with both my email and personal phone number, then used one or two of these apps.

I decided to pick the Contacts backup app to take a closer look. Installing the app on a wiped phone, I explored the UI, disassembled code and snooped the requests to their servers to see where exactly this mysterious "GDPR Compliance" was. The primary functionality is of course to create an account, upload all your contacts, and let you sign in on another phone to download them. There was some effort to make this work for most users, workarounds for edge cases, etc. It was more than the low-effort app I was expecting.

All the sharing functionality was checked behind a "consent" dialogue (and I use that term extremely loosely). The deal was that app would helpfully hydrate my entire contacts book with missing details! All I had to do was share it in turn. What I found peculiar about this was it simply didn't work. It seemed as through not only would the server not populate the missing data, but the code that handled this client-side was unfinished.

If you're wondering what the link between Lusha & L.S Mobile Apps is, they're effectively the same company. Yoni Tserruya, the co-founder of Lusha, has their fingerprints all over the the certificates used to sign the Android LSM Apps. It's clear this app's data is what they've built their company on.

Now, both Google and Apple have well known to display "Data Sharing" information as part of the store pages. The Play Store page explicitly says "No data shared with third parties", whereas the App Store omits the usual section you'd see when data is shared with third parties.

I contacted both Apple and Google with full details about what I'd found, and in the least surprising event to my saga, they did nothing.

Sadly, instead of having any satisfying conclusion, what I saw was what I already knew. I even got angry when reading their privacy policy, and how completely clear that all this "GDPR Compliance" labelling they have is there to sell their product to EU customers and they're clearly not compliant.

Here's some ragebait for the rest of HN who cares about their data:

- French DPA (CNIL) says Lusha is full of shit, but they can't do anything because they're based in Israel[2]

- Lusha doesn't think consent is important[3]

  [0] - https://apps.apple.com/gb/developer/lsm-apps/id1634388352
  [1] - https://play.google.com/store/apps/dev?id=5128998142474323958
  [2] - https://www.legifrance.gouv.fr/cnil/id/CNILTEXT000046775564?isSuggest=true
  [3] - https://www.lusha.com/privacy-articles/please-show-me-where-i-have-consented/

This means high volume low value sellers have little incentive to actually properly describe things or post correctly. A common issue I keep seeing is sellers using slower postage than paid for. You can immediately see from the tracking number, even if you wait 7+ days to submit feedback, you'll get a 'sorry' refund and the feedback is somehow 'addressed' without them going back in time and delivering it faster.

Online reviews are just a sham now, Goodhart's law etc as even if the reviews aren't fake, they're encouraged or incentivised from real customers. Look up any service provider on TrustPilot and it's the same: hundreds of 5-star reviews from people told to add a review just after signing up, a dozen 1-star reviews from bad customer service, and barely anything in between.

These winning photos are a bit boring my comparison, the ghostly effect of foliage in IR is cool but a bit overdone when there's so many and there were so many other interesting differences in every day objects.

I'd love to do the same with my mirrorless camera but it's a quite destructive operation.

I think it's one of the big misconceptions that React Native is _the_ path to get your web devs or even existing code onto mobiles. That's how you get the criticism that RN builds bad, mouldy apps.

Between our clients that have had this issue with quality and shops in the same space as us that haven't (one who boasts a review on one of their apps being "an example on how to build a proper fully native app"), having a good portion of native devs on the team is a big differentiator. Unfortunately this means a RN Team isn't as cheap as some hope.

Although I had success with PTGui and it "just worked", I didn't fancy paying for it and instead used Hugin in the end. This lead me to take around 63 pictures with 50% overlap.

The film was a 4x5 negative and after stitching I'd say the effective DPI was ~4500

That being said, this was a one-off, but once I had enough overlap with each capture, PTGui was able to switch it together relatively hands-free, even with it having lots of sky.