Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How Bluesky draws its logo on screenshots

timmarinin.net

Post reply on HN
Print view View original

41–50 of 478 posts

Re: How Bluesky draws its logo on screenshots

#41

Post by Waterluvian »

mikepurvis wrote: post #22
fer wrote: post #10

Earlier quoted context omitted.

> hostile and annoying If someone from Google Maps or LinkedIn team is here, please, when I take a screenshot it's because I want to a screenshot, not share the friggin location/post. Not sure who got the idea that it was useful, it isn't.

I would happily use the Google Maps "share" feature, but I've yet to encounter any but the simplest of scenarios where it actually preserves the entire context of what I'm trying to share: the viewport, the start and destination, stops along the way, route choice, the time of day, all of it. If I'm sending a screenshot it's because I want to send exactly what I see on my screen and not have my recipient's gmaps insta…

It's of course about lock-in. In the early Web-GIS era there were a few competing but popular notation standards for sharing lat/lon/zoom/ that was meant to be human readable and compatible with any WMS or similar.

Ah... to imagine a world where you could just share a coordinate string and people could open it in whatever map app/page they wanted. Geo URI is probably the closest we have today but I don't think much of anything outside the OS Geo community accepts it.

Re: How Bluesky draws its logo on screenshots

#43

Post by hmokiguess »

x313 wrote: post #21
hmokiguess wrote: post #17

Earlier quoted context omitted.

And such engineer would have enough organizational clout to just ship it without going through anyone?

Bluesky has <100 employees so it could be possible

I agree that having less people to manage means easier to build trust relationships and culture, though I believe some form of management and control must exist.

Re: How Bluesky draws its logo on screenshots

#44

Post by nemomarx »

javier2 wrote: post #34
shiandow wrote: post #9

Earlier quoted context omitted.

It still baffles me that it has become normal for an OS to place the wishes of an app above those of the user. Hijacking the screenshot process is a privilege that you ought to be able to revoke, it's insane to allow software to be given more control. And don't tell me it's anything to do with security when it can be circumvented in any number of ways.

Did you read the post? Nothing is hijacked, but its a trick where they render the normal button in a ui element for secret data, which is blanked by the system on screenshot, revealing the logo underneath. Its a reasonable feature, so its hard for apple to control it better or remove this.

users should have some way to control if screenshots have secret data in them or not, really. what if I do actually need to preserve it?

Re: How Bluesky draws its logo on screenshots

#45

Post by haileyok »

hmokiguess wrote: post #8

This sort of stuff to me is an example of fear within an organization. Whenever I see engineering resources allocated towards self promotion and branding rather than quality and features for its users it shows how leaders want control over narratives.

Someone spending half a day on a feature that places the app's logo in the screenshot so people seeing it can know where it came from is "fear within an organization"? You've got to be kidding lol

Re: How Bluesky draws its logo on screenshots

#46

Post by xorcist »

javier2 wrote: post #34
shiandow wrote: post #9

Earlier quoted context omitted.

It still baffles me that it has become normal for an OS to place the wishes of an app above those of the user. Hijacking the screenshot process is a privilege that you ought to be able to revoke, it's insane to allow software to be given more control. And don't tell me it's anything to do with security when it can be circumvented in any number of ways.

Did you read the post? Nothing is hijacked, but its a trick where they render the normal button in a ui element for secret data, which is blanked by the system on screenshot, revealing the logo underneath. Its a reasonable feature, so its hard for apple to control it better or remove this.

That is a lot of words just to make it sound reasonable that a page can be exempt from the underlying screenshot functionality. It isn't. Not without asking the user.

Re: How Bluesky draws its logo on screenshots

#47

Post by bethekidyouwant »

Razengan wrote: post #24
fer wrote: post #10

Earlier quoted context omitted.

> hostile and annoying If someone from Google Maps or LinkedIn team is here, please, when I take a screenshot it's because I want to a screenshot, not share the friggin location/post. Not sure who got the idea that it was useful, it isn't.

Blame Apple for even allowing apps to be aware of the user taking a screenshot. Just like their iCloud Keychain API that lets apps secretly track users across app reinstalls and device resets.

Getting your account back on reinstall is good

Re: How Bluesky draws its logo on screenshots

#49

Post by jjcm »

If it's between this and a perpetual logo, I'll take this any day.

I actually really like this approach. The action button isn't relevant in this context, and it doesn't occlude the content.

There's certainly situations where you wouldn't want this (ie if you're developing the app and you want to redesign starting from a screenshot), but for the average user I think this isn't overly hostile. I understand that people are dogmatically opposed to intent being modified, but I think you need to balance nuance. I actually enjoy having an attributable source in shared elements, and I think this is a low-impact way of achieving that.

Re: How Bluesky draws its logo on screenshots

#50

Post by pfraze »

hmokiguess wrote: post #43
x313 wrote: post #21

Earlier quoted context omitted.

Bluesky has <100 employees so it could be possible

I agree that having less people to manage means easier to build trust relationships and culture, though I believe some form of management and control must exist.

I'm sure this wasn't even in the top 10 of things that we made sam implement out of fear
Post reply on HN