this post was submitted on 12 Dec 2024
117 points (100.0% liked)
Fediverse
28721 readers
80 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hello Blaze,
One request, whenever you post about clubsall, can you please tag me so I can also participate? Thank you.
As for this discussion, when we had a discussion last time on reddit, I thought we agreed that as long as there is not meaningful traffic, it should be ok. I guess you were not fully onboard with this.
My request with all admins is - can we agree on some rules. If we block all new sites on hunch or rules as we make up, it will kill anyone trying to do something new.
There was another thread (that I cannot find now) where some rules were proposed. (If someone can find, please reply to this).
There are 2 things being discussed
I can give an update on both of these. As I mentioned previously, someone was helping me in doing some audit, implementing federation and then we could also open source. We were going to use "sublinks", which would do a number of upgrades. So that seems the right choice moving forward. It will allow self hosting, federation, move to postgres, move to docker etc.
However during implementation we found that sublinks itself does not implement federation out. So we were blocked by that. I checked with developer just few days ago and I was told that since all developers are volunteers and they got busy, federation was delayed. The work will pickup again in new year.
I am not sure when they will be able to finish federation. I can quickly move there once done. However that seems months away.
In the meantime, can we have a discussion about a set of rules for clarification and fairness?
Let me give you my opinion, specifically as a React developer, if you don't mind.
And let's be clear: I intend this to be a constructive criticism. I hope you understand and don't take it the wrong way.
To be honest, I don't know how good or bad federating one-way is. This is more of a "people" problem rather than a technical problem.
But, to be honest, what I am bothered by, is the fact that the website doesn't give an attribution in the UI about which instance certain users are from and which instance certain certain community are from.
Take a look at this post: https://clubsall.com/posts/theyre-trying-to-charge-luigi-with-terrorism-imagine-that-qfF82
The UI says that the post was posted by
u[slash]BytesOnBikes. If I didn't know better, I'd have assumed this was from a user from clubsall. But if you click the username, you realize that the link saysu[slash]BytesOnBikes[at]slrpnk.net. I think this would be confusing as a user. What if there is the same user under the usernameBytesOnBikesfrom clubsall? At least if you include the instance name, user would know right away that both users are different. But if you didn't include the instance name, I feel like this can be abused to impersonate user. This is a bad thing to happen to your website, don't you agree?Now that we both understand that lack of attribution is a bad thing to clubsall... What's stopping you from adding an instance name to the username? I'm sure the app has a way to know which instance certain users are from. From what I gather, I feel like this is as easy as appending a string in the code.
I haven't even talked about the community name on the UI. Or the ethicality of misleading attribution.
Yes this is easy to implement. While I do not fully agree because impersonation can still be done by using username Bytes0nBikes. I feel showing instance names adds complexity for the user and it does not fully address impersonation anyways.
But then again, even though I disagree, many people mentioned that lack of attribution bothers them. So I should take feedback and get this done. I hope this is what everyone meant and they will accept this as a solution.
This is rather easier to implement. I should be able to get this done rather quickly. I will try to do this before end of Dec.