

Blorp dev here. Sorry for the silly name, but I assure you I’ve spend hundreds of hours making Blorp the best app I possibly can. It’s totally free, fully open source, and it doesn’t log any of our data. I would love for you to give my app a try!


Blorp dev here. Sorry for the silly name, but I assure you I’ve spend hundreds of hours making Blorp the best app I possibly can. It’s totally free, fully open source, and it doesn’t log any of our data. I would love for you to give my app a try!


Fuck you Jenny
Yeah it’s pretty much just me. Except for the app logo, which was done by @lay@piefed.social


Does girth similarity affect their ability to jerk different dicks simultaneously?
I think what’s happening is the app is refreshing in the background, and it’s not smart enough to tell the difference between initial launch and background refresh. I would either have to think of a solution to tell the difference, or have a toggle to disable automatic refresh entirely, so you always have to pull to refresh. But even I solved the refresh issue, I think it will still throw you to the top of the feed :/
The earth is flat, but its flat in spherical spacetime. Checkmate atheists
This might be tricky then. I’ll do some poking around and see if there are any obvious performance improvements I can make. But no promises
Is it worse on posts with more comment? What happens if you open a post with 0 comments?
Anything specific or just everything? Admittedly, I don’t spend enough time testing Blorp on older phones.


Blorp dev here. Comment are virtualized. That means anything that isn’t currently in view can get unmounted to keep the comments page super snappy. For small posts, this is definitely overkill, but it means we can smoothly render posts with thousands of comments.
I’ve kinda been waiting for someone to complain about this for me to fix it. What I’ll likely do is implement a custom search box that is compatible with the virtualized comments. I have a lot on my plate rn, but I’ll get this fixed as soon as I have time. Sorry for the inconvenience.


And Google Play, and F-Droid, and web, and macOS. We also support Lemmy, and you can login to Lemmy and PieFed simultaneously.


Only the best Lemmy/PieFed client of all time. Which is my definitely unbiased opinion as the creator of Blorp.


Good catch! I’ll see if I can fix that in the next release of Blorp.
Edit: on second thought, let me double check what other Lemmy/PieFed clients do. I would hate to encourage users to use a syntax if it looks broken on other clients. In general, if the official UI supports something then we will support it.
I’m totally guessing but I’m guessing it’s more similar to:
Block if risk of abuse exceeded X%
I have no idea what I’m talking about, but I can’t imagine these companies aren’t using some pretty advanced detection of bot traffic
In my experience, many Lemmy instances block what looks like bot traffic. I don’t think it’s as simple as VPN = blocked, but that’s probably one of the signals they pay attention to. I’ve noticed most comments will fail to post when I’m using Mullvad.
What was the dealbreaker with Blorp and how can I make it better?
If you ever do find yourself using a second account, I’ve spend a lot of time perfecting multi account on Blorp. Nice if you wanna use Lemmy and PieFed. I’m pretty confident that you won’t find a Lemmy/PieFed client out that that will switch accounts as seamlessly Blorp. For example, Voyager is one of the best apps out there, but it will close any open posts or communities when you switch accounts. With Blorp, you can switch accounts and continue exactly where you left off.