RE: https://bne.social/@james/116827309192939865
(Not that @evan needs more pile-on, but I also don't like talking about someone behind his back.)
RE: https://bne.social/@james/116827309192939865
(Not that @evan needs more pile-on, but I also don't like talking about someone behind his back.)
@DavidMarzalC @james it's opt in by server or by user:
We used to also share content from open registration relays, but that surprised and upset people, so we stopped.
@james @evan sorry if I should know this, but I thought that the service was opt-in. I followed an account so my boost could be amplified. But on that thread the last post said it's opt-out.
@evan @DavidMarzalC Thank you. I’ve passed that on. I don’t have any issue then with this service. Grateful for your patient response.
This blow-up is, if you don’t mind me saying so, all on you - this documentation is poor and unclear; and it would have been helpful to clarify when you quietly stopped amplifying posts without opt-in. Writing clear documentation for human beings is a good thing.
@james @DavidMarzalC That's surprising to me. What's unclear that you are missing?
I thought it covers things pretty well: how to follow hashtags, how to connect your account or server to hashtags, what our privacy situation is, how to opt out or turn off notifications, and how to contact us.
What were you looking for in there that you couldn't find?
@evan @DavidMarzalC I would have thought just looking at your notifications over the weekend would make it obvious that your documentation isn’t clear…
Not least - there’s a heading called “Opting out”, but not one called “Opting in”. You need to make it really clear that it’s an opt-in service, not one you need to opt out of any more (whenever you made that change). The language is technical and complicated, and assumes deep knowledge of ActivityPub. Again, for the reasons why you need to make it clearer, just look at your notifications.
The way I’ve always done documentation is from feedback. “Oh, person X thinks this service does Y. Why do they think that, and how can I make that clearer that it doesn’t?” I do this on every piece of feedback I get. Rewriting documentation and UX is never-ending; so that even if people only skim the headers they know how it works.
@james @DavidMarzalC I'll update the "connect" header to "opt in". Good idea.
@james @DavidMarzalC Oh, you're not talking about documentation for people who actually want to use the service. You're talking about giving an explanation to people who are mad about the service. Those are different things.
@james this morning! I think you replied to a post with this link. I thought you meant, "You should add that info to your page."
https://socialwebfoundation.org/2026/06/28/unsubscribing-tags-pub-from-open-registration-relays/
@evan Your documentation is for both of those people. All documentation is.
Particularly, if your documentation was clear that it is opt-in, people wouldn’t be mad at your service for only being opt-out.
Though you still haven’t told me when you made that change - I’ve asked twice - and perhaps I am naïve in giving you the benefit of the doubt here. May I politely ask a third time?
@james Thanks for the idea! It's updated now. https://tags.pub/#optin
@evan Never seen that link before.
The only thing I’ve said is that the documentation on tags.pub is overly technical and confusing: and that it didn’t make it clear it was opt-in.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.