-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Common extension integration in favor of custom installation #385
Comments
Something that would be very nice to have related to the word translator and builtiin dictionary would be integration with anki, like the way yomichan on firefox has. |
I would definitely enjoy a markdown viewer. Example on firefox: markdown-viewer-webext |
This comment was marked as resolved.
This comment was marked as resolved.
That seems like it is already possible with the redirects setting, so not adding to the list for now. |
Hi, I've just discovered the browser, and I'm in love! But I need Modheader plugin for day to day development for injecting certain env variables in the http requests. As I've just discovered this browser i'm not sure if you already support this, but It could be a great feature to integrate (if at all possible). (I do apologise if my comment here is out of place) |
This seems like a nice addition, would you need multiple profiles with filters, or would a general method to edit the request headers be enough? And if not, how should we organize the config? |
Wow, thats great! Then I can use the browser at work! Awsome! |
This comment was marked as resolved.
This comment was marked as resolved.
Looked at this briefly, and while it does seem cool and useful to add, the example extension sends every request to the "api url", which is hosted by the owner of the extension, where the logic for extracting the feed urls is abstracted away. This is both a security issue and cannot be used as an example of how to implement this. I would accept contributions to implement client-side feed url extraction, but sending the url to a server to get a list of feed urls seems illogical and overcomplex. Since I have never used RSS in my life for anything, I will not be working on this personally, but I do accept PRs that implement this (again, if parsing of the page is done client-side in Vieb, not sending every url to a server like the extension linked). |
Is it possible to add the ability to access vieb internal resources and execute |
Not currently, but that is tracked in this ticket #192, so please continue discussion for such a feature there. |
something like libredirect https://libredirect.github.io/ I know vieb has set redirect but is limited in comparation with this one I point out.. ALSO: please gemini/gopher support will be great |
Redirects in Vieb are less easy to configure, but absolutely more powerful than regular redirect libraries, as you get complete freedom to change any url to a completely different url. While not directly aimed at replacing services with a different (possibly compatible instance) of it, with the right replacement patterns you can achieve the same functionality, but also for custom redirects or configs. |
People use many external password managers. Is the goal to bake in integration for all of them? |
Not exactly, but since extension support is pretty much impossible (as per #130), the current approach is to integrate the functionality of extensions for regular feature requests. For password management, there is a separate ticket that should ideally have custom integration with any password manager, see #106. |
Would a vim client in the browser like in firenvim be possible in Vieb? I know of the vimcommand setting but I think most people would prefer the above method if it's possible. |
Checklist
:help
documentation using/
for helpful informationAddition or change
As had been the case for a few years, extension support in Electron isn't good, neither is the support in Vieb. For this reason, I propose to deprecate and remove the current extension support in favor of integrating commonly requested features into Vieb without the need for an extension. The current list of extensions (or features of said extensions) that are considered are:
:help darkreader
):help sponsorblock
):help userscript
):help userstyle
):help userstyle
and:help guiscrollbar
):help :translatepage
):help toggleMarkdownViewer
):help resourcetypes
):help requestheaders
):help pageRSSLinksList
)All of these should be OPTIONALLY activated, as is already the case for the ones that are marked as done. Please feel free to suggest additional extensions/features you use often and for which there is no existing way to do so in Vieb, either in the comments below or as a new ticket.
Alternatives considered
An alternative to the above scenario would be to create and support browser extensions, but please DO NOT underestimate this task. I have tried and failed for years, as have many others. The enormous size of this task is what led to the deprecation of extension support in the first place. If you think you are up for the task, please go ahead: write the code and make a PR for it, but until then, know that building optional features into Vieb will be the current way forward. For info about the previous extension approach, see #130.
The text was updated successfully, but these errors were encountered: