Directories on host machine:
-
/data/certbot/letsencrypt
-
/data/certbot/www
-
Nginx server in docker container
docker run -d --name nginx \
Directories on host machine:
/data/certbot/letsencrypt
/data/certbot/www
Nginx server in docker container
docker run -d --name nginx \
Protection method | Is safety ? | Examle password | |
---|---|---|---|
plain text | insecure | example:P@ssw0rd_123 | |
crypt | insecure | example:$1$Z4iyFnl/$ZdbNEw8wcJeFkJmUUmQ6E1 | |
sha1 | insecure | example:5b50e3ae27d51c44da3cee51552aa6f7cb805a56 | |
apr1 | insecure | example:$apr1$8MMhB4DE$/r/lY2CQQgj61xPO7mBXu/ | |
bcrypt | secure | example:$2y$12$dNP9/NOZg.My1a474if36eSk6TCFYyIKfHAWTKkCG.FJQjwHsrSVi | |
SHA512 | secure | example:453d6168242737b3b1b9f3fb360c8d1afc00a349abe6b617a6c4e57f14a38f400c83e0468d41350c2d3483d8a76b8789a6ac2ad9d63893c208785f8535a89241 |
import json | |
import base64 | |
import os | |
import pathlib | |
from urllib.parse import urlparse | |
# list of supported image mime-types | |
# Special thanks to https://gist.github.com/FurloSK/0477e01024f701db42341fc3223a5d8c | |
# Special mention, and thanks to MDN | |
# https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types |
<div class="card"> | |
SpiderVerse Confirmado !!! | |
</div> | |
<a href="https://github.com/AlexGG23" target="_blank">AlexGG23</a> |
Hey there. During the time of bot development, I've learnt a lot, there are several things which I wish I could change and several things which I'm glad I did. I'd like to share my experience which may help some beginners or even some experts.
Before you reach verification, you must transfer your bot to a team and include a secured alt in the team. Many developers regret not doing it before their application reaches verification. This essentially provides a ray of hope of not losing your bot if you ever lose your main account. Side note (31 October 2024 ๐): Discord has made it compulsory to have 2FA to do almost anything in the developer portal. You'll have to enable 2fa in your alt.
An epic centre is the core of your bot, your bot could be known for it. Take Dyno for example, we all know it for it's moderation capabilities. In a similar way, your bot must be known for something. You need to avoid being a sheep in the flock.
Important Note!
Doing this requires running a script inside Discord, historically Discord has allowed these perfectly fine but it was for advanced people only and Discod discovered non-advanced users were copying and pasting random scripts people gave them which ended up being malicious and harmful to their account.
Discord has since blocked access to scripts unless you enable a hidden setting. The script below is open source and commented. Anyone is welcome to verify the legitimacy of it. It's very simple in how it works. However if you proceed further and enable custom scripts, I highly reccomend to disable it afterwards unless you know what you are doing. There's a reason Discord disabled this feature, don't even run scripts without knowing what they do first.
To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.
Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.
There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed.
It's recommend to use the Authorization
header. If header auth isn't an option, the token may be sent through the ApiKey
query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.