Re: [Bug-gnuzilla] Allow Free Fonts from websites option

2017-08-09 Thread ng0
Forget this idea, it will just not work out. I don't know that much
of the internals of Firefox, but I'm pretty sure there is no concept
for a limited list of fonts in Firefox.

And with that we arrive again at lists. A list will always be limited.
Let's just assume that in theory you were able to do this. Will this be
an __optional__ thing? Because you will not be able to cover all the FOSS
fonts ever, and you will have a very hard time dealing with the joy that is
lack of versions or any kind of associated metadata in the font creator
community. Those who care to do it are I assume in the minority or have
been bothered enough by operating systems.

Personally I have started on a side-quest to make all fonts which are bundled
at fonts.google.com, which is just a 3rd party irregular updated repository,
to be able to be used without it through Guix.

To try and rule over fonts is impossible. Okay, it is 2017 and most fonts are
under a free license or at least the one which I know of. Nevertheless there are
commerical fonts, and some people pay money for them. If I wanted to default to
seeing the fonts - which might even be hosted on the server of the website you
are visiting because they aquired a license for it - I should have the option
to do so.

There are better ways to waste your time. Unless you start filling up some 
existing
font database or create a new one which can be queried and/or even included 
offline
to be searched by applications, in that case I'd say go for it. Everything else
is just hopeless and doomed (avoid static lists!).

Narcis Garcia transcribed 1.2K bytes:
> If fonts have no license metadata, then this distinction is not a well
> doable.
> What user-side can do is to have some plugin that replaces web-requested
> fonts to a catalog of FOSS ones, but not the browser itself.
> 
> 
> El 08/08/17 a les 22:51, ng0 ha escrit:
> > How would you check the license of a font at runtime?
> > Hardcoding names? Not an option, please don't even think about it.
> > Maintaining a list of fonts that are considered free? That could become
> > outdated very soon and will never be 100% complete. Off the table aswell.
> > 
> > So far this is the start of an early idea, not a start for an proposal.
> > 
> > David Hedlund transcribed 3.2K bytes:
> >> It is not unchecked in icecat 52.2.1 for Trisquel 7.
> >>
> >>
> >> On 2016-06-05 00:26, Alejandro Hernández wrote:
> >>> Hi,
> >>>
> >>> Icecat has uncheck this typography option by default:*Allow pages to 
> >>> choose their own fonts*.
> >>>
> >>>
> >>> I would like to*allow sites to choose their own fonts*  *ONLY IF THEY ARE 
> >>> FREE SOFTWARE*. It would be good there were an*option*  for that.
> >>>
> >>> Sonrisa
> >>>
> >>>
> >>>
> >>> Thanks.
> >>>
> >>>
> >>>
> >>> --
> >>> http://gnuzilla.gnu.org
> >>
> > 
> >> --
> >> http://gnuzilla.gnu.org
> > 
> > 
> > 
> > 
> > --
> > http://gnuzilla.gnu.org
> > 
> 
> --
> http://gnuzilla.gnu.org
> 

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Allow Free Fonts from websites option

2017-08-08 Thread ng0
How would you check the license of a font at runtime?
Hardcoding names? Not an option, please don't even think about it.
Maintaining a list of fonts that are considered free? That could become
outdated very soon and will never be 100% complete. Off the table aswell.

So far this is the start of an early idea, not a start for an proposal.

David Hedlund transcribed 3.2K bytes:
> It is not unchecked in icecat 52.2.1 for Trisquel 7.
> 
> 
> On 2016-06-05 00:26, Alejandro Hernández wrote:
> > Hi,
> > 
> > Icecat has uncheck this typography option by default:*Allow pages to choose 
> > their own fonts*.
> > 
> > 
> > I would like to*allow sites to choose their own fonts*  *ONLY IF THEY ARE 
> > FREE SOFTWARE*. It would be good there were an*option*  for that.
> > 
> > Sonrisa
> > 
> > 
> > 
> > Thanks.
> > 
> > 
> > 
> > --
> > http://gnuzilla.gnu.org
> 

