May I ask why? It's something that is offered on other sites like this.

Reply to post #511 (show post):
Leafmarks now has both a TSV and CSV export, does that help make any difference?

Reply to post #516 (show post):
Very sorry, but each site has different tables, despite the same file format. So, should be created a separate import for Leafmarks. Of course we took it to the attention, but did not promise that it will be soon.

Reply to post #518 (show post):
This won't help everyone, but for those that are comfortable manipulating .csv files in Excel, would it be possible to post an example table for BookLikes? They could then format the .csv file from Leafmarks to match the BL table and import data successfully.

Additionally, we really need an export function - I have no intention of leaving BookLikes, but having an export of my reviews and bookshelves is just smart. Everyone should always be responsible for their own backups. :)

We'll never have an export function, as I explained previously on another thread. It's not in BL's DNA...

Reply to post #520 (show post):
Perhaps you could share a link to the previous post on another thread so those who haven't already seen it can understand why it'll never happen.

I think Booklikes has plenty of csv and table examples from where they let us import books from goodreads, csv, lovelybooks, etc.

I also feel that a backup/export of our shelves (and eventually our blogs) is pretty vital. As much as I love booklikes when staff are actually active, it's hard to trust your book data to a site that might shutdown, lose it, or any of the other issues we've had with other sites.

I'd like to suggest a tweak to the wording on reading progress updates to get rid of the word "update" -- if it said "Reading Progress: I've read x percent" instead of "Reading Progress Update: I've read x percent" the blog heading would be a one-line title instead of a a 2-line title leaving more room for the post text to display.

It's pretty apparent it's an update on your reading progress without the actual word update. Actually, not so sure you need "I read" either.

Not a priority of course -- certainly not over shelf/book/review backup/export, bugs, performance issues, librarian needs, handling reblogs ... but possibly a very simple change.

Yes, when I remember I can manually delete 'update' but I forget frequently.

Can the Show Entire Post feature be updated to not jump to the end of the post? Instead, it would be great if it didn't change the section of the post I'm looking at. I keep having to scroll back up to where the cut was, which for some posts really ruins the intended flow as I see all the reaction gifs before I can read the text.

Reply to post #523 (show post):
I wonder if this is tied to a specific browser? I use Safari and I don't see that same behaviour; when I click "read more" it only expands the window - no jumping.

Reply to post #525 (show post):
In Chrome it started expanding upwards (losing your place) rather than downwards a few days ago.

Yeah, I can see how that would be super annoying.

Does that mean I should point it out in the Bug thread instead of the feature thread?

Reply to post #528 (show post):
I would; it sounds like it's a new behaviour tied either to a change BL made or perhaps, if Chrome was updated, a new way it handles that function. It might just need an adjustment (hopefully), and if so, it'll get done faster if you report it as a bug. :)

Thank you for all the ideas.