Lemmy 0.19 supports authorized fetch when retrieving remote objects. Enforcing it for fetches from Lemmy would also not be hard. It doesn't make much sense though as long as we don't have private communities.
nutomic
joined 4 years ago
All of the fields should be defined in context. Which one do you think is missing?
Downvotes federate as Dislike activity which are part of the standard. There are some nonstandard parts eg for locking posts distinguishing comments. But most platforms including Mastodon or Peertube have such custom fields.
Well there are some different ideas for implementing hashtags. One idea was that Lemmy could follow hashtags from Mastodon etc to display them in the corresponding community. The only way to receive these hashtag posts is by following the users who create them, but Lemmy doesnt support user following.
Another option would be that Lemmy adds hashtags to posts so that they are picked up by Mastodon etc, without Lemmy itself using hashtags. This is definitely doable, for example it would be very easy to automatically add hashtags based on the community name, so everything in /c/memes would have #memes hashtag. It would also be possible to configure the hashtags in community settings similar to this tagginator tool, but that would require more extensive changes.
A third option would be to add hashtags based on post tags, thats what db0 was discussing before and which I referenced with that comment. However we are still discussing how post tags should work as you can see from the issue and from the RFC.
So option two or three seem reasonable, but like you say none of the maintainers seem to give this much priority. So the only way this will get implemented is if someone else writes the code. Thats just the reality, complaining wont change anything.
There are countless feature requests for Lemmy, but we are only two fulltime devs. Our time is limited so we have to set some priorities, and no matter what we do, some people will always disagree with those priorities. And besides implementing new features we also have many other tasks like reviewing pull requests, or right now bug fixing to get already implemented changes out into production. The only way to implement more features faster is by having more developers. Either as volunteers, or by hiring people with donation money.
I think your proposal is reasonable. However it depends how exactly post tags will get implemented, which is still rather vague. I dont think it makes sense to implement federated hashtags before we have post tags in Lemmy figured out.
In any case your tool looks very useful as a stopgap, and can help to test how hashtag federation can work in practice.
There is already an open PR for Oauth, though Im not sure whats the difference to LDAP. Regarding tests you must have looked in the wrong place, we have a couple hundred already. Docs are here.