> --
> http://gnuzilla.gnu.org


-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Forced to have valid cert

2017-08-02 Thread ng0
David Hedlund transcribed 4.3K bytes:
> That error occur in Firefox first of all. You should file the bug to
> bugzilla.mozilla.org.

This has nothing to do with Firefox. Well it does, but it is known.
StartCom has been kicked out of the trust store.

https://www.ssllabs.com/ssltest/analyze.html?d=y.st
https://freepo.st/post/jgcacuv4l4#comment-rbr0jagu5y
https://wiki.mozilla.org/CA:WoSign_Issues

WoSign is the CA which runs also StartCom, the one which y.st uses.
So the majority of browsers will not display this site via the globally
trust revoked CA.

> 
> On 2017-08-02 19:59, Caleb Herbert wrote:
> > When I visit https://y.st/ I get the following message from IceCat:
> > 
> >  An error occurred during a connection to y.st. Peer’s
> >  Certificate has been revoked. Error code:
> >  SEC_ERROR_REVOKED_CERTIFICATE
> > IceCat offers no option to accept the certificate anyway.  All it
> > presents me is a "Try Again" button.  I'm helpless.
> > 
> > I know all certificates should verify, but browser authors and
> > webmasters are dumb.  Honestly, I think the certificate system is doomed
> > to be broken forever, and everyone will have to use "wget
> > --no-check-certificate" all the time.
> > 
> > I would switch to another browser to view this site, but:
> > 
> >* Midori crashes all the time
> >* GNOME Web is slow and takes up too much screen space (bulky,
> >  "modern" widgets)
> >* Chromium is probably nonfree
> >* QupZilla is probably nonfree, because it contains Qt5 Web
> >  Engine, which is a component of Chromium, which is probably
> >  nonfree
> >* Lynx, Links, wget, w3m and eww shouldn't be the only options to
> >  view a webpage
> >* Links2 and Netsurf are the ugliest things on the planet
> >* Surf (suckless.org) and Uzbl are too minimalistic, and only a
> >  step up from Links2, and won't even render Riot correctly
> >* IceWeasel produces the same result
> >* Abrowser produces the same result
> > 
> > 
> > --
> > http://gnuzilla.gnu.org
> 

> --
> http://gnuzilla.gnu.org


-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature
--
http://gnuzilla.gnu.org


[Bug-gnuzilla] [Fwd: Re: search-engines can not be edited]

2017-07-30 Thread ng0
If this comes in twice, I tried to bounce the email before
but I'm not sure if it worked.
- Forwarded message from ng0 -

