Many people on feddit.de already do so
Many people on feddit.de already do so
Since mastodon has no equivalent to lemmy’s communities, it can’t handle lemmy’s !community@instance links.
Communities are represented as a regular user on the mastodon side, if you mention a user (using @) on mastodon, it will be parsed as a markdown link on lemmy: [@lucy_idk](https://mastodon.world/@lucy_idk)
I think it wasn’t meant as a repost to this community. It was a post on mastodon that was picked up by lemmy because this community was credited:
Found by: @programmerhumor
Just put
true = False
false = True
at the top of your files.
That’s what I love about Rust: many problems that would turn into runtime errors in other languages aren’t possible with its type system and the compiler catches them.
And we will be monitored too!
Type Annotations and other typing-related stuff are built into the language/standard library.
To get a real benefit you should use a static type checker like mypy.
Rust has pretty strong stability guarantees. Backwards incompatible changes are only made using “editions” where every compiler version supports all previous editions and editions are fully interoperable.
https://doc.rust-lang.org/stable/edition-guide/editions/index.html#what-are-editions
That’s why I like to include a comment with a link to an example on regex101.com.
Okay, thanks! Maybe I’ll try it in the future.
That wouldn’t work if multiple containers use the same port (eg. 8000), right?
Without a docker network, I can just map 8001:8000
and don’t have that issue.
The ActivityPub extension ForgeFed for federation between different servers is not finished yet. AFAIK Forgejo contributors work closely together with other ForgeFed devs to bring it forward.
Good bot
Forgejo will follow next week: https://floss.social/@forgejo/110725896533944821
418 I'm a teapot
Caddy! It has HTTPS built in and provides simple but powerful configuration with sane defaults.
Example Caddyfile for a static file server:
example.com {
root * /var/www
file_server
}
I used nginx in the past, but didn’t like it’s verbose config files.
AFAIK, instead of forwarding your DNS requests to an upstream DNS provider (eg. 1.1.1.1), it resolves the domain step by step. First, it asks the root nameserver “where’s org.?”, the returned server is asked “where’s example.org.?”, the returned server is asked “where’s www.example.org.?” and so on until you get your target IP.
See also https://en.wikipedia.org/wiki/Domain_Name_System#Address_resolution_mechanism
Edit: there is also a good explaination on https://docs.pi-hole.net/guides/dns/unbound/#what-does-this-guide-provide
I recommend using https://regex101.com/
It explains all parts of your regex and highlights all matches in your example text. I usually add a comment to a regex101 playground if I use a regex in code.