lower temps work partially afaik and they will never fully dry the silica gel. You should aim for above 100°C
If you are concerned about safety have one dedicated oven dish for the silica gel and ventilate your oven and kitchen thoroughly after a session.
That would be collective punishment. Which is very unfair - I agree. But it is not discrimination.
Discrimination is the process of making unfair or prejudicial distinctions between people based on the groups, classes, or other categories to which they belong or are perceived to belong, such as race, gender, age, class, religion, or sexual orientation.
The distinction in this case is made by how much cheating happens in a region, which is kind of not prejudical.
If you already have a server then follow the installation instructions on the pterodactyl website. https://pterodactyl.io/panel/1.0/getting_started.html
Then if some step goes wrong:
if you want help you should provide detailed information. Tell exactly what commands you entered, from start to finish, not skipping anything and provide the outputs that you’ve gotten, especially the errors.
The pterodactyl discord will probably be more helpful there.
You can not run pterodactyl on cloudflare.
For pterodactyl or any gaming server, you need a real server with a real operating system that you get full control over.
Instead look for cheap VPS options in your country. Make sure their specs are good enough for a minecraft server. It will cost ~ 5-10$ per month. Then:
Point the domain from cloudflare to that VPS by changing the dns records in cloudflare
Install some linux on it like debian.
Get into that linux by using ssh.
Then follow the installation instructions on the pterodactyl website. https://pterodactyl.io/panel/1.0/getting_started.html
Sounds like you are in head over heels.
Pterodactyl has a discord, why don't you go there for dedicated support?
Regardless of where you ask - if you want help you should provide detailed information. Tell exactly what commands you entered, from start to finish, not skipping anything and provide the outputs that you've gotten, especially the errors.
On linux you can also use vmtouch to force cache the project files in RAM. This would speed up the first compilation of the day. On repeated compilations files that are read from disk would naturally be in the RAM cache already and it would not matter what drive you have.
I have used this in the past when I had slow drives. I was forcing all necessary system libs (my IDE, jdk etc.) and my project files into RAM at the start of the day, before going on a 2min break to make coffee while it read all that stuff from a hdd. Which sped up the workflow in general, at least at the start of the day.
It is not the same as a ramdisk, as the normal linux file cache writes back changes to the disk in the background.
You can also pin your fastest core to a specific process, so that it gets no tasks except for the one you want it to do. But that seems more hassle than it's worth, so I never tried that.
Do donations really come in all at 1 or 2 given dates per year?
I would assume non-recurring donors average out over the months. Maybe there is a bit more in holiday season.
But if I donate 200$ in May, are there no other people in the world that donate 200$ in June and then others still in July etc.?
edit:
I could not find any donation stats/charts for gnome. But assuming they are similar to KDE, it looks pretty managable to me. There seems to be a solid baseline of about 4k per month and then some months have huge extras. It does not seem very complicated to budget that.
2025: https://kde.org/community/donations/previousdonations/
2024 looks way more wild. But that is when they introduced the donation popup by the end of the year.
2024:
The license says (paraphrased) that you need to keep the original license file, which has the authors name. Even if you re-license it, you leave the old license there without touching it and put your new license next to it.
They did not follow that clause and deleted the original license and the original attribution.
A thanks does not necessarily imply credit.
I just tested it on my instance. You can create a public share by setting the mode to "Write", which is accessible without logging in as a user (but with optional password).
It works, but one does not see any files, not even the ones you uploaded yourself. So for example if you updated the file and need to re-upload it, there is no way for you to delete the previous one.
You can also create a shared "virtual folder" that is seen by multiple users, and then you have fine grained control on a user basis (Users > burgermenu > edit > ACLs > Per directory permissions) there you can mix and match from a list of ~15 permissions. To upload anything to that virtual folder, you'll have to properly log in as a user.
Hope either one of the ways works for you. Cheers
I personally really like sftpgo and I mount it via webdav.
I used seafile first, then nextcloud. Each for a couple of years and had significant problems with both.