> Date: Sun, 30 Jul 2017 18:25:10 +
> From: ng0>
> To: David Hedlund
> Cc: ng0
> Subject: Re: [Bug-gnuzilla] search-engines can not be edited
> 
> Hi David,
> 
> David Hedlund transcribed 1.5K bytes:
> > Can you fix it?
> 
> I would rather see someone else work on this:
> In october I start with university and I'm currently
> dealing with antisocial behavior of anti-human organizations
> I depend on until this starts. Plus I'm still working on
> getting more people involved with infotropique OS.
> 
> I'm looking at mozilla code at the moment for Icedove and
> Firefox and patches related to them, but I haven't looked
> at how to fix the static search engine behavior yet.
> 
> > On 2017-04-21 21:15, ng0 wrote:
> > > ng0 transcribed 1.2K bytes:
> > > > David Hedlund transcribed 0.9K bytes:
> > > > > On 2017-01-07 23:12, ng0 wrote:
> > > > > > ng0 <n...@we.make.ritual.n0.is> writes:
> > > > > > 
> > > > > > > ng0 <n...@we.make.ritual.n0.is> writes:
> > > > > > > 
> > > > > > > > I consider this a bug in icecat, not a feature:
> > > > > > > > 
> > > > > > > > When I use firefox and add "searx" from https://about.me/about ,
> > > > > > > Correction: https://searx.me/about
> > > > > > > 
> > > > > > > This feature pre-dates firefox 45x and is still present in 49x
> > > > > > > 
> > > > > > > > I am able to later edit its url in about:preferences#search and
> > > > > > > > change the properties to set the url to an .onion address.
> > > > > > > > 
> > > > > > > > I see no reason why I this ability should be removed in icecat,
> > > > > > > > anyone got an explanation why this functionality is removed?
> > > > > > > > 
> > > > > > > > And keyword.URL in about:config is not what I mean.
> > > > > > Please consider fixing this bug in the next release, this is a
> > > > > > feature which has limits the usability of the browser.
> > > > > > I will work on a patch for myself and/or my system.
> > > > > > 
> > > > > Can you please revise your bug and re-evaluate in icecat-52.0.2?
> > > > > 
> > > > Thanks for getting back to this.
> > > > 
> > > > I will as soon as the new icecat is available on the systems I use.
> > > > -- 
> > > > PGP and more: https://people.pragmatique.xyz/ng0/
> > > > 
> > > Okay, Icecat FF52 based is now available, and I looked into this bug.
> > > It's still existing.
> > > 
> > > Unless someone beats me at fixing it, I will fix it at some point in the 
> > > next
> > > months and send a patch here (I'm not using savannah).
> > 
> 
> -- 
> ng0
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://n0is.noblogs.org/my-keys
> https://www.infotropique.org https://krosos.org



- End forwarded message -

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] search-engines can not be edited

2017-07-30 Thread ng0
Hi David,

David Hedlund transcribed 1.5K bytes:
> Can you fix it?

I would rather see someone else work on this:
In october I start with university and I'm currently
dealing with antisocial behavior of anti-human organizations
I depend on until this starts. Plus I'm still working on
getting more people involved with infotropique OS.

I'm looking at mozilla code at the moment for Icedove and
Firefox and patches related to them, but I haven't looked
at how to fix the static search engine behavior yet.

> On 2017-04-21 21:15, ng0 wrote:
> > ng0 transcribed 1.2K bytes:
> > > David Hedlund transcribed 0.9K bytes:
> > > > On 2017-01-07 23:12, ng0 wrote:
> > > > > ng0 <n...@we.make.ritual.n0.is> writes:
> > > > > 
> > > > > > ng0 <n...@we.make.ritual.n0.is> writes:
> > > > > > 
> > > > > > > I consider this a bug in icecat, not a feature:
> > > > > > > 
> > > > > > > When I use firefox and add "searx" from https://about.me/about ,
> > > > > > Correction: https://searx.me/about
> > > > > > 
> > > > > > This feature pre-dates firefox 45x and is still present in 49x
> > > > > > 
> > > > > > > I am able to later edit its url in about:preferences#search and
> > > > > > > change the properties to set the url to an .onion address.
> > > > > > > 
> > > > > > > I see no reason why I this ability should be removed in icecat,
> > > > > > > anyone got an explanation why this functionality is removed?
> > > > > > > 
> > > > > > > And keyword.URL in about:config is not what I mean.
> > > > > Please consider fixing this bug in the next release, this is a
> > > > > feature which has limits the usability of the browser.
> > > > > I will work on a patch for myself and/or my system.
> > > > > 
> > > > Can you please revise your bug and re-evaluate in icecat-52.0.2?
> > > > 
> > > Thanks for getting back to this.
> > > 
> > > I will as soon as the new icecat is available on the systems I use.
> > > -- 
> > > PGP and more: https://people.pragmatique.xyz/ng0/
> > > 
> > Okay, Icecat FF52 based is now available, and I looked into this bug.
> > It's still existing.
> > 
> > Unless someone beats me at fixing it, I will fix it at some point in the 
> > next
> > months and send a patch here (I'm not using savannah).
> 

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org


signature.asc
Description: PGP signature
--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] search-engines can not be edited

