OMG I was literally about to delete the easter eggs because nobody has found them yet. There are a couple more lol

Blorp dev here. I’m not saying I will add this, but I would be open to investigating respecting the instance hide image setting within Blorp.

Makes sense! Now I understand the scope of the problem. I think I’m gonna make it just jump to the top as soon as you go to the next page with no animation.

Interesting. That shouldn’t be too difficult to fix.

Just to clarify:

• It doesn’t scroll all the way to the top (I see that)
• Does it also cut off the top of the first post in your video? Can you still manually scroll to the top of the feed?

Can you add some more detail reguarding the scroll back up not working properly? I can imagine it being broken in several ways, so I’m currous what steps you’re doing specificlly where you see this.

Alt text in post images is way easier than comment images. That makes things much easier.

Yeah that’s what I think everytime someone asks for mbin support. But I had a crazy idea. If I was able to get this to work, potentally I could get some level of support for Mastodon. Though Lemmy/PieFed will always be my main focus.

This was actually already on my planned features. I’ll bump up the priority.

How about a small timer?

Can you give me example url you would be entering into search? I think I know what you mean already, but I wanna be 100% sure.

Could you try the Dracula theme I added in v1.12.2 and see what you think? If you’re not a fan I can look into expanding the theme options, but ideally the next theme will be noticeably different from the 2 existing options.

I think that’s a good idea. I created this issue if you wanna track this work https://github.com/Blorp-Labs/blorp/issues/409

I can’t commit to anything as my primary focus is Lemmy and PieFed, but I would be open to exploring what it would look like if I remove the requirement for content to be organized into communities. That might make mbin support possible too.

Does it consistently fail on mobile? If you relaunch the app, does it sometimes work? Obviously either of those is a bug, but I’m trying to pinpoint the underlying issue.

Blorp dev here. If you did ever wanna try plugging Blorp into goofed, I’ve made it pretty easy to write “adapters” that plug Blorp into your API.

Blorp makes a lot of assumptions that could make this tricky, depending on which of these you plan on supporting:

• Resolve object endpoint is required
• Everything (local or federated) needs to return its activity pub id in API responses
• Blorp assumes content is organized into communities

But if your project happens to fit that, I’ve done a lot of heavy lifting for you already that you can take advantage of.

I think this is a PieFed API issue. See:

https://codeberg.org/rimu/pyfedi/issues/1734

Just wanna confirm does post pagination start at page 0 or page 1? Looks like photon starts at 0 but Blorp assumes PieFed starts at page 1. An API update should unblock Photon, but I don’t see a way around fixing Photon or Blorp if we don’t all agree on which page is first.

Blorp dev here. Did some investigating and it looks like Photon is asking PieFed for page 0 of posts. I’m not sure how technical you are, sorry if this is duh, but programmers like to start counting things from 0. PieFed however doesn’t seem to like this.

Here’s what I think is happening:

• Photo asks for page 0 of posts
• PieFed says “there are no posts at page 0”
• Photon thinks if page 0 is empty, then there is no page 1

What should happen:

• Photo should ask for page 1 of posts
• PieFed will respond “there are 25 posts on page 1”
• Photon says page 1 is full so page 2 must have content
• Photon then asks PieFed for page 2 of posts
• …etc until we run out of pages of posts

In other words, page 0 is a short circuit that prevents the entire feed from loading

CC @[email protected] @[email protected] (photon dev)

Or maybe we wanna fix this at the API level? @[email protected] @[email protected]

Let me know if you have any questions! Even if those questions don’t turn into PRs I’m sure I can improve documentation.

The ionic stuff mostly affects page layout and routing. If you ignore ionic and just consider the page contents, it’s just good old react + a little of my spaghetti code.

Hmmm either your account got mislabeled as a bot or you’re a bot. Suspicious

Blorp only has 1 dev (for now), but if you interested in contributing, don’t be a stranger! And let me know if there’s anything I can do to make Blorp better for you.