I block all mags from all Cloudflare instances. So sometime after posting to homeimprovement@lemmy.world I blocked it. I still get notifications (which is good), then I unblock it just to read the response then re-block. That’s not likely related, but something happened in the past couple days that apparently caused a “seen” flag to get unset. It’s not in itself worth chasing up but maybe it’s a clue as to whatever happened.
if there's anything people can help with don't hesitate to ask in matrix!
One thing I wanted to raise to your attention was asdfzdfj's change to persist logging for docker setups which might make it easier to debug if your logs aren't persisted between container restarts
I mentioned in matrix but just in case since it's a bit of a gotcha for people that run in docker:
as a headsup for anyone running docker, there was a recent change to persist storage of logging just merged. it requires creating a directory and changing permissions on it. the admin guide was updated here but you may need to mkdir -p storage/logs and sudo chown $USER:$USER storage/logs where you run docker from by next sync/release
this may or may not be relevant to you depending on if sync'ing would change your compose setup
I am going to apply this upgrade this weekend. I spent a few hours looking through logs this morning but didn't see anything obvious (there are a breathtaking amount of logs) so gave up and restarted the containers. Will look again when it fails after I make log storage persistent
It's also possible there are no local subscribers, or weren't until now. It's one of the things we need to fix after updating subscriber counts to show accurate information rather than just local information, as it's unclear if a magazine has no local subscribers anymore
Hmm... looking at their instance list and stuff, I get the feeling they might consider fedia an "inactive" instance (based on the information being out of date), which is a bug lemmy has where after upgrades it marks instances as inactive and never updates it again. I will try to get in contact with their admins to confirm
Edit: quick edit, speaking with another german instance owner they said they have the same problem with feddit.de right now and have already spoken to the admins and already taken steps to reset active state but it isn't happening, perhaps more debugging is needed or maybe this is the lemmy federation issue people have been discussing
This might be the same issue that brought kbin.social to its knees, only fedia/mbin is giving up instead of the infinite retries which are crippling the other platform.
One comment in one of the kbin threads of a guy who hosts his own forked instance said it's probably caused by a Lemmy update, which I guess makes sense. kbin and mbin aren't the same code wise (can't even use the nsfw unblur here), and kbin is also a version ahead of mbin so they might just handle the same issue differently. A lot of the magazines / communities I checked have their latest threads from like a week ago when viewed through fedia. kbin ironically has similar examples, but different ones to fedia. Whatever the cause, it obviously shines a negative light on any 'bin instance and to a degree onto the fediverse. For me, I would really like to avoid having to deal with the shitty Lemmy UI and support the Lemmy devs directly.
I wouldn't exactly say mbin is behind kbin, as things have diverged much since the fork. For example, mbin has moderators from lemmy, and lemmy shows mbin moderators. As of latest, mbin gets moderator reports from lemmy (and maybe the other way, I didn't closely review that PR), things like sensitive groups are marked correctly, subscriber and follower counts come from source... Still, there's a lot of work to do for the user experience, many people have made that clear lately, so I'm hoping mbin will be able to gain the contributors needed to make the changes people want to see
Also, yea a lot of /kbin tweaks won't work. I do want to make an eye toggle button to make visible all nsfw on a page, but that might be hindered a bit due to infinite scroll (as well as a user setting to just have it shown by default). In the meantime though, it's just the structure of data changing from javascript to css, so it's always possible to do. I wrote a tampermonkey script able to do so as an example:
@jerry They range from 2.7 to 9.1 MB, though looking at the ones that did post successfully, they seem to be less than 5 MB. I think I ran into a size limit.
As the diff mentions the default max size is 6MB and 5s upload timeout. While php.ini declares 10MB defaults. It's a bit weird they don't match, but there's probably followup on 1. allowing instance owners to configure the size of images they are ok with hosting 2. maybe more research into what other platforms allow, there's a lot of discussion about thumbnails and the sort since remote instances cache things themselves, and broken thumbnails make things look like they aren't working across the fediverse
Ah, so it wasn't just me? I thought I must have done something weird with my formatting to mess up federation. Since the post you mentioned, this has happened on two moreposts with images and a link post. I'm not trying to break Fedia, I promise!
Ah, so it wasn't just me? I thought I must have done something weird with my formatting to mess up federation. Since the post you mentioned, this has happened on two moreposts with images and a link post. I'm not trying to break Fedia, I promise!
I think the issue now is with the containerized version of mbin. I tried saving money by running it in my container host, but it's clear to me that is not going to work out. So I will be rolling it back to a bare metal server :/
Given this is a software-the-instance-is-running request rather than an instance request as such, you might be better off posting on the (centralized 😅) mbin repo or perhaps asking about it on the mbin Matrix if they accept that kind of thing there.
You’re right, but my boycott against Microsoft makes Github a no-go, and my boycott against Cloudflare makes that matrix instance unusable to me. Though I have to admit I’m not too familiar with Matrix. Is it possible to connect to a non-CF matrix node and reach people who are on matrix·to?
Last time I checked, kbin/mbin only supports intra-instance messaging. I.e., you ( sender@fedia.io ) can message receiver@fedia.io , but not receiver@kbin.social or receiver@lemmy.world
There is no option to add blocks of any sort (mag/user/domain) from settings, so it's more likely to be intentionally designed that way, i.e. you cannot add nor see a note on a user by going to their page either, you can only hover.
From how I understand it, you cannot block an instance entirely by blocking a domain i.e. fedia.io/d/lemm.ee, what's blocked would be hosted content like lemm.ee/pictrs/..../[file] and not some link posted to lemm.ee/c/abc, you will have to block from the magazine page i.e. fedia.io/m/abc@lemm.ee to get rid of them one by one. Domain blocking is probably intended for sites i.e. fedia.io/d/www-bbc-com.cdn.ampproject.org
EDIT:
I still want to see comments from lemmy.world users.
I think this is achievable via visiting fedia.io/d/lemmy.world/comments if you're looking for a stream of any and all comments (not just replies to your own threads/posts), not completely certain though!
Most were suspended for child porn at various points - though I think it was not necessarily something they condone, but lemmy has damn near no ability to moderate or remove images once they land on a server
Ok. Maintenance completed. I've moved fedia.io to a container-based setup that is now running on my main infrastructure - a 48 core/96 thread AMD epyc zen4 genoa with 256GB of DDR5 ECC ram and 2x4TB nvme SSDs, backed by a dedicated database server with the exact same specs, on a 10gbps network.
The more I see of its sysop the more I like this place. Thanks for keeping it all running.
Whilst it's on my mind can you recommend a place to report general mbin bugs? It doesn't seem able to see m/baduk@lemmy.ml and a few others I've noticed. Neither was kbin until recently.
fedia
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.