2017-04-21 Thread ng0
ng0 transcribed 1.2K bytes:
> David Hedlund transcribed 0.9K bytes:
> > On 2017-01-07 23:12, ng0 wrote:
> > > ng0 <n...@we.make.ritual.n0.is> writes:
> > > 
> > > > ng0 <n...@we.make.ritual.n0.is> writes:
> > > > 
> > > > > I consider this a bug in icecat, not a feature:
> > > > > 
> > > > > When I use firefox and add "searx" from https://about.me/about ,
> > > > Correction: https://searx.me/about
> > > > 
> > > > This feature pre-dates firefox 45x and is still present in 49x
> > > > 
> > > > > I am able to later edit its url in about:preferences#search and
> > > > > change the properties to set the url to an .onion address.
> > > > > 
> > > > > I see no reason why I this ability should be removed in icecat,
> > > > > anyone got an explanation why this functionality is removed?
> > > > > 
> > > > > And keyword.URL in about:config is not what I mean.
> > > Please consider fixing this bug in the next release, this is a
> > > feature which has limits the usability of the browser.
> > > I will work on a patch for myself and/or my system.
> > > 
> > Can you please revise your bug and re-evaluate in icecat-52.0.2?
> > 
> Thanks for getting back to this.
> 
> I will as soon as the new icecat is available on the systems I use.
> -- 
> PGP and more: https://people.pragmatique.xyz/ng0/
> 

The previous offlist-message was intended for the list:

The bug still exists in Icecat FF52 based. I will work on this eventually
in the next months, so you have plenty of time to beat me in fixing it.
If I fix it, I will send the patch here as I don't use savannah.
-- 
PGP and more: https://people.pragmatique.xyz/ng0/

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Firefox 52.0 ESR - The first Electrolysis-based ESR version

2017-03-09 Thread ng0
Gary transcribed 4.0K bytes:
> I'm not quite sure anyone realizes what it takes to maintain a small
> project like this and keep it up to date in line with a project from an
> organization with paid employees like Firefox & Mozilla -- especially
> considering how many changes Firefox has seen in recent months.
> https://www.ghacks.net/2017/03/07/cyberfox-proclaims-death-of-web-browser/
> 
> Even the ESR branch offers no guarantee of stability:
> https://www.mozilla.org/en-US/firefox/organizations/faq/
> 
> Which leads me to wonder how many people use IceCat versus how many that
> actually contribute to the project?

There are certain features which are not necessary. Yet trying to
discuss them doesn't get picked up on this mailinglist.

I don't know how many people contribute, but it will always be smaller
than the size of people who use icecat. I think even the icecat in Guix
applies more fixes than upstream icecat.
And I can understand the reasons. Not everyone has the resources to
contribute, not everyone sees certain work as easy, enjoyable, or even
worth doing. I mostly work on projects I work on because of either
interest or (mainly) because no one else was fixing or contributing
what I wanted to see as changes.
For icecat, I'm not looking to get involved, but: Is there a clear overview
of open bugs, open issues, features which need to be addressed, what can
be contributed in code, documentation, etc etc? If you presented this on
a website it could help to get more people interested in contributing.
> 
> 
> On Wed, Mar 8, 2017 at 5:03 PM, David Hedlund  wrote:
> 
> > * The current released version of IceCat is version 45.7.0 and it is based
> > on Firefox ESR 45.7.0.
> > * Firefox 48 is the first version of Firefox Electrolysis, read more about
> > Electrolysis here: https://directory.fsf.org/wiki
> > /Free_Software_Directory:IceCat_extensions_(proposed)/Resources
> > * Firefox 52.0 ESR was released 6th March: https://ftp.mozilla.org/pub/fi
> > refox/releases/52.0esr/
> > This is the first ever released Firefox ESR that is based on
> > Electrolysis, as the previous version was 45.8.0
> >
> > When can we expect IceCat 52.0?
> >
> >
> > --
> > http://gnuzilla.gnu.org
> >

