Simon Jolle:

I requested a Debian Package for Flatpress, see http://bugs.debian.o … eport.cgi?bug=466297.

Feel free to add comments to this open wishlist request

That’s cool, thank you :)

On Monday I’ve committed the hash thingie; it seems to be working nicely.

Also, I’m almost officially a thesist, and, can you guess? The thesis will involve FlatPress.

We have to still define the details but it will probably involve rethinking and rewriting the indexing system (which is still quite crappy), and maybe multiuser support, so you’ll fianlly stop asking when it will be there :P

Supporting more than one user, despite what you might think, is anything but a trivial task, and not because I’ll have to handle registrations for users, but because of the usual concurrency problems, which at the moment aren’t critical.

So it might end that those damn Petrinets will come in handy after all.

Now I’ve only to pass this 3 exams.

Please be nice to me, I’m very busy :P

Connected with the new hashing algorithm in SVN I had some problems upgrading my own personal blog www.nowhereland.it, so I had an idea (not yet implemented but it will be soon) which should avoid it.

Salt for the hash is now calculated using a combination of some constants, which are (IIRC :D) the blog url, and the absolute path on the server.

The major problem with this algorithm is that if you’ll ever have to move from a server to another you will have to re-create your user.

Moreover yesterday I discovered something can vary also in other situations, I’ll have to investigate.

So here’s the hack: the salt will be generated once and the stored in a file which will be in your fp-content/config/ (hashsalt.conf.php)

The file won’t be word-readable as the other conf files aren’t (it’s php, so if you call it it won’t be printed but executed, and the execution doesn’t generate any output), and will contain the string which will be the salt to encode passwords.

Moreover you’ll be able to edit this salt by hand for additional strength :)

Aside: on Monday I’ll be talking to one of my professor, and see if FlatPress can be object of my thesis :)

We’re on OpenSourceCMS

:)

Why is this cool? Because there is now a demo page, so you can test FlatPress live!

Have fun!

Aside: I wonder who asked for adding us to the list, as Samy, Drudo and a bunch of other people kept on asking me when I was going to do it; I’ve always answered I wanted to release Crescendo+1, first.

Well someone was quicker than me :P

I’m sooo lazy. So lazy that I should be studying right now, so I go back to my books, bye!

As you know FlatPress provides two “permalinks”, one with comments and one without them.

Since its birth FlatPress tried to be an (almost… not fully :P) drop-in replacement for SPB, so the main “windows” on the rest of the world stayed the same: index.php, comments.php, static.php, rss.php.

Now, many of you begged for our beloved prettyurls, which required - in order to make it painless (really “less painful” :D) I’ve finally decided - as SVN users should have noticed - to centralize the whole link affair on index.php

Now, for people who don’t like/don’t want/can’t have pretty urls there’s a question to be answered.

static pages are identified by the ?page= parameter, permalinks with ?entry= parameter; RSSs with feed=FEED-ID (where feed id is rss2 or atom: cool, isn’t it?).

Now, how should comments be identified?

For now it’s ?entry=entry123456-123456&comments, but I kinda dislike how that looks.

i.e. http://www.flatpress.org/home/?entry=entry123456-123456&comments # this is just a sample url

note: most of the times this will look like

http://www.flatpress.org/home/?entry=entry123456-123456&comments#comments

with the anchor to the comment list. now *that* looks ugly. Any suggestions?

I ask you because once decided it will *stay* that way.

note: I don’t know if any of you noticed you can now subscribe individual comment feeds, just append to your entry &feed=rss2 or &feed=atom :)

i.e. http://www.flatpress.org/home/?entry=entry123456-123456&comments&feed=rss2

Discuss commenting here or on the forum