I think it’s not really on your side, most likely either just something wrong on kbin.social itself, OR a side-effect of the measures lemmy.world implemented against kbin.social recently.

They are basically local-only communities on lemmy.world at this point, unfortunately. There is no federation to any other instance for any lemmy.world user posts on those communities.

You haven’t been doing anything wrong from your side - we have just been experiencing some growing pains with a new Lemmy feature (image proxying).

It’s a bit unfortunate that these problems cropped up, but ultimately we will benefit from this new feature, as it will help solve several issues with Lemmy image hosting overall. So I hope you can forgive the issues and trust that the end result is worth it!

Ahh I see the issue & have fixed that example post now.

Basically, I had already fixed the root cause which was breaking the images, but there was a period while I was working on the fix during which some images posted would remain in a broken state. I don’t unfortunately have a fast way of automatically detecting and fixing those broken images unfortunately, but I can fix them one by one manually.

Having said that, any new images posted now are not getting broken. I’ll see what I can do about the broken ones, maybe I can find some way to automate fixing them.

Hey, I’m not seeing any issues at the moment, can you share more details about what is broken for you currently?

I’ve made a few PRs to hopefully improve the image situation, these are all running on lemm.ee as of now as well, so hopefully it’s better now!

https://github.com/LemmyNet/lemmy/pull/4871

https://github.com/LemmyNet/lemmy/pull/4875

https://github.com/LemmyNet/lemmy/pull/4874

Maybe this community is a good target for that? Let me know your thoughts.

FWIW I know some users often check their local announcement/support communities through other instances during downtime, so it can actually be quite nice to have such communities federated to other instances.

The maximum file size limit for images hosted directly on lemm.ee servers is always visible in the sidebar of our front page. The limit stands at 500kb per image currently.

Additionally, It’s also possible to post images larger than 500kb, they just have to be hosted externally. The markdown for this is ![alt text](image url)

I’ve made some experimental changes, please let me know if you notice any difference

I’ve implemented a workaround for the imgur rate limiting now!

I’ve changed the logic now to no longer proxy imgur images, so their rate limits should no longer affect us!

deleted by creator

Thank you, that’s super useful, I will try to investigate what was going on with that request

Hey, I don’t actually see anything abnormal in terms of metrics. What continent are you connecting from (if you don’t mind sharing)?

Do you know around what time it got slow for you?

Hey!

Around June 9th I found that I could no longer display images in comments & posts. The specific problem seemed to stem from some broken code that was being auto-added

This is most likely due to the imgur rate limiter which is blocking our server (Basically our server is trying to request too many images from imgur). I have a plan to bypass our image proxying for a handful of known image-hosts, such as imgur, but haven’t been able to implement this yet. But it’s coming soon!

In general I intend to keep image proxying enabled for most other sites, though, because it allows protecting the privacy of lemm.ee users, as well as ensures slightly faster page load times compared to always making users fetch images directly from their original host.

But sadly, there’s more. Namely, it seems that lemm.ee communities are no longer showing up in one of the significant FV search engines, i.e. “lemmyverse.net.”

This requires fixing on the lemmyverse.net side - they currently only have support for older Lemmy versions, but I believe it’s only a matter of time before this gets fixed.

I think there are two separate things I want to address here:

First, agile isn’t a project management methodology, it’s just a set of 4 abstract priorities and 12 abstract principles. It’s very short, you can check it out here:

https://agilemanifesto.org/

Nothing here says that you’re not allowed to write documentation, write down requirements, etc. In fact, the principles encourage you yourself as a software team to create the exact processes and documentation that you need in order to meet your goals.

“Working software over comprehensive documentation” does not mean you aren’t allowed to have documentation, it just means that you should only write documentation if it helps you build working software, rather than writing documentation for the sake of bureaucracy.

“Individuals and interactions over processes and tools” does not mean that you should have no processes, it just means that the individuals in your team should be empowered to collaboratively create whatever processes you need to deliver good software.

Secondly, in terms of practical advice:

1. Talk about this problem with your team. Is it hard for others to figure out where requirements came from? Maybe they already have a good method and can share it with you. If it’s hard for everybody, then propose improvements to your process, for example, propose some type of design document process as part of building any new features
2. There are no perfect answers to the question of “how do I safely make non-trivial changes to systems”, but the general approach is to ensure that:

a. You have metrics about how your system is used.

b. You have automated tests covering any requirements, so that you can feel confident when making changes to one part of the system that it isn’t violating any unrelated requirements.

c. You actually document any confusing parts in the code itself using comments. The most important thing to cover in comments is “why is this logic necessary?” - whenever something is confusing, you need to answer this question with a comment. Otherwise, the system becomes very annoying to change later on.

If you are missing any of the above, then propose to your team that you start doing it ASAP

3. At the end of the day, somebody is responsible for making product decisions. Is it your team? Or maybe some separate product owner? Sometimes, you just need to communicate with whoever is responsible to figure out if any requirements are still relevant, or if they are now safe to change.

It’s not really a bug, it’s just a case where app developers need to update their code to support a small change in the Lemmy API. More details here: https://lemm.ee/post/34259050/12479585

It’s occasionally breaking for us due to imgur rate limiting the lemm.ee server. I am planning to disable proxying for a few well known image hosting sites (including imgur) soon - it requires some additional development, but I think I’ll be able to do it in the next few days. Sorry for the inconvenience!

Hey, this post is quite old, actually you can find the latest info in the sidebar of our front page:

• Image uploads are enabled 4 weeks after account creation
• Image upload limit is 500kb per image

Hey! Thanks for the report.

I think the first issue is not something I can help with - probably the Connect app needs to fix something on their side.

For the second issue, see my comment here: https://lemm.ee/post/34118135/12479638