Lemmy.One and R.NF are currently blocked. This is a temporary measure to prevent the spread of CSAM. The instance appears to have inactive admins who have not responded to requests. We will remain defederated with them until they respond and clean up the traces of CSAM.
Some of our sister sites will be closing down June 1st, 2025.
Bye Utter.Online (Mastodon)
It has been decided that the Mastodon instance Utter.online will be shut down on June 1st, 2025, due to a lack of interest from the community. There are many Mastodon instances available for people to choose from. We could not create an Instance that stood out and encouraged growth. I'm okay with this because I, too, lack interest in micro-blogging. In the coming days, I will migrate some users to a new Mastodon Instance, such as @[email protected].
Bye Social.Photo (Pixelfed)
It has also been decided that the Pixelfed instance Social.photo will be shut down on June 1st, 2025. This instance has been growing in popularity slowly, and the decision to shut it down stems from frustrations with sustaining a Pixelfed service.
Is it because of money?
Closing these two services down also provides cost benefits from not having to renew domains and run the services. Masto
Sorry everyone I know how much you love the attention she gives you, but I've implemented some quick and dirty filtering for private messaging.
We now have the ability to automatically mark PM's as deleted or read, depending on content inside of them. If we accidentally filter something you legitimately wanted (ie, not Nicole) please let me know.
If any other instances would like to implement this, here's the code. Note that you'll need to set your hostname at the top here for some reason I haven't exactly identified.
undefined
SET lemmy.protocol_and_hostname = 'https://lemmy.ca/';
CREATE TABLE private_message_filters (
id SERIAL PRIMARY KEY,
phrase TEXT NOT NULL,
behavior VARCHAR(10) NOT NULL CHECK (behavior IN ('delete', 'mark_read'))
);
CREATE OR REPLACE FUNCTION filter_private_messages()
RETURNS trigger AS $$
DECLARE
ba
We've gotten a lot of new users over the past few days, and thought it would be good to make a post to help steer people in the right direction.
First of all, welcome!
You're on discuss.online, which is a platform for, well, discussing things online! 😃
We're a general-purpose forum hosted in the USA, and welcome casual and serious conversation alike about any topic you're interested in. To start, here's a thread that lists lots of active communities you can join (communities are like subreddits) that aren't focused on politics, news, memes, or tech:
Go there, click on interesting communities (they start with !, like how /r/ works for subreddits). As an example, this post is in [email protected].
There's a much wider universe of people that you can talk to and interact with on here! You've probably heard about the Fediverse, ActivityPub, and other stuff li
You may have noticed some instability and performance issues with the web client of Discuss.online. I have made some infrastructure changes to hopefully improve stability. In the process, I also updated to the latest version of Lemmy.
They joined to help increase community engagement, moderation, & perhaps some help raising funding. We're looking forward to their help and experience in improving our instance and the fediverse as a whole.
Here is a quick introduction from m_f.
I started getting involved in Lemmy mod duties over at [email protected] when the only mod went AWOL. That gave me the confidence to create a few communities for comics that didn't have any Lemmy communities yet, and then a community for posting loops. When [email protected] needed a moderator, I volunteered to help out there, and now I'm helping out on admin duties for the instance. Moral of the story is, stepping up to help out is a great low-effort way to help Lemmy grow
ATTENTION: There is a known issue with the database cluster for discuss.online. It's a managed cluster by #DigitalOcean. They are working on resolving the issue. I'll update you once the issue is resolved.
You might see strange errors like the inability to log in or view specific posts.
Update 03/01/2024 @ 9:40 pm ET:
The database has been migrated to a new server. Please, let us know if you experience any issues.
We are thrilled to announce the upcoming release of Sublinks, a groundbreaking Link Aggregation Social Network, joining the Fediverse. This innovative platform is designed to revolutionize how we share and discover online. Our dedicated team of volunteer contributors has worked tirelessly, utilizing technologies like Java, Go, TypeScript, and HTML to bring this vision to life. Sublinks promises a user-friendly interface and robust features that cater to diverse online communities. Stay tuned for our launch date, and get ready to experience a new era of social link sharing!
Sublinks will have a fully compatible API with Lemmy so all current Lemmy apps will also work with Sublinks. In fact, discuss.online will switch to Sublinks to fully replace Lemmy once we reach our Parity Milestone.
Lemmy doesn't provide any analytics. Give this post a like and/or comment if you use this instance. I'm trying to gauge usage by humans.
I'll let this census run for about a week to gauge usage.
Results might cause different changes to the services.
I'm doing this because the cost of running this instance is higher than most other instances due to reliability and disaster recovery implementations. I'm curious if I should back down many of these costs if we're not used fully. I don't see much activity directly in this instance.
I know that discuss.online wasn't listed on join-lemmy.org for about a month due to a bug with the Lemmy crawler. They just recently fixed it with their redesign. We are now listed but no longer featured.
tl;dr; is this instance dying? Let me know if you're here.
We are running the latest release candidate for Lemmy, version 0.19.0-rc.1. This release candidate includes many changes.
Every release comes with its own challenges; however, it resolves previous ones. We hope this release will resolve a longstanding issue with sync not working, causing a lot of manual work from the admins to keep things in sync.
Please let us know if you experience any weird behavior.
Some known issues so far are:
HTML entities characters in posts bodies (Changing & to &)
The spoiler tag crashes the site if used in the sidebar
We are aware of an issue with some clients not being able to sync (receiving 502 errors, etc..). It does not appear to affect all clients and the web view is still working. We will update this post as we know more and when we have resolved it.
Updates:
09-Sept 11:19 PM UTC
We attempted to roll back from Lemmy v0.18.4-beta.8 to v0.18.4 (as well as even earlier beta versions) but the service failed to start. We've reverted back to v0.18.4-beta.8 for now and will continue investigating the cause of the sync issues.
10-Sept 3:30 AM UTC
And... we are back, where we started. If you hadn't noticed, we were down for almost 2.5 hours while we tried to rollback the database migrations introduced in the beta releases so we could go back to the stable v0.18.4. When that failed, we tried to restore from the backup we took just prior to the rollback attempt. When that failed, we used Digital Ocean's restore to point in time and created a new DB cluster and swit
I’ve known lazyguru for over ten years. He’s a close friend. His skills are like mine. He will be able to help contribute to all projects of the discuss.online ecosystem.
lazyguru will help with moderation, system administration, monitoring, and development of new features. Joe has already improved some monitoring and is working on some changes to the infrastructure to make it more scalable. He will soon be helping with SocialCare.cloud once the first beta is released.
We use SendGrid to send our emails out. By default, SendGrid enables link tracking. Link tracking was causing issues with allowing users to verify their accounts. In short, I disabled link tracking, and links should work for all new emails in the future.
Contact support if you need your account activated. [email protected] from the email you used to sign up.
Issue
When new users sign up or when existing users reset their password, an email is sent to verify ownership of the account. These emails are sent from us through a service called SendGrid.
SendGrid, by default, will mask all the URLs to enable what they call link tracking. It's a marketing thing to track engagement with email. I have no use for it, but I didn't disable it before.
The issue is that sometimes this link doesn't resolve. An HTTPS error is shown to the user.
Resolution
The quickest and most logical resolution was to disable link tracking. I never use it. I did ju