Your instance seems to use a beta version of lemmy so it's possible there are API changes that make it incompatible with some 3rd party apps. Either that or the instance is being hosted behind cloudflare and the operator have strict anti bots option enabled (traffics from apps is almost similar with bot traffics). If yo ask your instance's admins, they might be able to do something about it.
Disable enhanced tracking protection temporarily and try again. The signup form uses mailchimps which is blocked by firefox tracking protection and most adblockers.
I just want to mention that your signup submission endpoint syncapps.us14.list-manage.com is being blocked by Firefox's enhanced tracking protection. If anyone having trouble with signup, try temporarily disabling adblocker or tracking protection.
Alma and Rocky are competitors to RHEL in much the same way piracy scene groups are competitors to game publishers. It is obviously not a fair competition.
If we were to draw parallel with game piracy, the pirates will not necessarily convert to paid customers if you implement a perfect DRM that totally prevent piracy. Instead, you might even lose customers in the long term as you piss your own customers by deploying such overly strict DRM. Some of those customers might swore to avoid buying your future games.
It'll remain to be seen whether this move will negatively affect Red Hat in the future, but I think it's a very real possibility.
I got a feeling that the kind of people that use Rocky or Alma linux would have a heart attack dealing with snap on ubuntu. Maybe they're better off switching to Debian LTS instead.
Sure it's FOSS, but who's actually working on the codebase? That's right, google employees. Good luck submitting patch if your patch runs counter to google's interests.
Me as a junior dev writing 1000 lines of spaghetti code everyday: "Let's go!!!"
Me as a senior dev writing 5 lines of code everyday and spent the rest of the day reviewing thousands LoC commits from my juniors: "I didn't sign up for this. I should've learn carpentry instead."
My advise if you want to work on a personal project which can be tied to piracy or copyright infringement is to avoid associating your real identity to it. I heard too many stories about experienced devs not getting any job offers or otherwise shafted due to past involvements with these kind of projects. For example, people suspect that Microsoft's decision cancel AppGet acquisition (and create WinGet instead) and shafted its developer (forcing him to kill AppGet) was due to his past contribution to Sonarr (a popular tool than can be used for piracy mentioned by others in this thread).
I don't want to sound mean and defeatist, but steaming service is very expensive to run due to the sheer amount of bandwidth and storage cost required. You can host standard website for free these days, but video hosting is another story.
Consider a standard 1080p video stream @ 16mbps. If your server has 1gbps bandwidth, you can only serve 62 people at the same time. You're going to need more and more bandwidth as your users grow or they'll get irritated and leave because your servers don't have enough bandwidth to serve videos to all of them (lots of buffering and timeouts).
So how much will those bandwidth cost you? If you plan to host them in a cloud provider, you should know that they'll usually charge by the amount of egress traffics you consume. If you maxed out a 1gbps link for a month in an AWS server, Amazon will charge you around $0.1 per GB, which means you'll get a hefty $32,400 at the end of the month for delivering 324TB of traffics.
Now AWS is literally the most expensive provider in term of bandwidth, so you might want to use a provider that provides unmetered billing. This usually means traditional colocation service where you buy your own physical servers and only pay for electricity and internet, or renting out dedicated servers which will cost a lot upfront but ended up being cheaper than pay as you go cloud providers. But you'll still looking to pay thousands $ each months to pay for the bandwidth.
Some pirate streaming sites cheats by uploading their videos into various cloud file storage such as Google drive and playing cat and mouse by constantly creating a new account and reuploading their videos when when their account for banned for violating tos. You might be tempted to go that route as well, but considering how you're already sweating at the prospect of finding and uploading all anime files yourself, constantly creating a new cloud storage account and constantly reuploading your anime files doesn't sound really great, right? Some pirate streaming sites literally have full time staff doing this stuff all day, constantly keeping up with new anime release, downloading them released schene torrents or ripping them out from Crunchyroll, then uploading to a cloud storage account or other video hosting services (and reuploading again if it were taken down due to tos violation).
I think this project is way too big for you right now, but pretty fun to think about especially the logistics part.
Nice! Looks like it even has update checker as well. Is there any reason why pictrs is not included in the update checker and hardcoded to version 0.3.1?
Your instance seems to use a beta version of lemmy so it's possible there are API changes that make it incompatible with some 3rd party apps. Either that or the instance is being hosted behind cloudflare and the operator have strict anti bots option enabled (traffics from apps is almost similar with bot traffics). If yo ask your instance's admins, they might be able to do something about it.