
Requirements Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a single bug? Do not put multipl...
![[Bug]: Last 3ish weeks of activity wiped after upgrading to 0.19.2 · Issue #4362 · LemmyNet/lemmy](https://lemmy.frozeninferno.xyz/pictrs/image/3e28f8d1-2f9a-4760-b60f-3cdee2644a27.png?format=webp)
Community for announcements regarding the Frozen Lemmy instance.
Maintenance complete!
All of the primary Lemmy services have been updated as part of this maintenance.
PosgreSQL database: 15 -> 16
pict-rs image repository: 0.4 -> 0.5
Lemmy: 0.19.3 -> 0.19.5
Also, as part of the migration, the pict-rs image repository's backend has been migrated from its internal sled-repo database to the shared PostgreSQL database, which will simplify backup and recovery in the future.
Please report any issues on this post or a new post in [email protected].
Thanks for your patience as we work to improve your Lemmy experience.
Maintenance downtime Saturday 9 August, 4PM UTC
We'll be taking the instance down for maintenance at 4PM UTC on Saturday 9 August. Use this to convert to your local time.
The instance will be upgraded to Lemmy 0.19.5, which requires upgrading several other services Lemmy relies on.
The maintenance window will be 5 hours
Maintenance unsuccessful, yet complete
We ran into some unexpected issues upgrading the instance to the latest Lemmy version, and troubleshooting was starting to take too long and extend past the previously given maintenance window. As such, we decided to restore from backup and attempt the upgrade again another day, next time with a larger maintenance window.
Everything should be back as it was before the downtime. The next maintenance will be announced soon.
Thanks for your patience!
Maintenance downtime Saturday 29 June, 2PM UTC
We'll be taking the instance down for maintenance at 2PM UTC on Saturday 29 June. Use this to convert to your local time.
The instance will be upgraded to Lemmy 0.19.5, which requires upgrading several other services Lemmy relies on.
The maintenance window will be 3 hours
0.19.1 to 0.19.2 Upgrade: We are currently being affected by some kind of bug
Requirements Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a single bug? Do not put multipl...
Not entirely sure what happened, but a routine backend upgrade from Lemmy 0.19.1 to 0.19.2 is causing issues with the past 3ish weeks of activity. The linked bug report has a bit more detail.
I'm going to try to work with the devs to figure out exactly what happened and do my best to recover that activity.
Maintenance complete!
The storage backend for the instance has been upgraded, which means the instance should be faster by quite a bit. It also enables a few new data resiliency features, which is pretty cool. Hopefully we don't need them, but better safe than sorry!
Please report any issues on this post or a new post in [email protected].
Thanks for your patience as we work to improve your Lemmy experience.
Maintenance downtime Friday 22 Dec, 6PM UTC
We'll be taking the instance down for maintenance at 6PM UTC on Friday, 22 Dec. Use this to convert to your local time.
This maintenance is due to a much-needed storage upgrade, which will hopefully speed up the instance quite a bit. The maintenance window will be 3 hours to account for full system backup and restore, but I'm hoping we'll be done quicker than that.
Now running Lemmy 0.19
We are now running Lemmy 0.19! There were a lot of cool changes in this release, definitely check out the release notes if you're interested in the specifics.
The important ones for users are:
There may be breakage depending on what Lemmy client you use, so be sure your client supports the breaking ch
Implementing defederation lists from Fediseer
In the interest of transparency, we're announcing the implementation of defed list synchronization from Fediseer.
Fediseer is a community of fediverse instances that work together to crowdsource classification of both safe and harmful fediverse instances. This instance has just recently been "guaranteed", which means a member of the Fediseer community has sponsored us to join them. You can see details of our Fediseer presence here.
This enables a couple of things.
Given this instance's stance towards censorship, we've been hesitant to implement block list synchronization, as we don't want to block an instance prematurely. However, given the recent influx of loli / pedo content creeping in, we feel it's in t
Maintenance downtime Monday 23 Oct, 5PM UTC
We'll be taking the server down for general maintenance at 5PM UTC on Monday, 23 Oct. Shouldn't last more than an hour.
Use this to convert to your local time.
Defederating from burggit.moe and a rules update
Hey All,
First point of business, we're defederating from burggit.moe effectively immediately. I'm currently purging all burggit.moe communities, but if I miss one, please report it. The reason is closely tied to the second point of business.
Second point of business, I never thought we'd have to do this, but we've added a 6th rule: No loli / pedo shit. Pretty self-explanatory and straightforward. We don't care if it's "technically" legal, we're not hosting it. I don't even know if it's actually legal where the server is physically located, and I'm not putting that in my search history.
Again, we're staunchly against almost all types of censorship, but if that's the kind of material you're after, we have to ask you to look for it on another instance.
Now hosting Photon, an alternative UI for Lemmy!
We are now hosting Photon at https://photon.frozeninferno.xyz! I've personally used a few different alternative front ends for Lemmy, but this is the first one I liked enough to host myself. Please feel free to leave any feedback here, and enjoy!
P.S. If you don't like Photon, the default Lemmy UI is still available at https://lemmy.frozeninferno.xyz as always. :)
P.P.S. If you want a wider interface (for desktop, for example), go into settings in the top right and disable Limit Layout Width.
Defederating from rqd2.net
I received a user report of (text) pedophilia on a post from rqd2.net. I considered banning the user, but after further investigation, much of that entire instance is dedicated to similar content. As such, I've decided to defederate from the instance.
As much as I dislike censorship and want users to be able to decide for themselves what they do or don't see, I don't feel comfortable hosting or providing access to content like that.
Edit: I'm also in the process of purging all rqd2.net communities from this instance. If I miss one, please report it.
Scheduling maintenance downtime for Monday 5pm UTC
Fixing the image database has started causing increased disk usage, so I'm scheduling some downtime to move the database to a larger storage device.
The downtime should be no longer than 30 minutes.
Here is the specific time converted for your local time zone (if you have browser location services enabled.
Issues with images
Sorry, everyone, but I had the image database misconfigured, and it wasn't properly retrieving thumbnails and some other image content. This issue has now been resolved, I believe, but if you notice any other oddities around images and pictures, feel free to respond here.
Scheduled downtime
Lemmy services will be restarted every day at 4am CDT (9am UTC)
This has been implemented for a while now, but I never made an announcement. I noticed a few weeks ago that Lemmy seems to have federation issues when left running for longer than a few days, so I figured a quick daily restart would be the solution, and it's been working so far.
Using lemmony tool for a more populated "All" feed
A better "All" browsing experience for Lemmy instances - jheidecker/lemmony
There will be a lot of new communities added to the "All" feed by this tool, some maybe NSFW.
Signing the FediPact
I've been mulling it over for a while, but I've decided to sign the FediPact1, pledging defederation for any and all Meta-owned ActivityPub instances (Lemmy, kbin, Mastodon, Threads, etc.).
There may be some real value in exposing such a large audience to the fediverse, but I believe the risks outweigh any potential benefits. Embrace, extend, and extinguish (EEE) is a strategy that companies use to stifle competition and innovation, and I don't want to support Meta in any hostile takeover they may be imagining for the ActivityPub protocol.
Also, the teardown of the leaked Android version of Threads shows that Meta is planning on federating political ads2. So yeah, you're welcome.
1The FediPact can be found here.
Defederating from exploding-heads
Alt-right instance with intentions on infiltrating other big instances. Falls under Rule 2.
Frozen Lemmy up and operational!
Hello, welcome to my Lemmy instance! Feel free to take a look around.
Lemmy is a federated link aggregation platform. You're familiar with the "link aggregation" part, I'm sure (think Reddit), but probably not so much with the "federated" part.
A federated platform is one in which individuals and/or communities create their own instance of the platform and share content between them. Think about it like two cities existing independently, but trading goods and services. lemmy.frozeninferno.xyz is an independent instance, as is lemmy.ml, but they can communicate with each other and share content.
Each Lemmy instance will host and make visible locally any content that has been either created locally or federated by a user. This means you'll see any communities (think subreddits) created locally, as well as any communities from other instances that a user of your instance has joined.
For example, I have joined [[email protected]](h