> I was under the impression (at least from The Register) that *office* XP was > doing this, most significantly in Word and FrontPage (I think that's what it's > called). Apparently you can overcome this by just editing the HTML directly, > and you could probably write a little macro that did it for you, if you cared.
Yeah, and alienate the bulk of the potential Windows user base. No matter what opinions we may have about Windows, the fact remains: The key to populating Freenet with a massive wealth of content lies in making Freenet accessible, convenient and technically UN-challenging to even the most unskilled of Windows users. Don't overlook what I said earlier - Word and Frontpage XP aren't the only apps that fuck with '//'. Lots of (non-M$) windows apps do that as well. ----- Original Message ----- From: "Benjamin Coates" <[email protected]> To: <devl at freenetproject.org> Sent: Monday, June 04, 2001 03:45 Subject: RE: [freenet-devl] URI Syntax - Next Generation > >From "David McNab" <david at rebirthing.co.nz> > >I reported earlier that certain Windows appz are censoring the '//' in MSK > >URIs into '/' > >A visit to www.tucows.com and other win s/w sites will quell any scepticism > >here. > > > >But just tonight in my insomnia I read on Content of Evil that Windows XP > >appz will be doing the same thing - changing '//' to '/', which effectively > >bans freesites in their present syntax. > > I was under the impression (at least from The Register) that *office* XP was > doing this, most significantly in Word and FrontPage (I think that's what it's > called). Apparently you can overcome this by just editing the HTML directly, > and you could probably write a little macro that did it for you, if you cared. > > Also note that all the crap added by MS's obfuscated HTML format triggers the > anonimity filter anyway, and probably with good reason. > > >What I *am* saying is that it could be crucial to Freenet's long term > >welfare to phase in another URI syntax, especially for MSKs. Despite the > >apparent flippancy of my previous post on the subject, I'm quite serious on > >this one. > > > >Here's a proposal for new URI syntaxes, which tunnel completely within http > >URL syntax, and won't strike any problems. No more URI encoding/decoding > >blues. No more '@' => %40 etc. > > Double slashes *are* within the HTTP URL syntax, that's why everybody's > writing those pissy articles about office being broken. > > We can't just go around changing our URI format every time someone writes a > broken application. If Microsoft is actually being incompatible with freenet > on purpose (doubtful), it's not like we can force their apps to work with us > anyway. > > >The tiny price to pay for this is that the strings 'freenet', 'chk', 'ssk', > >'svk' and 'msk' will be forever off-limits from KSK namespace. > > That seems like a pretty big downside to me! > > -- > Benjamin Coates > > p.s. Does anybody know what happens when you have office xp hyperlink to a > freenet: uri with double-slashes? > > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl > _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
