This looks really nice, dude
That actually looks wayyyy better than I thought it would. Well done.
That's very smart. It'd be nice to have native ntfy support for Lemmy though.
Also, the email address format is documented here: https://docs.ntfy.sh/publish/#e-mail-publishing
The Lemmy dev has expressed interest in that. He uses ntfy too :-D
Thank you for contributing to the magic of the old school internet.
My question: How does one get to write an RFC? Do you have to become part of a certain group, or just be known in certain circles, or do you just start writing and then submit it somewhere? If I had a great idea that I think should become an RFC, what is the process to make this a reality?
Awesome!! I'll go check it out. Thank you!
I once started building a Discord bot for ntfy myself here: https://github.com/binwiederhier/ntfy-bot -- And then I realized I should work on ntfy itself instead, hehe.
Install Debian Stable on a SSD, most likely via debootstrap from the Ubuntu system
What an interesting way to install a new system. I've only ever done that for image building purposes. Why would you do that instead of just installing it from a flash drive?
Also: it sounds like you're manually installing things. I would suggest Ansible or something similar, so that reinstalling isn't so brittle and manual.
Related question: is "Hot" super buggy? I am on 0.18.0, but I still often see really really really old posts (1 year old, 2 years old) sprinkled in with new stuff, and I often see clusters of 5-10 posts of a single community grouped together.
I have to pay extra attention to the post age because of this.
If you don't, half the time your posts will just disappear into the ether...
There are plenty of instances that copy the original content. As an instance owner that runs a only a single project specific community, I should be able to decide what content is available on my domain, and what isn't. Don't you think?
Aside from the questionable content, there is also legal issues around it that I'd rather not deal with.
There is no way to exclude individual communities. The post URLs are generic, like /post/1234. From nginx or other proxies, I cannot tell what community they belong to. I would love to have my own be searchable, but not at the price of tainting my project's reputation.
There is no way to list topics. That would be silly, given that topics are meant to be used as secret notification channels ๐
The admin of the server can obviously list topics, but normal users cannot.