I wanted to like it, guys, really I did, but for fuck’s sake, there’s ZERO feedback when you longpress photos to try and save them? It’s not in the upper menu? Just “save post”? Then while scrolling the whole app freezes and reloads back to page 1 missing your place.
For the last month, I haven’t been able to see my own account’s posts because of some Cloudflare bug despite being able to use the rest of the site and see everyone else’s profile.
It’s really janky, guys. I’m sorry but someone has to say something other than see for yourself.
I saw for myself and it’s pretty mid ngl
Blorp dev here. Anyone who’s just hearing of Blorp, I encourage you to try https://blorpblorp.xyz/ and decide for yourself if my app sucks.
Edit: if you wind up enjoying Blorp, follow !blorp@lemmy.zip for updates. If not, Voyager and Photon are some other great options you should check out
I like Blorp and am using it right now.
Probably not the right forum to say this, but I do get a bug where sometimes when I back out of a post, I get a black screen that I can only get rid of by switching to another “tab” at the bottom, then back to the home tab which puts me right back into the prior post instead of the home feed.
What version of Blorp are you on? See version at the bottom of the settings page.
Just to gauge the severity, how often when your using Blorp dies this happen? On a scale of very infrequently to it constantly interrupts what I’m doing.
Sounds like it might be difficult for this bug, but if you could find a list of steps to recreate this bug (starting with relaunch the app), I can fix this much more quickly.
V1.10.8
I’d say this happens about once or twice a day and vague my daily usage to be 1-2 hours.
Unfortunately its not an issue I can trigger consistently, but it does occur almost daily.
This makes giving you replication steps difficult.
It happens when I tap onto an image on a post and back out, then tap on the next post. I hit the blackout button subconsciously, so I don’t know if its the back button on Android or the app itself, but I believe both.
After I do that, screen goes black except the UI controls at the bottom. I can get out of it by selecting something else (such as the notification bell), then tapping back at home.
When I do that, I’m back starring at that image from the first post, but back out will work that time.
Ok, I experimented a few times and here’s my findings from a 1 minute spike.
If I tap into an image on a post at my subscription feed, then hit the Android backout button
Then tap into the image of another post, hit the Blorp back out button, it happens.
Its not consistent, so you may have to do it a few times. I also noticed other odd issues after replicating it a number of times, such as it reopening the explore tab after I already switched back to home and didn’t touch anything. Or it taking forever to load a refresh at the home tab.
Hope this helps. Sorry I can’t give consistent replication steps. If I find a more consistent way to replicate, I’ll message.
Amazing work! I was able to recreate the bug on my phone using your steps. I’ll try and get a fix up ASAP.
Glad I could help. Thank you for listening to me, and thank you for your contributions to this app.
Blorp absolutely does not “suck” and this user either has a problem or is just generally rude.
throughout my nearly 3 years making Photon I’ve had my fair share of hate comments, including one thread on a post, by someone encouraging people to check photon out, filled with people absolutely dunking on it.
your software is great enough to be noticed and hosted by several Lemmy and piefed instances, and you’ve got nearly 1000 or more users on a client for a super niche platform. you’ve done something right.
speaking from experience, hate comments really do dig into you even amongst a sea of positivity, but I hope you know that the opinion of 1 immature person does not matter in the grand scheme of things.
one more thing: people are much more likely to speak out when they have a problem versus when they enjoy some software. I guarantee you for every person either leaving feedback or complaining, there are 10 more silently enjoying your app.
Yeah, stop with that BS and pretend you’re a developer and not an emotionally immature grade school student.
In their complaint they mention specific issues, be an adult and identify those for yourself.
If they are problems you can resolve add them to your own to-do list, cause that’s what responsible adults do, if they aren’t problems you can solve then dismiss the complaint, cause they aren’t relevant to you.
You aren’t gonna come off like some rock star developer disregarding complaints about bugs in your software by getting defensive and specifically choosing to ignore an issue cause you don’t like the person presenting it or the service they are using to do so.
Grow the fuck up!
A responsible adult would behave themselves and put in an issue on GitHub, not rant on a social media site and expect that to bring change
I don’t expect it to bring change, but that wasn’t a rant. Neither was the OP.
And, besides, a responsible developer wouldn’t be on ‘unpopularopinion’ policing the language of the complaints made by their basic apps users either.
So I suppose we’re going to remain at this expected impass indefinitely. Because…
I’ve been in customer service my whole adult life. Every product, whether service, or app, or device, will see mostly complaints as their primary feedback.
It is simply human nature for a person to not mention a thing that works well vs actually act or speak out in response to issues that they encounter.
A lot of the time the customer is going to be frustrated while doing that, and that will be reflected in their tone and language. And that should be expected, and thus allowed.
It is in the best interest of manufacturers and producers and service providers to look to those complaints intentionally for resources to improve their products or services. And to do so with the knowledge and acceptance that their customers are possibly pissed off, frustrated, drunk, speakers of another language, or, and this is the most important one, not professionals in the relevant field.
Are you a professional developer? If so maybe you know how to use GitHub, or even what it is. Not everyone downloading a social media app on Play is going to know any of that, nor should they have to learn about it to complain when they have an issue.
This is a small platform made of primarily open source tools as a service to humanity by mostly good meaning folk. Inclusivity is important. And that means being accepting and welcoming to the less tech savvy. And understanding of their frustration when they have tech issues.
So, if you or any dev or service provider or manufacturer of any sort wants to thrive, I suggest learning to listen more, and police your customers less. They don’t tend to respond well to that, especially if they are already frustrated or disappointed because of something you are responsible for.
It’s a topsy tervy world where a customer has to concern themselves with a business opinion of them rather than the other way around.
And even if the service provided is free, or just a pet project, it’s still being produced and provided in a world where these things are true.
Regardless, I’ve migrated away from Blorp and will no longer be recommending it’s use. I’m actually going to be recommending against it. And who knows, maybe I am somebody, maybe me recommending a app tends to lead to mass adoption? It’s hard to tell.
“Complaints” belong as constructive bug reports or feature requests on !blorp@lemmy.zip or the GitHub page, not as advocacy posts against the app on another community without putting any effort into requesting improvements.
It’s one thing to complain when the $500 TV you buy at the store has a defect in it, but a whole other matter when it’s a developer putting their own time and resources into making a free, open source Lemmy client. If you don’t like it and don’t want to take sixty seconds to submit a feature request or bug report and wait for your requested feature to be considered for implementation, that’s fine, but don’t then go and trash its reputation amongst other users.
They’re not customers, though. They aren’t paying anything and developers owe them nothing in return.
Your mental model of the relationship is entirely misplaced.
I haven’t really had experience in customer service, so I haven’t really been numbed to the negativity. I have a lot of respect for people who have, and I’m truly sorry for anyone that mistreated you when you were working customer service.
I don’t expect everyone to learn how to use GitHub. I’m doing my best to triage the feedback here into an actionable roadmap. Sorry if I make mistakes along the way.
I think you do good! Seemed like a fine response to me! You are providing everyone a service developing Blorp. I still can’t even log in to piefed on Voyager. Thank you for doing what you do, giving it away for free, AND being active in the community :)
Thank you, your feedback has been helpful. Clearly I need to implement auto collapsing comments with a negative score. I’m also going to see if I can use PieFed’s “attitude” feature to collapse comments from overwhelmingly negative accounts.
If you look at my account history, you will see that I’ve spend hours responding to my 99.9% polite users. As a mature adult, all I’m asking is you consider how many thankless hours I spend maintaining this free and open source software. Please have some common decency.
I think I’ll tag you “FOSS Karen”. Anyone have a better suggestion?
Blorp supports user tags!