Oh you definitely can. When I was around 8 I had a sever case of constipation during summer and couldn't poop for around 2.5 weeks. During which I had to eat primarily rolled oats and medication before being able to free the path.
Irisos
It is fine. But for your personal growth and some more peace of mind, you should migrate the repository to one of the git services of your organization.
Personal growth because you will be able to use feature like branch policies, CICD pipelines or an integrated work item board.
Peace of mind because that network share is less likely to be recoverable than a self hosted gitlab instance for example.
The migration process also only take less than 5 min so there are more advabtages than disadvantages to do so.
Honestly that "problem" will only appear in a few dozens of years after an instance started federating with others.
Most content is plain text, which is inexpensive to store. The only real weakness are images if your instance's users post them a lot.
But it can be easily mitigated by configuring how big file uploads can be and encouraging the use of links.
Probably the best one I have found so far.
By the way, do you have any plan to expose an API or daily extract of the data you have?
While those websites are useful for manual searches, I think it would benefit the feddiverse much more if there was a way to integrate all those lists into an app. At least without resorting to web scrapping.
Apollo also reported having around 1.2M users while not being a small app at all.
So with 400M MAU as the lowest possible amount of users, somehow all others 3rd party apps have over 118M users between them?
I could believe 30% of users being old.reddit ones due to it not being deleted after all those years. But for mobile apps, that 5% quote seems the most realistic.
(Servers only)
- Rocky Linux 9 by default
- If something is not supported on Rocky Linux 9, I revert to Centos 7
- Debian as a last choice if what I'm using does not support RHEL for any reason
The issue is that it could still be abused against small instances.
For example, I had a bit less than 10 bots trying to signup to my instance today (I had registration with approval on) and those account are reported as instance users even though I refused their registration. Because of this my comment/post ratio per user got a big hit with me being unable to do anything (other than delete those accounts directly from the db).
So even if you don't allow spam accounts to get into your instance, you can easily get blacklisted from that list because creating a few dozen thousands account registration requests isn't that hard even against an instance protected by captcha.