> --
> http://gnuzilla.gnu.org


--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] search-engines can not be edited

2017-01-07 Thread ng0
ng0 <n...@we.make.ritual.n0.is> writes:

> ng0 <n...@we.make.ritual.n0.is> writes:
>
>> I consider this a bug in icecat, not a feature:
>>
>> When I use firefox and add "searx" from https://about.me/about ,
>
> Correction: https://searx.me/about
>
> This feature pre-dates firefox 45x and is still present in 49x
>
>> I am able to later edit its url in about:preferences#search and
>> change the properties to set the url to an .onion address.
>>
>> I see no reason why I this ability should be removed in icecat,
>> anyone got an explanation why this functionality is removed?
>>
>> And keyword.URL in about:config is not what I mean.
>

Please consider fixing this bug in the next release, this is a
feature which has limits the usability of the browser.
I will work on a patch for myself and/or my system.

-- 
♥Ⓐ  ng0 -- https://www.inventati.org/patternsinthechaos/

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Suggestions for IceCat 45.5.1

2016-12-05 Thread ng0
Jean Louis  writes:

> I am testing the version 45.5.1, and here are some suggestions:
>
> - I could see that "Sign in to sync" wanted to move me to
>   accounts.firefox.com -- maybe that could be removed from future
>   versions. Maybe FSF may provide a server for IceCat users, that may
>   store the account data, encrypted, I would trust the FSF more than
>   Firefox that has too many users and may be more under attacks.
>
> - Webpages accessible from Help section, such as
>   https://libreplanet.org/wiki/Group:IceCat/Tour and
>   libreplanet.org/wiki/Group:IceCat/keyboard-shortcuts should be
>   updated. I could provide some screenshots or explanations, or
>   somebody?
>
> - Is the IceCat creating directory ~/Dekstop ? I am not sure, but it
>   looks like it is. Why would an Internet browser have a need to
>   create irrelevant directors on user space? This is for me not
>   acceptable. I don't care about the XDG, and I am not computing in
>   the environment of XDG specifications. I have no Gnome, and no KDE,
>   so I have no "desktop environment" in that sense. Just plain window
>   manager. So in that case, IceCat should not take care of it, and
>   just leave my directories as such.
>
> - The Amazon.com shall be removed from default list of search
>   engines. That is just my proposal
>
> Jean Louis
>
> --
> http://gnuzilla.gnu.org
>

Adding to this my thread I posted last month:

Subject: [Bug-gnuzilla] search-engines can not be edited
To: bug-gnuzilla@gnu.org
Date: Thu, 17 Nov 2016 15:49:50 +

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] search-engines can not be edited

2016-11-17 Thread ng0
ng0 <n...@we.make.ritual.n0.is> writes:

> I consider this a bug in icecat, not a feature:
>
> When I use firefox and add "searx" from https://about.me/about ,

Correction: https://searx.me/about

This feature pre-dates firefox 45x and is still present in 49x

> I am able to later edit its url in about:preferences#search and
> change the properties to set the url to an .onion address.
>
> I see no reason why I this ability should be removed in icecat,
> anyone got an explanation why this functionality is removed?
>
> And keyword.URL in about:config is not what I mean.

-- 
♥Ⓐ  ng0  | ng0.chaosnet.org

--
http://gnuzilla.gnu.org


[Bug-gnuzilla] search-engines can not be edited

2016-11-17 Thread ng0
I consider this a bug in icecat, not a feature:

When I use firefox and add "searx" from https://about.me/about ,
I am able to later edit its url in about:preferences#search and
change the properties to set the url to an .onion address.

I see no reason why I this ability should be removed in icecat,
anyone got an explanation why this functionality is removed?

And keyword.URL in about:config is not what I mean.

-- 
♥Ⓐ  ng0  | ng0.chaosnet.org

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] [VOTE] Tor code base

