I believe there are a large number of feature requests on Lemmy’s GitHub page, making it difficult for developers to prioritize what’s truly important to users.

Github issues are annoying that way. You could solve it by closing down “issues” and using discussions instead. People can up and downvote discussions, and you can see that from the listview, unlike with issues.

And you can have threaded conversations in discussions.

There’s a user made OpenAPI spec: https://github.com/MV-GH/lemmy_openapi_spec - You probably mean that one

I’ve had similar issues as you mentioned that the dev did fix - but yea, Typescript has less precision than Rust (the source) or the openapi spec. And the Typescript client is build for Lemmy-JS and not build an example for other language client libraries…

Though the OpenAPI Documents in C# and Java are based on reflection of the source itself, and Rust doesn’t have Reflection like that… So it’s probably difficult for them to add without manually maintaining the OpenAPI specs

[From the github comment]

The issue I see with the RFC is not wanting to allow users to add tags to ease the burden on moderators. This comes from a lack of users with privileges, so moderators are overworked and need to rely on bots.

If the tags are just kinda “plain old hashtags” - and not something cool like I mentioned in the previous post 😉 -

Possibly you could have a look at how Gazelle handles tags, where it’s just a voting system. For example, this is “Kanye West” https://i.imgur.com/adTe4t8.png - then tags are no longer a boolean yes/no system, but a user-voted system. And then it’s no longer a moderation concern to have to correct tags, and you don’t need “User privileges” to manage the tags either.

It’s just a pretty chaotic system though - you might still want moderators to remove bad tags and/or ban users from creating tags if they’re always adding nonsense.

Could be some point based system like Stackoverflow - users with n points can vote on existing tags, users with n+ points can add their own new tags

I don’t know if there’s a “definitive guide” - it’s not that complicated to get a torrent client up and running. What kind of content are you looking for? Movies, Series, Music, Games, Books…?

Best is probably to try to get access to a decent private tracker, and an “easy” one - one with a bonus point system for seeding and uptime - that makes it much easier to keep a good ratio with a NAS, if you’re just permanently seeding everything you download, you’ll get points and “rise the ranks” of that tracker.

Once you’re a high enough rank on that tracker, you’ll get access to their “Invite Forums” where other private trackers advertise and give out invites to their trackers

What software/OS are you running on your NAS? If you’re running some goofy software on a private tracker your client might not be whitelisted.

Besides that - this NAS is attached to your home network I assume? Is it behind a router? Are the ports you’re using for torrenting port-forwarded?

What tracker are you testing this on? A bunch of trackers will have a “Connectivity check” that will tell you whether or not your client is connectable

Personally I don’t have any problems with it (if that was directed at me) - I’ve added 418 as “unhandled exception code” response to a bunch of applications, so I can easily differentiate whether my application is throwing an error, or whether it’s some middleware gateway AWS io-thing

I was just curious what OP thought about it, since in the early days it wasn’t uncommon to add goofs or easter-eggs into software, but nowadays not done so much… and apparently the “HTTP Working Group” doesn’t like it either… So I was curious whether OP though in hindsight whether it should’ve been added or not

Do you regret adding it, or with the knowledge you have today, would you still add the 418?

Since a bunch of languages have not implemented it, or/and has long discussions about it:

https://github.com/dotnet/runtime/issues/15650
https://github.com/golang/go/issues/21326
https://github.com/nodejs/node/issues/14644
https://github.com/psf/requests/issues/4238
https://github.com/aspnet/HttpAbstractions/issues/915