Timeline streaming fails on Pleroma

[iero]

Hello

I want to read every toot I receive. So I would like to have an option for hyperspace to load the new messages without auto-scrolling to the newest.

Thanks

[issue-label-bot]

Issue-Label Bot is automatically applying the label enhancement to this issue, with a confidence of 0.63. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[alicerunsonfedora]

Is this for messages specifically or for a timeline?

Edit: I just want to be sure that I'm understanding your request correctly.

[iero]

Thanks @alicerunsonfedora for the question, it's for the 'Home' timeline.
I let Hyperspace on a virtual desktop.

When I have time to read a few messages, I would like to be able to scroll them (from the last read message) and continue reading later.

[alicerunsonfedora]

Is this with version 1.x or 0.x? The auto scroll you are talking about might be a bug from 0.x and should be resolved in 1.x.

_{Sent with GitHawk}

[iero]

I'm using 1b5.

In fact, if you scroll up to the top, you are automatically in a "autoscroll" mode (that you can disable if you just scroll down a little bit after).

I would like to disable this autoscroll with an option and see somewhere (in the app or as notification on the icon) that I have new messages to read.

[alicerunsonfedora]

Hmm, that sounds more like a bug and not a feature. You should be remaining in your place when new posts are loaded. That is, unless you are referring to what happens when you click the "Load x new posts" chip.

[alicerunsonfedora]

It seems that I am unable to replicate what you're describing as of the latest version of Hyperspace.

• Does this occur when you're just viewing posts?
• Does this occur when you click the new posts chip (see screenshot below)?

[iero]

Thanks !

When I'm in the standard Timeline view, I have not any "View 11 new post" item. The view is automatically updated to the newest post:

[alicerunsonfedora]

Ah, this appears to be a bug, then. Triaging as timeline defaulting to 0.x behavior unintentionally.

[iero]

Ok, I logged to mastodon (was logged on pleroma instance before) my account and I now I have the "new post" item.

But When I click on it, I jump to directly the newest and I need to scroll back to read the others.

I want to scroll from the "current one" to the newest.

[alicerunsonfedora]

The "Show new posts" button isn't quite intended to keep the scrolling position, and I'm not sure if that's what we want to accomplish at the moment since keeping the scroll position is rather difficult.

However, the fact that the button does not show on Pleroma is concerning. Will need to be added to the Pleroma list.

[alicerunsonfedora]

It does appear that the streaming APIs aren't working correctly on Pleroma, and I'm assuming this is due to the way streaming is handled in Pleroma.

[alicerunsonfedora]

As an update to this particular issue, it appears that the site we're testing from, pleroma.site, doesn't have streaming implemented as the following is returned:

{"error": "Not implemented"}

[alicerunsonfedora]

To reiterate from #65:

The streaming issue from my initial tests appears to be a problem with Pleroma not having streaming in this manner rather than an issue with Hyperspace. Attempting to switch to WebSockets also causes some issues on the browser side of things, namely due to the way Megalodon seems to handle them.

I'm guessing that streaming via HTTPS will make it to Pleroma sooner or later, but it appears as if other important features work just fine. For now, I'm going to mark this as complete.

[iero]

FYI I opened a case on Pleroma's git for that:

https://git.pleroma.social/pleroma/pleroma/issues/1468

[feld]

To clarify, Pleroma supports websocket streaming not the original Mastodon API SSE streaming. I thought I heard Mastodon was deprecating the SSE streaming, but I'm not a spokeperson for that project and am not certain. It's worth verifying in case your app relies on SSE streaming support.

[alicerunsonfedora]

Hyperspace does use HTTPS streaming (supposedly SSE, if worded) as we use the Megalodon library to access Mastodon. I haven't heard anything about Mastodon deprecating SSE streaming.

I'm hesitant to see about switching the client to use the web socket version as I'm not sure how well Safari will handle it, but it up for discussion. I recommend getting a new issue filed for it on board so it appears on our radar/internal tracker.