Live data from Hacker News

Don't fuck with paste

github.com

171–180 of 397 posts

Re: Don't fuck with paste

#171

Earlier quoted context omitted.

This is a bit cynical isn't it, when the author is clearly being as transparent as possible about what they need and why, which is due to factors outside their control. Of course you're right in a technical sense. They could do whatever they want later. But still let's celebrate and attitude like this rather than criticizing it.

But WHY do they need that permission? They dont need it to implement the paste behavior. Looks super sus to me.

The extension needs to re-enable paste, which means it needs to possibly inject some JS into the page.

Re: Don't fuck with paste

#172

Thanks for this! Also related, Who t.f. thought that * Ctrl-V should be "paste with format" * Meta-Shift-Whatever-Ctrl-V should be "paste without format" I've never EVER had the need to copy some text and paste it with a different font face, color and ffs background color ... Who is the genius UX expert that decided on this abhorrent behavior?

Paste with format is actually usefull sometimes. For example, you can copy from vscode and paste into Microsoft Word, then the resulting code will be property formatted and highlighted.

Re: Don't fuck with paste

#173
post #5

Right up there with hijacking Ctrl-F.

I just don't get it why browsers allow websites to override their own hotkeys. I'm sure it even required extra code to be written to work correctly.

Linear hijacks Cmd+F for example, very helpfully providing some terrible thing instead of my browser's built-in search that works the same everywhere. (it's the same Linear that thinks you can't not want wysiwyg markdown editing)

Re: Don't fuck with paste

#174

> In order to provide the smoothest experience as possible, the extension needs to know when you change active tabs. In order for the extension to know about that event, it needs the tabs permission, which Chrome describes as "can read and change all your data on websites you visit." That description is very scary, and is certainly not what this extension is doing. Being an open-sourced project, you can always read a…

This is a bit cynical isn't it, when the author is clearly being as transparent as possible about what they need and why, which is due to factors outside their control. Of course you're right in a technical sense. They could do whatever they want later. But still let's celebrate and attitude like this rather than criticizing it.

It would be more transparent to be candid about the limitation of what they can provide.

It isn’t the developer’s fault that the ecosystem is dumb, but they could just note the limitation.

Re: Don't fuck with paste

#175
post #5

Right up there with hijacking Ctrl-F.

I just don't get it why browsers allow websites to override their own hotkeys. I'm sure it even required extra code to be written to work correctly. Linear hijacks Cmd+F for example, very helpfully providing some terrible thing instead of my browser's built-in search that works the same everywhere. (it's the same Linear that thinks you can't not want wysiwyg markdown editing)

Well, for Ctrl+F there is sometimes a reason. Many websites uses technique called virtualization of lists. That boosts performance, but standard Ctrl+F doesn't works anymore properly

Re: Don't fuck with paste

#176

> In order to provide the smoothest experience as possible, the extension needs to know when you change active tabs. In order for the extension to know about that event, it needs the tabs permission, which Chrome describes as "can read and change all your data on websites you visit." That description is very scary, and is certainly not what this extension is doing. Being an open-sourced project, you can always read a…

then u can simply clone the repo and locally load the extension ... bye bye auto-updates

Re: Don't fuck with paste

#177

Earlier quoted context omitted.

This is a bit cynical isn't it, when the author is clearly being as transparent as possible about what they need and why, which is due to factors outside their control. Of course you're right in a technical sense. They could do whatever they want later. But still let's celebrate and attitude like this rather than criticizing it.

It would be more transparent to be candid about the limitation of what they can provide. It isn’t the developer’s fault that the ecosystem is dumb, but they could just note the limitation.

So you're saying they shouldn't add the feature rather than asking for the permission?

Re: Don't fuck with paste

#178
I think browsers need to implement an optional feature.

Stop js shit after the page loads complete. Only enable js when user interacts with a button or something.

Re: Don't fuck with paste

#179

> In order to provide the smoothest experience as possible, the extension needs to know when you change active tabs. In order for the extension to know about that event, it needs the tabs permission, which Chrome describes as "can read and change all your data on websites you visit." That description is very scary, and is certainly not what this extension is doing. Being an open-sourced project, you can always read a…

That's exactly why I use my system package manager to install and update browser extensions.

And whenever the package repository is missing a browser extension I need, I contribute the package and take responsibility for its ongoing vetting and maintenance.

Re: Don't fuck with paste

#180
Do we really have to put up with vulgarity even on HN?

It's bad enough to see it in the title--cause someone will say that's what the title is--but, as can be seen, it breeds unnecessary vulgarity throughout this thread.

To see the irony of it all, I'll get fucking downvoted for fucking complaining about this fucking shit and maybe get really fucked up by getting fucking banned.

Do you get my fucking point?

Post reply on HN