On Tuesday 27 January 2009 11:00, Florent Daigniere wrote: > 3BUIb3S50i 3BUIb3S50i wrote: > > md at BngcNVtC0qdeg2HmgSSs8jHVbYAomT8nQ0Pvx1NQ0Ks wrote: > >> How do I delete a freesite? I changed the name but I don't know how to > >> delete the "old" version. > > > > saces at foqoipX8V3aio7B~tNoxFmRutrcVHixhlAXB2WpFoeU wrote: > >> delete is an importand feature for censorship, so such operation does not exist in freenet. > > > > falafel at IxVqeqM0LyYdTmYAf5z49SJZUxr7NtQkOqVYG0hvITw wrote: > >> This raises an interesting question: > >> > >> On the regular internet, you have HTTP error codes to indicate different > >> statuses of freesites: > >> > >> http://en.wikipedia.org/wiki/List_of_HTTP_status_codes > >> > >> In particular: > >> > >> 301 Moved Permanently > >> This and all future requests should be directed to the given URI. > >> > >> I think Freenet needs to provide a way for a freesite to trigger FProxy > >> to send a 301 redirect to the browser, and also a corresponding redirect > >> in FCP. > >> > >> It confuses things somewhat that FProxy talks to the node using some > >> hidden internal protocol - I think it should be more separate from the > >> node and use FCP to communicate with the node. > >> > >> In particular, we want freesite spiders and indexing engines to know that > >> the old site is dead and to include the new URL instead. When we get > >> clever about it, it can be used to retain the original site's ranking too. > >> > >> How could such a thing be done? > >> > >> What if you just reinsert the site as a redirect to the new freenet URI? > >> This would appear in FCP to be distinct from a mere redirect to a newer > >> version of the same key. > >> > >> Does that make FProxy send a 301 redirect message to the browser? > > > > The Tech mailing list is the place where we discuss long-term, freenet > related issues; Not the place where users are expected to make feature > requests. > > Please stop it.
You'd rather they made them on devl? > > NextGen$ -------------- 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/tech/attachments/20090127/74affde9/attachment.pgp>