2016-11-15 Thread ng0
ng0 <n...@we.make.ritual.n0.is> writes:

> "Daniel Quintiliani" <d...@runbox.com> writes:
>
>> Should we use the Tor code as a basis for Icecat?
>>
>> 1. Yes
>> 2. No
>>
>> I vote #1
>
> Assuming that you mean torbrowser code, where most of it is being
> upstreamed anyway, I vote #1

I change my vote to something between #1 and #2, I can't be
accurate at the moment.
In general it would not matter which browser derivation icecat
will be based on as long as more eyes are looking at its
code. Talk is cheap action is better, but I have no time to share
for icecat.
No matter which code base you choose, it would be a great
enhancement if the fingerprinting(? html5 canvas? something like
that) addon / code would be added to icecat.

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] [VOTE] Spyblock

2016-11-14 Thread ng0
"Daniel Quintiliani"  writes:

> On Spyblock, should we:
>
> 1. Keep Spyblock
> 2. Replace with uBlock Origin
> 3. Remove Spyblock
>
> I vote #2

I vote #2

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] [VOTE] Tor code base

2016-11-14 Thread ng0
"Daniel Quintiliani"  writes:

> Should we use the Tor code as a basis for Icecat?
>
> 1. Yes
> 2. No
>
> I vote #1

Assuming that you mean torbrowser code, where most of it is being
upstreamed anyway, I vote #1

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat future development

2016-08-27 Thread ng0
Additional input I just got:

The only addition which makes torbrowser use tor is the torbutton, which
I was told (currently I have no torbrowser access) can be turned off and
on.
Well this and maybe the default proxy settings, but I can't test at the
moment.

ng0 <n...@we.make.ritual.n0.is> writes:

> awake...@tutanota.de writes:
>
>> Sounds really good. we have alot to learn from tor browser. I hope it wont 
>> break functionality for normie use or we will loose alot of users. keep in 
>> mind that Tor has become severely mainstream and is likely compromised on 
>> many levels by the global elite cult that runs our country and our 
>> corporations (monsanto anyone). at this point in the world it is no longer a 
>> conspiracy theory. it is critical thought. critical fact.
>>
>> we can still learn from torbrowser, but we shouldn't ever truly depend on 
>> anyone or anything as 100% safe. remember that. we don't live in a utopia 
>> yet. that's for the next life.
>
> A good option could be a browser which can optionally enable the plugins
> which make torbrowser torbrowser (enable/disable tor functionallity),
> and (make) opt-out the plugins which can be considered useful
> (fingerprinting etc).
>
> As torbrowser is upstreaming and the release rate seems to increase,
> maybe there's a chance to either base on that or learn from how they
> base on firefox.
>>
>> --
>> Securely sent with Tutanota. Claim your encrypted mailbox today!
>> https://tutanota.com
>>
>> 13. Aug 2016 15:47 by n...@we.make.ritual.n0.is:
>>
>>
>>> Hi,
>>>
>>> I had an exchange of ideas with other people after the recent security
>>> announcement of firefox[2].
>>> The state of torbrowser was brought up in Guix as a problem and a
>>> discussion before, in the attempt to figure out how to package
>>> torbrowser compatible to our system.
>>>
>>> It was pointed out to me that the team which develops torbrowser is
>>> working together with mozilla to upstream their patchset[0][1].
>>> With this new development and the importance of networks like tor,
>>> it would be a logic choice to switch to torbrowser as upstream of
>>> icecat and follow their development.
>>> At least that's one alternative I can come up with.
>>> This will of course not be torbrowser in its original form, as
>>> adjustments are made. Wether this differs from upstream in the default
>>> unique fingerprint of the browser has to be monitored, but I am not
>>> suggesting to build another torbrowser, just to use it as a more recent,
>>> well maintained firefox codebase for icecat.
>>> For your information, torbrowser recently switched to follow a different
>>> version of firefox than in the last years.
>>>
>>> I don't know about the size of your development team, it is assumed that
>>> it is rather small? In any case, if you need help with tasks, there are
>>> certainly some people interested in helping to make the transition to a
>>> new version. Personally I have limited resources, so I can only be of
>>> limited help.
>>>
>>> I do believe that torbrowser might also benefit from this if tb is
>>> chosen as upstream and fixes are upstreamed to either firefox or
>>> torbrowser depending on the nature of the fix.
>>>
>>> I am aware that this message does not cover every detail I have talked
>>> about on other lists and off-list, but I'd like to get in contact with
>>> you on this topic.
>>>
>>>
>>> Additional question, what's needed to get into the store which icecat
>>> uses? > http://patrol.psyced.org>  is a extension which provides more
>>> functionality than https-everywhere. torbrowser 6.0.3 does not use
>>> firefox 48 as a base, but they might be working on a solution for the
>>> forced extensions+addons signing already which will start with FF 48.
>>>
>>>
>>> [0]: > https://bugzilla.mozilla.org/show_bug.cgi?id=1260929
>>> [1]: > https://bugzilla.mozilla.org/show_bug.cgi?id=1173199
>>> [2]: > http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00277.html
>>>
>>>
>>> thanks and greetings,
>>> -- 
>>> ♥Ⓐ  ng0
>>> For non-prism friendly talk find me on > http://www.psyced.org
>>>
>>> --
>>> http://gnuzilla.gnu.org
>
> -- 
> ng0
> For non-prism friendly talk find me on http://www.psyced.org
>
> --
> http://gnuzilla.gnu.org

