On Monday 23 June 2003 10:23 am, Some Guy wrote: > Ok, it's my first Post here let's hope it turns out ok. > > Yeah, I agree with Josh if people agreed to use the same little template > pics those pics would be common enough. What I would suggest doing is > making a nice freesite with cool art that everyone will want to use. Call > it "please rip off my site" PROMS. > > Tom's idea did have an interesting feature: that people could personalize > these little icons. If someone really wanted this maybe we could just > consider making some kind of a config file where the user can set up > replacements like replace HSK A with HSK B, so he can have his B style look > and feel. > > I don't see this being worth the trouble. Then again it doesn't seem that > hard to do either. Maybe someone could point out another reason for doing > this. > > Chris > > > > Josh Steiner <[EMAIL PROTECTED]> wrote: > just publishing it on the freenet at large would be nearly as effective, > and as todd mentioned i doubt this should be included in the actual > freenet.zip's to keep installer from getting bloated. if mulitple sites > started sharing the same clip art then files would be really well > established on the network and hence should load quickly.
It doesn't need necessarily be included in the freenet zip. What I'm proposing is essentially a much less invasive alternative to containers. I could publish a "please rip off my site" site, but it would contain hundreds of VERY small images. No matter how widely distributed it is, it is just not worth making a network request for 100+ images that are less that 100 bytes. This is why you rarely see this (even on the normal WWW). Now if fproxy implemented transparent unzipping, as discussed in the 'containers' thread. That would solve the problem. However that is a big hassle, and has a lot of potential for poor use. What I'm proposing is NOT to load all the images into fproxy like the existing images (where they would take up memory and be version dependent), But rather if fproxy did a simple string replace on "http://127.0.0.1:888/images/"; and substituted "file://$FREENETDIR/images/". Then the rest would be for the browser to sort out. This is far simpler than substituted HSK A for HSK B and would have virtually no overhead in fproxy. _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
