Single sign-on from trusted third-parties allow users to maintain a single account across many platforms. ActivityPub connects Discourse to the Fediverse, allowing users to follow categories and tags on any compatible platform.
Site-Specific Nuances
Discourse is one of many services hosted on eom.dev. Some of the others include:
Gitea stores source code and executes automatons. Nextcloud does groupware. MinIO handles object storage. Matrix is for quick, real-time chat (the fast lane). Discourse is for formal discussions (the slow lane). Owncast hosts live streams.
These services, along with some backend ones, work together to create the eom.dev platform. More details can be found in the software-infrastructure repository on Gitea.
I have updated the configuration settings for logins to allow users to create local accounts with email addresses. I had wanted to use ubiquitous SSO with upstream providers for accounts on my network, but I am wondering if that is actually a barrier to entry for some users, so I have decided to enable local accounts on this platform.
Hi!
I’m Kenji (or eev in luanti).
I tried to get a local account with my own email address, but I didn’t receive the activation email.
So for now, I regstered with my google account.
Thanks for joining! Did you check your spam box for the activation email? It is a self-hosted email server, so providers sometimes block it. You should be able to link the account to your email and give it a local password on the user settings page.
I think you’re the first to use a local account, so I’m happy to help debug!
Edit: I can see a second eev account in the backend, so it seems the initial account creation did work. I haven’t sent to that email domain before, so I would definitely check the spam box!
Do you host this site at home?
Then I think you can’t set the reverse DNS because the IP address is owned by the ISP (in this case Google?).
Possibly you can ask google to set the reverse DNS, but google probably don’t set that.
I will also check if I can opt out your domain from the FCrDNS filter.
By the way, can you send and receive emails from different domains like gmail.com?
Yeah these were interesting to set up. I actually made a video about it a while ago in another thread… If you don’t mind, though, I would prefer to keep this thread for discussing Discourse and move debugging the mail server to the Gitea issue linked above. Thanks!
I often obsess over having all of my data and content stored and organized with a consistent structure and logic. At the same time, I make changes to the very platform on which I store and share this content frequently. Having just uploaded my first video to PeerTube, I am now facing a dilemma in that my previous method for sharing videos within Discourse posts is now redundant.
I have written elsewhere about how I have thought that a mailing list may have been a better choice for the content I am sharing here, and even have gone so far as to deploy GNU Mailman.
Having already had an established YouTube channel when I deployed this platform, I faced the same question: how can I store all of my data consistently when I keep changing the ways in which I am doing so? Unfortunately, it is extremely tedious to go back and reformat an entire catalogue. The solution in all of these cases, and probably most future instances, is not to reformat the old content but to archive it as it currently exists. I will probably not upload all of my previous videos to PeerTube, and I probably will not repost all of these threads should I decide to focus on a mailing list instead. Through a lot of experience, I think I’ve learned that my obsession to have a perfectly consistent library is counterproductive. The things I created in the past should be left as they are and new methodologies should be explored freely. So long as the original platforms are maintained, they all serve to tell part of the entire project’s story.
I often obsess over having all of my data and content stored and organized with a consistent structure and logic. At the same time, I make changes to the very platform on which I store and share this content frequently. Having just uploaded my first video to PeerTube, I am now facing a dilemma in that my previous method for sharing videos within Discourse posts is now redundant.
I have written elsewhere about how I have thought that a mailing list may have been a better choice for the content I am sharing here, and even have gone so far as to deploy GNU Mailman.
Having already had an established YouTube channel when I deployed this platform, I faced the same question: how can I store all of my data consistently when I keep changing the ways in which I am doing so? Unfortunately, it is extremely tedious to go back and reformat an entire catalogue. The solution in all of these cases, and probably most future instances, is not to reformat the old content but to archive it as it currently exists. I will probably not upload all of my previous videos to PeerTube, and I probably will not repost all of these threads should I decide to focus on a mailing list instead. Through a lot of experience, I think I’ve learned that my obsession to have a perfectly consistent library is counterproductive. The things I created in the past should be left as they are and new methodologies should be explored freely. So long as the original platforms are maintained, they all serve to tell part of the entire project’s story.
ITT the features of Discourse are enumerated and their efficacy for suiting the bespoke needs of eom.dev is discussed.
Plain-text, the universal interface, is used to compose posts in markdown format.
Wiki posts allow for collaborative documentation.
Email clients can easily subscribe to threads and create new topics.
Single sign-on from trusted third-parties allow users to maintain a single account across many platforms.
ActivityPub connects Discourse to the Fediverse, allowing users to follow categories and tags on any compatible platform.
Gitea stores source code and executes automatons.
Nextcloud does groupware.
MinIO handles object storage.
Matrix is for quick, real-time chat (the fast lane).
Discourse is for formal discussions (the slow lane).
Owncast hosts live streams.
