Nobody likes downtime, but this time it's for a good reason! Our web host we use for SocialCu.be is upgrading their servers soon. This should result in faster site loading across the board which is a nice bonus for us! Starting on July 25, 2025 at 9:00 AM UTC, they'll be gradually rolling out the migration to new hardware over the following 12-24 hours (though we're not sure when exactly ours will go down).

If SocialCu.be still appears to be down after an extended amount of time, you may need to either wait for your ISP to flush their DNS cache or try manually using 1.1.1.1 (cloudflare's DNS IP) or 8.8.8.8/8.8.4.4 (either of Google's DNS IPs) which typically update faster.

If it's been 24 hours and you still can't reach the site, don't forget you can always shoot me an email at [email protected] for troubleshooting assistance.

I am making some changes to the way the website is seen by the internet. While the internet refreshes, you may have issues accessing the site. These should all resolve within 48 hours(realistically way less than that).

If you have issues beyond like the 3rd of April, email me at socialcubemanagem[email protected] which is a 13 year old email address I completely forgot existed until 10 minutes ago and will forward to my real one.

The move will be happening probably some time later today or tomorrow. This process is usually pretty seamless so you probably will not notice.

For the technically interested: We are moving to a different domain registrar and also routing through Cloudflare

Let's kick off 2025 with a (very) minor site update. Yeah, this one isn't very exciting... but hey, it's something.

What's different?

- Comments on news articles now correctly exclude those by blocked users.
- Notifications are no longer sent if the recipient blocked the user that performed the notifying action.
- Swear filter list updated. Now featuring 10% more brain rot.
- @Yenwood is no longer a Dill Pickle... for now, at least...

Just a heads-up, SocialCu.be is currently experiencing server performance degradation due to an issue with our server host. You might see pages loading very slowly as a result. They are currently working to resolve it, but have no ETA for it's completion yet.

Thanks for being patient.

Many of you probably know @umer936 who has been a mod here on SocialCu.be for a long time now. As people come and go, we occasionally need to make staffing changes to ensure we can keep the site running smoothly. After discussing internally, we feel confident in @umer936's ability to contribute to SocialCu.be and have agreed to promote him from mod to admin.

Going forward, this means that we'll have more hands to maintain existing site code as well as develop new stuff for SocialCu.be going forwards. No other staffing changes are occurring at this time and the existing admins will still be contributing code as well.

With all of that out of the way, feel free to congratulate @umer936 in the comments below. We look forward to having another great developer working with us here at SocialCu.be!

It's time for another feature update! The highlight?

Reacts!
After talking about bringing them to SocialCu.be for so long, it's about time they're finally here. If you've used discord or slack, you're already familiar with how these work. Simply click the little emoji in the corner to bring up an emoji picker which you can use to react to... well... what can you react to?

Turns out, a lot!

Reacts are supported on:
- Statuses (likes/dislikes have been converted to thumbs up/thumbs down emoji respectively)
- Comments
- News articles
- News comments
- Blog comments
- QN comments

(Note that there is a limit of 20 unique reacts to make sure that they don't go on for miles. Don't act like someone wouldn't have tried to react with every single emoji if we didn't do this.)

Also...

Quality of Life improvements!
- Redundant reply button to a status on the comments page has been removed.
- Replying functionality has been extended to the majority of the site for consistency.
- Tagging someone will only notify them once per post, regardless as to how many times you tag them
- The postbox for blog comments has been moved above existing comments for consistency.
- Several css files have been minified to reduce the initial page load time on slow connections.

This update was pretty extensive, so as usual, feel free to post in the bugs forum thread if you see anything that appears to be broken.

Enjoy!