; weak
> > point in the whole proxy/http/url's idea: if freenet has URLs, external
> > websites will be able to probe browser history's for them, therefore we
> > should not have a simple proxy at all, at least not without warning the
> > user
> > and asking for an explicit override.
> >
> >> -CPD
> > ___
> > Devl mailing list
> > Devl at freenetproject.org
> > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>
> ___
> Devl mailing list
> Devl at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/5c87d5b7/attachment.pgp>
available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/0d197ccd/attachment.pgp>
out warning the user
and asking for an explicit override.
> -CPD
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/227dccf8/attachment.pgp>
-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/927762f4/attachment.pgp>
ring.
Make freenet more "transparent" where a certain domain would correlate to a
freesite such as *.free or something that isnt in use on the internet. Anonet
has used this and it works great
I know that there's limited bandwidth out there, but if Freenet could use it a
bit more efficiently... And I would consider 'moving' the node towards
content it requested, rather than 'positioning' it depending on content it
provides.
Allow Freenet to be paused/suspended for when full processing power is needed
by other apps e.g. when gaming.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/ce7cb223/attachment.pgp>
install it
> first.
Since additional deps and bundles can always cause additional problems, my vote
then goes to option
2: Use javascript to handle it and add a note about using a different
browser/profile with disabled
javascript. On the other side, it would be nice to have as much as possible
implemented without the
need of javascript.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 315 bytes
Desc: OpenPGP digital signature
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/eb04e393/attachment.pgp>
Forgive my being naive, but couldn't you remove that vulnerability by
adding a nonce to the URL string?
As I understand to exploit the history trick, you need to be able to show
the page and check the css-color against a visited link.. If the fproxy
request went to
application/pgp-signature
Size: 315 bytes
Desc: OpenPGP digital signature
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/13fdafcf/attachment.pgp>
ng except windows), we'd have to ask the user to install it
first.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/1aae8fd8/attachment.pgp>
> -Original Message-
> From: devl-bounces at freenetproject.org
> [mailto:devl-bounces at freenetproject.org] On Behalf Of Matthew Toseland
> Sent: Wednesday, December 31, 2008 5:22 PM
> To: devl at freenetproject.org
> Subject: [freenet-dev] How to solve the browser problems
>
> 3.
te of development
> time.
Then which option do you prefer?
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/5a284f7a/attachment.pgp>
t poorness of the web interface.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/1c17f070/attachment.pgp>
or it ... doesn't that suggest they would use it?
>
> > IMHO offline mode is a good idea, especially when combined with a systray
> > icon. It would also help with e.g. connections that are throttled or
billed
> > severely at certain times of day.
>
> There is a branch for "bandwidth-scheduling" in svn
> (https://emu.freenetproject.org/svn/branches/bandwidth-scheduler) is
> wavey still around and working on it? what's its status?
AFAIK wavey disappeared. :|
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/4551ef2d/attachment.pgp>
ature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/e9b2e5d4/attachment.pgp>
: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/18629931/attachment.pgp>
ed or billed
> severely at certain times of day.
There is a branch for "bandwidth-scheduling" in svn
(https://emu.freenetproject.org/svn/branches/bandwidth-scheduler) is
wavey still around and working on it? what's its status?
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/6968cd18/attachment.pgp>
rg/wiki/DADVSI
My recommendation is to exercise your right as an EU citizen to move to and
work in another country of the EU. :)
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/b11c3211/attachment.pgp>
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/24f358a1/attachment.pgp>
--- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20081231/86c68f8b/attachment.pgp>
I really think option 2 is the by FAR the most user friendly, for quite
a few reasons-
1) Software shouldn't be ill-behaved. I'm a large advocate of and for
Freenet, and even I get quite annoyed when freenet alters Firefox by
creating a new profile. I understand the rationale, but one software
#1: 41 votes : release the 20 nodes barrier
most of the users nowadays have a lot of upload-bandwith available. Myself
has about 3Mbits upload, but the limit to connect to not more than 20 nodes
results in about 50kb/s max. Please release the limit or use a dynamic system
that offers more
I'm very sorry to hear this. Hope you can find some way to contribute
in the future (perhaps anonymously?) Thank you for all your work on
WoT; it's a good system and I think it and Freetalk show a lot of
promise. We'll keep up the fight.
Benjamin
___
On Sunday 28 December 2008 09:55, Florent Daignière wrote:
* juice...@freenetproject.org juice...@freenetproject.org [2008-12-28
02:49:25]:
Author: juiceman
Date: 2008-12-28 02:49:24 + (Sun, 28 Dec 2008)
New Revision: 24804
Modified:
On Sunday 28 December 2008 14:14, Julien Cornuwel wrote:
Ed Tomlinson a écrit :
On December 27, 2008, Julien Cornuwel wrote:
I'm sorry to tell you that for some legal reasons (I live in France), I
have to stop working on Freenet. I've learned a lot with you guys and
I'm sad to have to say
We have a lot of complaints on the uninstall survey about the firefox breakage
bug. IMHO we should deal with this as soon as possible. The easiest way to
deal with it is to periodically and/or after firefox exits, check the
profiles.ini file to see whether the freenet profile has become the
Matthew Toseland schrieb:
We have a lot of complaints on the uninstall survey about the firefox
breakage
bug. IMHO we should deal with this as soon as possible. The easiest way to
deal with it is to periodically and/or after firefox exits, check the
profiles.ini file to see whether the
On Wednesday 31 December 2008 16:34, Tommy[D] wrote:
Matthew Toseland schrieb:
We have a lot of complaints on the uninstall survey about the firefox
breakage
bug. IMHO we should deal with this as soon as possible. The easiest way to
deal with it is to periodically and/or after firefox
Matthew Toseland schrieb:
On Wednesday 31 December 2008 16:34, Tommy[D] wrote:
Matthew Toseland schrieb:
We have a lot of complaints on the uninstall survey about the firefox
breakage
bug. IMHO we should deal with this as soon as possible. The easiest way to
deal with it is to
I really think option 2 is the by FAR the most user friendly, for quite
a few reasons-
1) Software shouldn't be ill-behaved. I'm a large advocate of and for
Freenet, and even I get quite annoyed when freenet alters Firefox by
creating a new profile. I understand the rationale, but one software
On Wednesday 31 December 2008 20:53, Matthew Toseland wrote:
First the main reasons:
Not enough interesting content 1509 : 31%
I was not able to get it running! : 1050 : 22%
It takes too long to retrieve content from it 771 : 16%
It slowed down my computer 612 : 13%
It worked initially,
On Wednesday 31 December 2008 18:14, Colin Davis wrote:
I really think option 2 is the by FAR the most user friendly, for quite
a few reasons-
1) Software shouldn't be ill-behaved. I'm a large advocate of and for
Freenet, and even I get quite annoyed when freenet alters Firefox by
On Wednesday 31 December 2008 18:03, Tommy[D] wrote:
Since additional deps and bundles can always cause additional problems, my
vote then goes to option
2: Use javascript to handle it and add a note about using a different
browser/profile with disabled
javascript. On the other side, it
Hello,
some little french translation
sich
FNPPacketMangler.somePeersDisconnectedStillNotAcked=Probablement un bug :
veuillez faire le rapport suivant : ${count} noeuds ont été déconnecté de
force car les données ne sont pas reconnues.
Forgive my being naive, but couldn't you remove that vulnerability by
adding a nonce to the URL string?
As I understand to exploit the history trick, you need to be able to show
the page and check the css-color against a visited link.. If the fproxy
request went to
On Wednesday 31 December 2008 23:19, Colin Davis wrote:
Forgive my being naive, but couldn't you remove that vulnerability by
adding a nonce to the URL string?
As I understand to exploit the history trick, you need to be able to show
the page and check the css-color against a visited link..
On Wednesday 31 December 2008 23:37, Matthew Toseland wrote:
On Wednesday 31 December 2008 23:19, Colin Davis wrote:
Forgive my being naive, but couldn't you remove that vulnerability by
adding a nonce to the URL string?
As I understand to exploit the history trick, you need to be able
36 matches
Mail list logo