-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Disclaimer about Smart HTTPS and HTTPS Everywhere

2016-08-27 Thread ng0
David Hedlund <pub...@beloved.name> writes:

> Smart HTTPS and HTTPS Everywhere, both these IceCat add-ons are 
> incompatible with Aliexpress.com (Alexa Global Rank 56), therefore I do 
> not any longer recommend them for general browsing experience.
>
> --
> http://gnuzilla.gnu.org

Correction / Appending: It is only for detecting certificate related
changes, so a useful software in addition to https everywhere. In
combination with https everywhere it makes the included https everywhere
safer.

Maybe even the old version of https everywhere bundled with icecat is to
blame? upstream https everywhere is now at version 5.2.3. The icecat
version doesn't even detect lists.gnu.org.
-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

--
http://gnuzilla.gnu.org


Re: [Bug-gnuzilla] Icecat future development

2016-08-18 Thread ng0
awake...@tutanota.de writes:

> Sounds really good. we have alot to learn from tor browser. I hope it wont 
> break functionality for normie use or we will loose alot of users. keep in 
> mind that Tor has become severely mainstream and is likely compromised on 
> many levels by the global elite cult that runs our country and our 
> corporations (monsanto anyone). at this point in the world it is no longer a 
> conspiracy theory. it is critical thought. critical fact.
>
> we can still learn from torbrowser, but we shouldn't ever truly depend on 
> anyone or anything as 100% safe. remember that. we don't live in a utopia 
> yet. that's for the next life.

A good option could be a browser which can optionally enable the plugins
which make torbrowser torbrowser (enable/disable tor functionallity),
and (make) opt-out the plugins which can be considered useful
(fingerprinting etc).

