you've probably figured htis out in 4 weeks, but I don't see a reply so I figured I'd document it for someone else.

A thread is posted to one magazine, while a microblog is posted to the whole fediverse.

To see your threads a user has to be subscribed to the magazine in question (or on some platforms at least one user on the remote instance does), while to see your posts a user has to follow @srasmus@fedia.io

So a new thread is a new lemmy (or Reddit) post, while a post is a new toot/tweet.

A lemmy user can't see the posts to your microblog, a mastodon user won't see your treads unless they "follow" the "user" @askmbin@fedia.io and it looks kind of janky, with every post/reply looking as if the magaize user is re-tooting it.

Magazines (Communities) easily searchable. Lightning fast feeds (subscribed and federated)

For me at least it's these things:

• good integration of microblogs, so interacting with a bigger part of the fediverse
• a good UI that is customizable (subjective)
• useful notification settings (per user, per magazine)
• following users

Fedia seems like Infosec pub and Lemmy Cafe

So, I just checked for about ten pages on Opera mobile, and it seems to be working fine now.

So, as a check, today I've kept a Fedia tab open pretty much the whole day, on the combined page. I scrolled through it during the day, every time goin to the next page. No "you've reached the end" or missing navagation pane in sight. So right now it seems it's because I normally browse the threaded view that I'm having issues.

No worries, just keeping stuff posted here. I will be following up if you want me to.

quick edit: While the main threads page doesn't show the navigation, the combined page does.

I am very sorry that it is not working great for you... I don't know why this should happen. I will investigate it over the next few days and if it cannot be fixed easily we'll bring back the old pagination style until it is fixed

And just now the front page ended without the lower navigation part (laptop, Firefox), inspected it and made a screenshot.

Just had it on my laptop, using Firefox, end of fourth page gives the "you've reached the end" message. Went to the home page again, clicked through, this time it's five pages. Link to the last page for me. Picture added.

It was on the front page, Opera mobile as browser. I have the languages filtered to English German and Dutch, the rest are at default settings.

Well if you're in a magazine it might be true... I havent encountered it myself and I've been using it for a while. Can you tell me where you've looked and what your filters and sort look like?

Ok, I guessed so. But what about the quirk where I don't get the arrow, or where it says after page two I've reached the end?

Nope the page numbers are gone. We shifted to a different kind of pagination that is called "cursor pagination". You cannot tell how many "pages" there are and you cannot tell on which page number you'd be with this kind of pagination. The reason we changed it is because it is (in our case) over 100 times faster than the old pagination. (not saying the page loads a hundred times faster, but it is a lot faster. The time this is referring to is the database query time)

No there is not one, yet. I do have importing and exporting sub, follows, etc. on my Q1 roadmap, but exporting posts and comments is not in there. I think that would be more of a niche feature

On a post has a link attached, you can click "show more from domain" in the more menu. Id you're on that page, which is /d/YOUR_DOMAIN, you can hit the block button in the sidebar

Right now we do not have a way of blocking an entire instance. You can block a domain, so all posts linking that domain get removed, but that is not what you are looking for I think

I have 7 pages on my blocklist of just the weather accounts before I gave up

There is now a poll for this topic.

There is now a poll for this topic.

LOL, I didn't realise you are one of the developers last night, but thanks for noticing!

There is now a poll for this topic.

Please, please add a toggle. For now, I'm just blocking everyone I see posting microblog content. This is obviously not a sustainable solution.