• 0 Posts
  • 7 Comments
Joined 3 months ago
cake
Cake day: April 9th, 2024

help-circle
  • “us/them” mentality doesn’t help much. this is surely a great fuss for a 3 year old pr but you’re misrepresenting the situation:

    • serenityOS (and consequently ladybird) has rather strict rules about wording documentation: they enforce language style and even date formats
    • that wasn’t a report, but a PR: rather than pressing ~50 keys on your keyboard and then a “lock” button he could have just pressed the “merge” button and integrated those ~10 total characters changes
    • github issues are routinely used to fix wording: documentation often lives on git and it’s useful to have it version controlled, even plain documents without attached source are kept on git so that their edit history is accessible and manageable

    folks are making a big fuss but Andreas really set himself up: just say sorry and change 4 words, such a weird horse to die on




  • thanks for saying this! i really don’t want to victim blame itsfoss for getting traffic spikes but if you cant handle ~20MB in one minute (~400kbps) of traffic you’re doing something really really wrong and you really should look into it, especially if you want to distribute content. crying “dont share our links on mastodon” also sounds like hunting windmills, block the mastodon UA and be done with it, or stop putting images in your link previews for mastodon, or drop link previews completely. a “100 mb DDOS” is laughable at best, nice amplification calculation but that’s still 100 megs


  • consider that caching happens at thousands of levels on the internet. every centralized site has its content replicated many many times in geo local caches, proxies and even local browsers. caching is a very core concept for the internet. others often bash AP because it replicates a lot, but that’s kind of like explicit caching: if the whole fediverse network fetched a post from it source, millions of requests would beat small servers down constantly. big servers cache the content they intend to distribute and handle the traffic spike instead of the small instance. small instances on their hand dont need to replicate as much and can rely more on bigger instances, maybe cleaning their cached content often and refetching when necessary. replication is a feature, not a design flaw!


  • yes because how a factory produces goods is independent from its workers well being, right?

    code is made by people, pushing away good contributors will lead to worse code, stressing contributors will lead to worse code, splitting contributor communities will lead to worse code

    if you really only care about code quality why are you bothered by identity talk? leave it to those affected and go back looking at code