moseschrute

1. NSFW is a big issue, and I’m really sorry to everyone that I missed that. I’m going to try and get a fix up for that tonight, but it could take a day or two to roll out
2. I actually cache pretty aggressively, but what you’re describing is likely when I chose to load the next page. For example, it might say, “when you’re 50% through the currently feed of posts, fetch the next 50”. This could probably be tuned a little better.

For the second issue, could you compare the loading time against Lemmy.world in Blorp? It’s probably the way I’m paginating, but that will rule out 100% that it’s an issue with Blorp and not a slow response from PieFed.

Thanks! A couple changes may need to be made, so you can configure it how you like. Feel free to open an issue if you notice anything missing. Check the .env.example to see the existing options

That just Lemmy doing Lemmy things lol. Because I support Lemmy and PieFed, idk if I want to change the default to PieFed at the moment. But if you were interested in hosting blorp.piefed.social, I can help you set it up with piefed.social as the default instance.

Edit: My biggest concern with default instance is another lemm.ee scenario where the instance shuts down.

I need to fix that. I was thinking about just hiding the down arrow, but if you think I heart is better, I can try that. But the score should still be shown next to the heart, right? Unless score is hidden. I’m thinking I put the heart to the left of the score.

Yeah that’s a bug I really need to address, sorry. I’ll bump that to the top of my priorities. Realistically I won’t have a fix for that until mid week.

Blorp dev here. PieFed support has been added. See announcement post

That means a lot! I’m pretty proud of what I’ve built, but there is still a lot of room for improvement. Expect it to continue to get better.

Pro tip, if you see a PieFed server missing, you can paste the address into the search and Blorp will attempt to look it up.

Testing image upload from PieFed

Happy cake day!

Sick!