Florent Daignière (NextGen$) wrote:
> * David McNab <[EMAIL PROTECTED]> [2006-05-08 14:10:31]:
>
>> Ian Clarke wrote:
>>> On 7 May 2006, at 18:04, David McNab wrote:
Ian Clarke wrote:
> So websites that use this will only work with users that have Firefox
> and have installed the plug
* David McNab <[EMAIL PROTECTED]> [2006-05-08 14:10:31]:
> Ian Clarke wrote:
> > On 7 May 2006, at 18:04, David McNab wrote:
> >> Ian Clarke wrote:
> >>> So websites that use this will only work with users that have Firefox
> >>> and have installed the plugin?
> >> ...
> >>> Isn't it preferable t
Ian Clarke wrote:
> On 7 May 2006, at 18:04, David McNab wrote:
>> Ian Clarke wrote:
>>> So websites that use this will only work with users that have Firefox
>>> and have installed the plugin?
>> ...
>>> Isn't it preferable to encourage people
>>> to use the normal http://127.0.0.1:/ prefix?
On 7 May 2006, at 18:04, David McNab wrote:
Ian Clarke wrote:
So websites that use this will only work with users that have Firefox
and have installed the plugin?
...
Isn't it preferable to encourage people
to use the normal http://127.0.0.1:/ prefix?
Seems we've got two imperfect optio
Ian Clarke wrote:
> So websites that use this will only work with users that have Firefox
> and have installed the plugin?
...
> Isn't it preferable to encourage people
> to use the normal http://127.0.0.1:/ prefix?
Seems we've got two imperfect options:
1) Dump user into a sea of broken lin
This worries me, as it has worried me every time someone has
suggested it (it is suggested about once every 6 months on average):
On 7 May 2006, at 14:48, David McNab wrote:
A 2-minute recipe for getting Firefox to handle 'freenet:'-style URLs,
so that mainstream web pages can link to freesite
FIXED!
Synopsis:
A 2-minute recipe for getting Firefox to handle 'freenet:'-style URLs,
so that mainstream web pages can link to freesite pages without worrying
about fproxy access specifics.
Purpose:
---
Allow mainstream websites to contain abstracted freenet links such as:
hot
