Skip to main content

why are those routes still not made public? some Gab leftover?
Yeah, it annoys the shit out of me whenever I want to look up some user on a server that runs Soapbox. Yo @alex WTF?
Bro. Normal people don’t stalk remote users online. You guys need to take a break from the internet if this annoys you so much.
You’ve never checked a person’s profile to see if you want to follow or not? I mean you could argue you’re “digging too deep” at that point but eh, sometimes you’re unsure after seeing their posts and want to see their replies. (Especially if someone has very few top level posts)

It’s a pretty minor wart on the best front end though…
You can see top level posts. Replies are different.
People on Pleroma can see (most of) your replies anyways.
Look, anyone can go to any Pleroma instance and just look up (most of the) replies from users on Spinster

I don't even follow those people!
Oh good, you have a workaround, so there’s nothing to do here.

Pleroma FE is the superior frontend!

If there’s anything I’ve learned, it’s that when the vast majority of users aren’t complaining, it’s to take what a small handful of loud users are saying with a grain of salt. And I don’t mean it personally, but Snow complains about this constantly.
First of all, no, you’re the one who wants more user data. That’s what this is all about lmao.

Secondly, if someone writes the code to make it configurable, I’ll allow it. But it’s a harder challenge than it would seem, and I don’t think it’s worth my time.
After shower thoughts, maybe letting it be configurable wouldn’t be so hard…

But if I did make it configurable, I know what you’d do… You’d go to every single Soapbox instance and tell them to reconfigure it.
This may seem like a silly opinion to hold, but I'm of the view that an ideal client will make the most of the information that the server delivers to them. That is, the most of what they're permitted to see. If the server reveals too much, and the client uses that, it's usually a backend issue.
well, pretending a feature doesn’t exist is always a bad idea
pretending a feature doesn’t exist is always a bad idea
“A weak lock is better than no lock at all”, true or false?

Depends on the context, and what’s at risk.

User know their replies aren’t private, since anyone can sign up to see them. 99% of users don’t know how to use the API, just like 99% of people don’t know how to pick a weak lock. If someone wanted to try hard enough, they could access that information either way.

The purpose of gating in the UI is to discourage it, not prevent it.