On Saturday 12 December 2009 15:19:23 alex wrote:
> Hello,
>
> for some time I've been thinking about points that make me disconnect from
> freenet from time to time. One of them, I think, is that once you manage to
> connect, you feel quite alone in there.
>
> Freesites are static in nature, there's a feeling that you're in the middle
> of the night and here and there you stump into unrelated freesites. Index
> sites mitigate somewhat this feeling, but not much. Frost and FMS, they're
> not trivial to setup nor in the web interface.
>
> Sure, I lurk in the dev mailing lists. That's great since I see activity
> and community there. But, putting myself in the shoes of an average user (in
> the end, I'm a techie), that's only trying freenet via the web interface, I
> think there's something (that many other projects do) that could do, with
> little effort, much to diminish the feeling that freenet is a bunch of
> freesites.
>
> I'm namely proposing to add to the freenet interface (in the welcome page
> or a dedicated page) an official announcement section, where the freenet
> team publish news related to the project. Basically, the same updates that
> go thru dev, could be distilled in a (weekly?) post that the node would
> present to the user.
>
> This way one feels that things are moving even without having chat yet, nor
> subscribing to mailing lists. Plain users would have quick access to a
> minimal but regularly updated "what's happening with freenet" page,
> sanctioned by the devs. I'm not talking about entering into conflicting
> debate or technical detail, just plain understandable updates that show
> that the project is well alive and moving along.
>
> What do you think? I know that some freesites are sanctioned and linked in
> the "browse freenet" page, but I'm aiming at something even more basic:
> "the" freenet team news. A "latest news" section.
Ways to implement this sort of thing (which is probably a good idea):
1. Official Freesite. The problem is people will trust it, so if the private
key were ever leaked we'd be in deep trouble. The fix for this is Revocable
SSKs. This will happen eventually. There are easy ways to do RSKs and hard
ways, but we can do a reasonably easy way which is forward compatible.
2. Per-build update notes. We could either include a file with the build, or
insert it as a CHK and have the node fetch it. We could display it as a
dismissable alert or something, and have it come back when the next build comes
out, unless the user tells it to go away forever.
3. Something in between. An official SSK containing regular updates, for
example. This has the same revocation problems as an official freesite,
although there are easier solutions than RSKs, such as just tying it to the
auto-updater (which has its own revocation mechanism).
signature.asc
Description: This is a digitally signed message part.
___
chat mailing list
chat@freenetproject.org
Archived: http://news.gmane.org/gmane.network.freenet.general
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/chat
Or mailto:chat-requ...@freenetproject.org?subject=unsubscribe
