Abstracting storing files, like:

- LocaStorage (stores files on local directory
- WebDavStorage (stores files on any WebDAV, let's make a simple WUI here for NextCloud/OwnCloud configuration to encourage people using it)
- SftpStorage (stores files over an SFTP link)
- FooStorage (stores files the foo-way)

And many more. So how to procede?

If one has a path for storage, you can let the OS figure out what it is.

eg, Friendica looks in a directory called /storage

This can literally be a directory called /storage...or you can add an fstab entry to add an arbitrary type of remote file system mounted at /storage.

And pushed, tomorrow morning, around for an hour there will be no electricity here, they work on the cables outside and our house number is affected. So I shutdown my computer now (which will ruin the uptime again).

$ uptime
 23:18:08 up 36 days,  3:21,  4 users,  load average: 0.35, 0.55, 0.59
$

Good bye and until tomorrow!

Yesterday I had a look at the jquery plugins you mentioned. github.com/pixelcog/parallax.j… is not about infinite scrolling. It is about to have a prallax effect. And github.com/fredwu/jquery-endle… doesn't do that much more than our implementation already do (OK it can load previous pages).

The problem isn't to load next or previous pages through ajax. That would be very simple.

The problems we would have to deal with are:

• which posts belong e.g. to page 1 (which should be removed from the screen when we scroll e.g from page 2 to page 3)
• how do we deal with the situation when new posts arrive (e.g. the user would be on page 3 - a new post does arrive, and he/she scrolls to page 4 - I guess in this situation the first post of page 4 would be missing)
• how do we deal with comments on posts (wich would move the post on top of the first place

The whole topic is very complex. I think this is not something which is easy to implement. I don't want to say that it is unsolvable, I just want to highlight that this "extended" infinite scrolling is more than just adding and removing content

Just using a request parameter, like "page" is not helpful, then you will may see duplicate posts as "page=2" will change when new posts are being added. #GNUSocial uses here something like "lastPostId" which is the id number of the last post that has been loaded and so displayed.

Maybe I better make an example on how I think how it can be done:

1) Load page and embed "last post id" directly into page
2) Send request out: "POST /ajax/network/?lastPostId=12345&page=current"
3) This returns the posts (lastPostId - postsPerPage) that just be displayed right away including a new lastPostId
4) The user scrolls up, send another request out: "POST /ajax/network/?lastPostId=12335&page=up" (I assumed 10 posts per page and again a new lastPostId is included)
5) On any of those requests, check that more can be loaded, if not, the new lastPostId should be empty, indicating that no more can beloaded
6) Similar when the user scrolls down, then &page=down is given

Maybe not perfect but newly added posts can be found out the same way:
"POST /ajax/network/?lastPostId=12345&page=up (as newer posts are added on top)

The JavaScript then needs to handle empty lastPostId (when < postsPerPage has been found) and removing/adding content.