I can’t seem to see posts that are below 0 points.
If I respond to a person, and their post gets downvoted, mine also becomes contextually unviewable.
Same seems to happen if I respond to someone and they delete their post.
Is this a connect feature? Where can I change this? I don’t want posts to be hidden unless I hide it manually. I always want to be able to revisit my posts in the threads they were posted in.
This seems to have been fixed now. I can click on comments in your profile that are responses to downvoted comments and view them in context on posts.
I’m still having the issue.
The post in my recent history that begins with an ellipsis (…) is an example. I cannot access it’s context from my profile.
That’s odd. I can view that post in context through the app.
deleted by creator
It isn’t fixed. The reply to negative votes must not be what the cause was.
There are a significant amount of posts in my profile that I cannot click on to obtain context.
That’s weird, I’m not doing any filtering Connect side on low score posts or comments. Could you link me to an example? I’ll take a look.
An instance where Connect isn’t loading the full thread is this comment foggy posted. On Connect, whether viewing the comment chain or the entire thread, the comment isn’t being loaded but you can view the thread fine on mobile.
If I could share a comment from my profile, I would provide you with a ton of links.
Unfortunately there is no way to interact with posts from my profile.
Clicking the post attempts to bring me to it’s context, and fails.
It’s failing in over half of my posts. Idk what’s causing it, but revisiting conversations is the primary purpose for me being here. This renders the app useless to me.
I assumed it was either responses to low scores or deleted posts, but I’m finding instances of top level comments with positive scores that I am unable to visit contextually; only view in my profile, in a state that disallows interaction.
I can’t stand this; truly frustrating.
Hi, thank you for your feedback and this should now be fixed on beta 1.0.109 (hopefully live in the next couple days).