As torbrowser is upstreaming and the release rate seems to increase,
maybe there's a chance to either base on that or learn from how they
base on firefox.
>
> --
> Securely sent with Tutanota. Claim your encrypted mailbox today!
> https://tutanota.com
>
> 13. Aug 2016 15:47 by n...@we.make.ritual.n0.is:
>
>
>> Hi,
>>
>> I had an exchange of ideas with other people after the recent security
>> announcement of firefox[2].
>> The state of torbrowser was brought up in Guix as a problem and a
>> discussion before, in the attempt to figure out how to package
>> torbrowser compatible to our system.
>>
>> It was pointed out to me that the team which develops torbrowser is
>> working together with mozilla to upstream their patchset[0][1].
>> With this new development and the importance of networks like tor,
>> it would be a logic choice to switch to torbrowser as upstream of
>> icecat and follow their development.
>> At least that's one alternative I can come up with.
>> This will of course not be torbrowser in its original form, as
>> adjustments are made. Wether this differs from upstream in the default
>> unique fingerprint of the browser has to be monitored, but I am not
>> suggesting to build another torbrowser, just to use it as a more recent,
>> well maintained firefox codebase for icecat.
>> For your information, torbrowser recently switched to follow a different
>> version of firefox than in the last years.
>>
>> I don't know about the size of your development team, it is assumed that
>> it is rather small? In any case, if you need help with tasks, there are
>> certainly some people interested in helping to make the transition to a
>> new version. Personally I have limited resources, so I can only be of
>> limited help.
>>
>> I do believe that torbrowser might also benefit from this if tb is
>> chosen as upstream and fixes are upstreamed to either firefox or
>> torbrowser depending on the nature of the fix.
>>
>> I am aware that this message does not cover every detail I have talked
>> about on other lists and off-list, but I'd like to get in contact with
>> you on this topic.
>>
>>
>> Additional question, what's needed to get into the store which icecat
>> uses? > http://patrol.psyced.org>  is a extension which provides more
>> functionality than https-everywhere. torbrowser 6.0.3 does not use
>> firefox 48 as a base, but they might be working on a solution for the
>> forced extensions+addons signing already which will start with FF 48.
>>
>>
>> [0]: > https://bugzilla.mozilla.org/show_bug.cgi?id=1260929
>> [1]: > https://bugzilla.mozilla.org/show_bug.cgi?id=1173199
>> [2]: > http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00277.html
>>
>>
>> thanks and greetings,
>> -- 
>> ♥Ⓐ  ng0
>> For non-prism friendly talk find me on > http://www.psyced.org
>>
>> --
>> http://gnuzilla.gnu.org

-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

--
http://gnuzilla.gnu.org


[Bug-gnuzilla] Icecat future development

2016-08-13 Thread ng0
Hi,

I had an exchange of ideas with other people after the recent security
announcement of firefox[2].
The state of torbrowser was brought up in Guix as a problem and a
discussion before, in the attempt to figure out how to package
torbrowser compatible to our system.

It was pointed out to me that the team which develops torbrowser is
working together with mozilla to upstream their patchset[0][1].
With this new development and the importance of networks like tor,
it would be a logic choice to switch to torbrowser as upstream of
icecat and follow their development.
At least that's one alternative I can come up with.
This will of course not be torbrowser in its original form, as
adjustments are made. Wether this differs from upstream in the default
unique fingerprint of the browser has to be monitored, but I am not
suggesting to build another torbrowser, just to use it as a more recent,
well maintained firefox codebase for icecat.
For your information, torbrowser recently switched to follow a different
version of firefox than in the last years.

I don't know about the size of your development team, it is assumed that
it is rather small? In any case, if you need help with tasks, there are
certainly some people interested in helping to make the transition to a
new version. Personally I have limited resources, so I can only be of
limited help.

I do believe that torbrowser might also benefit from this if tb is
chosen as upstream and fixes are upstreamed to either firefox or
torbrowser depending on the nature of the fix.

I am aware that this message does not cover every detail I have talked
about on other lists and off-list, but I'd like to get in contact with
you on this topic.


Additional question, what's needed to get into the store which icecat
uses? http://patrol.psyced.org/ is a extension which provides more
functionality than https-everywhere. torbrowser 6.0.3 does not use
firefox 48 as a base, but they might be working on a solution for the
forced extensions+addons signing already which will start with FF 48.


[0]: https://bugzilla.mozilla.org/show_bug.cgi?id=1260929
[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1173199
[2]: http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00277.html


thanks and greetings,
-- 
♥Ⓐ  ng0
For non-prism friendly talk find me on http://www.psyced.org

--
http://gnuzilla.gnu.org