-
Notifications
You must be signed in to change notification settings - Fork 44
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
Facebook support? #39
Comments
This is definetly possible, but it would require quite a lot of extra work to keep everything working on newer and newer versions of facebook. Facebook changes their website quite often, so the css would have to update at a similar pace to keep from being broken (unless it is designed very well). I might design one for the nojs version of facebook, as that seems to be relatively stable and is what I personally use. For information on adding a new site, see this section of the readme, but if you start work, please start on the |
Yeah, I would expect any Facebook support to be very quickly obsoleted by changes on Facebook's end. But feel free to contribute it if you like. :) |
Sadly of course, but yeah I'll need to contribute one day.
On Fri, Apr 20, 2018 at 18:53 alphapapa ***@***.***> wrote:
Yeah, I would expect any Facebook support to be very quickly obsoleted by
changes on Facebook's end. But feel free to contribute it if you like. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK2v6sKu8ze17pVui-CSSRSBKDMnJ_jaks5tqnTtgaJpZM4TYnzi>
.
--
Jordyn Carattini (The Linux Geek)
|
BTW this is an example of a case where an alternative method of defining stylesheets would be more effective, e.g. mapping certain colors to alternative colors would allow nearly automatic transformation of any stylesheet Facebook puts out to an alternative color theme. That could be done fairly simply with a script. |
Would facebook support be a posibility in the near future?
The text was updated successfully, but these errors were encountered: