Someone made a pretty imo unfairly negative post about Blorp:
I just wanted to take a moment to than you all for your amazing support. I feel very lucky that I’ve made it over a year with very little negativity from my users. Everyone is overwhelmingly polite and patient.
If you have the time, I would love some comments on that post from real users. Even if the comment is politely critical of my app.
There are still many people who haven’t heard of “Blorp” and I would hate for them to get a bad first impression.
I should probably not engage with the haters. Clearly I need a marketing person lol. Maybe I’ll delete this.
Edit: my original reason for making this post was kinda dumb, but I really appreciate all the support in the comments so I don’t delete it


I agree with you here; it would be so nice to see all these talented developers working on one project in unison. I’m sure the resultant fediverse client would be a dream! I’m just not sure how we could make that happen.
At the very least we should borrow each other’s good ideas!
I’m also proud of my using post/comment/community activity pub id over local id. That makes account switching a breeze. I don’t think I’ve seen anyone else do that, and honestly I don’t think activity pub id was even ment to be used in that way.
I even do this now where if you are looking at an object that isn’t on your currently selected account/instance, I suggest what accounts you have that do know about that object. As you can see I have way too many account for testing my app lol.
Oh wow, your account switcher screen looks nice! So far, Interstellar doesn’t have any method of switching accounts like that.
Using the AP id is interesting. And you use it for users and communities too? Do you use the dedicated AP object API routes to fetch data, or do you somehow parse the AP id itself? From my personal experience, the AP object endpoints are a bit slower to return data (maybe that’s just Mbin though).
We’re currently working on adding web support to Interstellar, so we will need to make a decision on how we handle routes.
Fetch community by communty@instance works on lemmy.world the same as it works on lemmy.zip since it contains the instance the community is on. So I don’t need need to do anything special here other than enforce that @instance is always added.
Users, posts, and PieFed feeds (PieFed resolve object works with feeds) are fetched via their activity pub id. I haven’t run any benchmarks as far as how fast resolve object is.
I have added a few optimizations where if you’re on lemmy.world and the apId is lemmy.world, we can extract the local id from the activity pub id url. Potentially I could store a local cache of
Map<apId, localId>, so when you click on a post that we already know about from a list of posts, we can skip the object resolve.I think resolve object was intended to be used to force an instance to discover an object that it doesn’t already know about. So I’m kinda abusing that endpoint. But I actually get the added benefit of making the instance discover the object you’re looking for more quickly.