Locking Pinned Tabs
-
Said:
BUT a major drawback is security.
All extensions are open source code. In the folder of the extension you have all the files:
Check one by one the Javascript ones and see if there is a home page that the extension is communicating and sending information to it.
If not, it is safe.
-
I appreciate that guidance, of which I had no idea. But the dev can change any of these scripts at any time so I'd have to check them all daily. Correct? I'd be glad to hear otherwise. Thanks again.
-
Said:
But the dev can change any of these scripts at any time so I'd have to check them all daily.
It seems to me that it doesn't work that way.
Because when would it be “appropriate” to change the code?
At 6, 8, 12, or 24 months after putting it in the Store. It doesn't make sense.
But if you don't trust the extensions as if they were devil, then don't use it and stay with the problem.
-
I don't mean to derail this thread into a discussion of extension security, but it is central to why I want Pinned Page Lock / Link Control to be native in Vivaldi. Extension dev ownership can change. That's what happened with "Poper Blocker" which bit me. Now I'm much more careful and enable as few extensions as possible.
-
Said:
I want Pinned Page Lock / Link Control to be native in Vivaldi.
Pure goodism.
You should never have installed “Poper Blocker”, since uBO does it naturally.
Also, you should not use NoScript together with uBO, it only harms instead of helping.
-
@barbudo2005 I didn't have UBO in 2017 so your advice on that is irrelevant to both my experience and, obviously, to my caution re extensions in general.
As for running UBO alongside NoScript, knowledgeable people differ with your equally valuable advice on that. Anyway, that picture will soon change greatly with the demise of UBO. I'll be switching to UBlock Origin Lite from the same dev.
Sorry to hear that you're so opposed to an option for a pinned tab to be locked. It still seems sensible and desirable to me, and to others, and btw to the developers of the Link Control extension.
-
Said:
Sorry to hear that you're so opposed to an option for a pinned tab to be locked.
I am not opposed to an option for a pinned tab to be locked.
Simply put, the way the team would accomplish what you want is exactly the same way the extension does, that is to open those links in a new tab.
So, since the team doesn't waste scarce resources, it won't do what you ask, since it can be done with an extension.
And this approach is valid for all those requested features that can be achieved with CSS & JS Mods or extensions. It is as simple as that.
-
@barbudo2005 CSS and JS mods are risk-free. Extensions are not. It is as simple as that.
-
Immediately uninstall uBO. It is risky.
-
@barbudo2005 Your juvenile sarcasm doesn't advance this thread. I explained why I run as few extensions as possible, and only the most trusted. Read that again if you still don't understand.
-
Have the developers acknowledged that they are aware of the requests for this feature?
-
This is currently the 25th most highly upvoted request. In the sea of thousands of requests, I'd view this as pretty high up there.
In it's smallest form, it would be two new options added to the right-click menu of the pinned tab. I understand there's more technical difficulty beneath that. But I think it would be great to hear from the team on if this would be prioritized.
I'd LOVE to see "back to pinned url" and "replace pinned url with current".
-
@kvenn Actually, the 27th most popular request including mail and mobile requests, but it is very old, and still not tagged. There is a simple workaround, or two:
- Open links in new tabs from pinned tabs
- Use the Back Button History list (Click and hold) and choose the last item on the list.
The developers are aware of the feature request, but the number of upvotes is not the sole criterion in deciding priority for implementing it.
@DoctorG said in Locking Pinned Tabs:
Team does not give a timeline.
-
Thanks for the reply - and I totally understand that prioritization can be challenging. Those workarounds aren't particularly viable for my use case, but I appreciate you throwing out suggestions. It would be great if it was supported natively by the browser, like it is in Arc and Zen.
I was just hoping to convey why I felt this would be a cool feature to have and why I felt it would be beneficial to re-assess it in priority. Having worked on browsers before, I would have assumed (barring any crazy architectural limitations), that this feature would be about a 4 hour project for someone (not include reviews and QA).
I assumed these threads were an opportunity for the community to advocate for why they felt certain features should be prioritized and discuss what their ideal browser could be. Was I mistaken? The vibe I've gotten from a few of these threads from ambassadors was that they don't really want the community to engage.
-
@kvenn I have tried for years to elicit more feedback from the Developers, but without much luck. Ambassadors are only ordinary users who try to help out, so I provide workarounds wherever I can, or tell users how it is.
