![](https://piefed.social/static/media/users/9I/t0/9It0HTbhGmstX2F.jpg)
![](https://feddit.nl/pictrs/image/0e5ef11b-1841-4e8d-be66-21f6c31589ef.jpeg)
Hi. I raised an Issue on the crawler’s repo a couple of weeks ago. Still waiting for a response though …
aka freamon
Codeberg: https://codeberg.org/freamon?tab=activity
Anything from https://lemmon.website is me too.
Hi. I raised an Issue on the crawler’s repo a couple of weeks ago. Still waiting for a response though …
Yeah, maybe. I’ll leave it with you …
Fixed now - a community called "wave" music
caused a JSON deserialization error (because JSON uses "
for its own purposes).
It’s been 2 weeks since I raised the Issue for 0.19.4 / 5 instances on lemmyverse - given that there’s been no response, we might have to give up with these lists anyway.
Re: your edit - please feel free to open an Issue for PieFed about it. It’s MBIN content in Lemmy’s communities, so it’s something that needs attention (we should show it, even if Lemmy doesn’t). I’ll have a crack at fixing it next time I’m working on the code.
'Bin follows the same format as Mastodon for inline images, which is different from Lemmy.
Mastodon puts the details for an inline image inside an ‘attachment’ field, with nothing in the ‘content’ fields, whereas Lemmy doesn’t use an ‘attachment’ field at all for them, and includes the HTML for img src
in the content.
It’s always been the case that Mastodon didn’t show images from Lemmy comments. I don’t know if the reverse is a new thing or if it’s always been like that.
The last time I raised an Issue, the dev did respond, but it was a full week later. Maybe just considered low priority vs. other stuff in his life, rather than unmaintained. Hopefully, anyway. We’ll see …
For lemmyverse, the issue for it is here: https://github.com/tgxn/lemmy-explorer/issues/184
We’ll have to wait until that dev responds, or maybe until Lemmy devs change their mind about not providing a nodeinfo 2.0 response for 0.19.4 instances.
EDIT: ah, me and Blaze were commenting at the same time, it seems.
More and more stuff won’t feature as instances continue to upgrade to 0.19.4, as lemmyverse.net doesn’t yet support it (there was something like 582 instances listed yesterday on there, it’s 572 now).
Please use your mander account to inform OP that their instance is wildly behind .world - see here
The delay and eventual deletion of comments and votes will have an obvious effect on mander’s “hot” and “active” algos.
If you look at this post on mander, it’s not got any of the comments, so there’s no point anyone using a .world community to answer OP’s question.
Hello. This data is sourced from lemmyverse.net, which uses its own crawler, distinct from the lemmy-stats one. The underlying issue is likely the same, so I’ve filed a bug here (past experience suggests that the dev won’t be that quick responding to it though)
The instance I’m on is defederated from links.hackliberty.org. I’m not certain why, but I looked at it to find it’s a place for conspiracy theories, including ‘9/11 Truth’ stuff, so it’s probably that.
There looks to be a bit of indecision about the right instance for a new ‘privacy’ community, so I’m just mentioning this in regard to that.
Nothing yet for today (Sunday), because the crawler at lemmyverse has failed. More info is here: https://github.com/tgxn/lemmy-explorer/actions/runs/9434433542/job/25986550190 - it’s bailed because there are 6011 communities missing from that run compared to the previous one. I’ve seen that number before, which suggests it’s a single instance with that many communities which is failing to give a response.
EDIT: the midday run worked though.
That’s great to hear. There’s zero API at the moment though, let alone a stable one. PieFed is a monolith, without the backend / front-end split that necessitates an API.
It easy to add one, pending the addition of some missing features and a code reorganization that needs to happen anyway. At that point, hopefully some interested app developers will also be involved, to shape the API into something they may wish that other app’s APIs were like.
Buster should turn their attention to the size of the images uploaded to servers like this: 1.1M is arguably overkill for this one.
That’s the book I was referring to, yep.
I think most bread that’s available to buy is actually junk. Even the ‘wholemeal’ stuff, which itself obfuscates what you actually want: wholegrain. Ideally, the carbs percentage shouldn’t be more than 5 times the fibre percentage (according to the ‘How not to die’ book), but I’ve found that very little that actually meets that.
This is why people can become obese without understanding why: the over-processing of food considered as staples.
Most people will be unaffected ('cos their instance already has a copy), but trippingthroughtime has a broken outbox, so it won’t come with old posts if it’s a fresh discovery. Issue should be fixed in Lemmy’s 0.19.4 update.
This is for other frontends, but I remember reading something about image uploads not working when you’re self-hosting due an issue with CORS. I don’t know what CORS is, really, so can’t expand on it. It may be that you need to upload the image to a filehost like postimages.org and link to the inline version of that instead.
There seems to be some decent channels that are local to that instance (some PeerTube integration was recently added to PieFed, so I’m going by the list on this post ). From there, you can watch stuff from other instances, if course.
I made a post here: https://lemmy.world/post/16949903