[–] 25 points 1 month ago (12 children)

Umm no? Have you never vomited? I'm not sure I'd call that "food". I guess, maybe, it's still food after you've finished chewing it; you could spit it out into your hand instead of swallowing, and someone else could choke it down. But it stops being food long before it hits the intestines. At some point when it starts mixing with stomach acid, probably.

  • source
  • [–] 13 points 1 month ago* (1 child)

    I'm surprised nobody hasn't already posted the inevitable: “Do you wish me a good morning, or mean that it is a good morning whether I want it or not; or that you feel good this morning; or that it is a morning to be good on?”

  • source
  • [–] 4 points 1 month ago

    And this is why anything that tries to block AI scraping will always, in every case, block screen readers. It's not a side effect. It's a natural outcome of the design.

  • source
  • [–] 3 points 1 month ago

    So glad you're showing me the path where your code is stored, and the name and username to access the postgresql database. As a user, this does me no good at all. As an attacker, this is the first step I need to hack into the system.

  • source
  • [–] 8 points 2 months ago (1 child)

    This is a problem with Lemmy on the admin side. I set up retention, and any post here is automatically deleted if it's more than a year old and nobody has interacted with it. But I had to write a lot of custom scripting to handle that, and it still screws up: I was somehow counting profile photos as posts, deciding they got no interaction, then deleting everyone's profile photos. I fixed it, of course, but that isn't something admins should have to handle from scratch, by hand, on every server. No instance owner can afford to store everything, forever, for free, for users. Especially in this market where memory and hard drives are soon going to cost as much as my house. This instance is funded entirely by me, at about $200 per month, located in a Canadian data center. But $200 is a hard cap; I need to find ways to ensure we stay within that monthly amount, or try and raise money from a collection of my fellow blind users, who likely have nothing to spare. This isn't a beg post, just trying to give you insight into the realities of instance hosting. Right now Lemmy expects that all admins are okay with media and database storage that expands for ever and ever, infinitely. Most of us are not. Meaning that if we're technical enough, we can write our own custom solutions to handle it. Or if we're not, our only recourse is banning users to force Lemmy to delete whatever's filling the disc.

    I'm a well federated instance, so I guess I could make a contract to sell all the data I get to an AI provider, and that would allow me to afford to store everything forever. But I'm not willing to do that, and I suspect if I tried every other instance would defederate us anyway.

  • source
  • [–] 3 points 2 months ago

    Interestingly, on my instance LiveThreadBot's edits were way behind. I'm an admin, so I could check our incoming queue and see them building up. We're on quite a large server (quad-core, 64 gigs of ram, etc) in a data center with excellent connectivity. So if we were having that problem, I assume a lot of instances were. For sports a backlog of five or six edits that your instance hasn't processed yet just won't work.

  • source
  • parent
  • context
  • [–] 6 points 2 months ago* (1 child)

    Edit: autocorrect

    Another problem might be lack of algorithm. No, hear me out! Sure, the Algorithms on big social media lock us all in our little bubbles. But even there, I often have a moment of "Why on earth is that in my recommended?" I personally don't care about e-sports, so I had absolutely no idea it was even happening anywhere on fedi, and would be unlikely to find out unless I went looking. I wonder how many sports enjoyers are on Lemmy, all assuming "Lemmy isn't a sports place", so they never look for sports content, and thus never find any? I enjoy a couple twitch streamers and some VTubers, so occasionally youtube goes "yolo" and throws some kind of e-sports thing my way. I never click it, but I am vaguely aware that DOTA2 is an esports thing that exists and people care about it, and sometimes a big event or tournament or something happens, and I could follow it on YouTube or Twitch if I wanted to. But because Lemmy has no algorithm and I would never subscribe to an e-sports sub myself, I'll just never encounter it here.

    PS: I'm not old and out of touch. I'm completely blind and out of touch with esports because it intersects in zero ways with anything I can perceive, participate in, or care about. LOL

  • source
  • parent
  • context
  • [–] 8 points 2 months ago

    Second comment to add an unrelated thought. As big tech platforms crack down harder and harder, the fediverse could easily gain popularity by becoming the home of sports piracy. Just an instance you could visit to find the latest working stream for any given game would attract a lot of folks, I would think. It's just a matter of finding a group willing to take on that amount of risk. However, I'm not sure this gains the fediverse the reputation or audience we want.

  • source
  •  

    All services on rblind.com will be down for 6 hours on August 18th, 2026.

    • Date: 18-08-2026
    • Start Time: 7:00 AM EST
    • End Time: 5:00 PM EST
    • Expected Downtime: Approximately 6 hours

    Services effected are:

    The RBlind discord will remain functioning as normal, and the ourblind.com website will also remain available. Thanks for your understanding, and see you on the other side!

     

    cross-posted from: https://rblind.com/post/17753100

    In this article, I will discuss the details of 10 innovations throughout history that were only possible through unlocking the power of accessibility and including the voices of people with disabilities. In the disability community, it is a deeply believed and often repeated fact that improving accessibility leads to innovations that improve the world for everyone. Necessity is the mother of invention is, after all, a proverb so frequently quoted that it has become a cliché. And yet, people with disabilities still find ourselves left out of research and design, and all too often we don’t get a seat at the product development table. This leaves our inventions overlooked, unrecognized, and sometimes unrealized.

     

    cross-posted from: https://rblind.com/post/17753100

    In this article, I will discuss the details of 10 innovations throughout history that were only possible through unlocking the power of accessibility and including the voices of people with disabilities. In the disability community, it is a deeply believed and often repeated fact that improving accessibility leads to innovations that improve the world for everyone. Necessity is the mother of invention is, after all, a proverb so frequently quoted that it has become a cliché. And yet, people with disabilities still find ourselves left out of research and design, and all too often we don’t get a seat at the product development table. This leaves our inventions overlooked, unrecognized, and sometimes unrealized.

     

    cross-posted from: https://rblind.com/post/17753100

    In this article, I will discuss the details of 10 innovations throughout history that were only possible through unlocking the power of accessibility and including the voices of people with disabilities. In the disability community, it is a deeply believed and often repeated fact that improving accessibility leads to innovations that improve the world for everyone. Necessity is the mother of invention is, after all, a proverb so frequently quoted that it has become a cliché. And yet, people with disabilities still find ourselves left out of research and design, and all too often we don’t get a seat at the product development table. This leaves our inventions overlooked, unrecognized, and sometimes unrealized.

     

    In this article, I will discuss the details of 10 innovations throughout history that were only possible through unlocking the power of accessibility and including the voices of people with disabilities. In the disability community, it is a deeply believed and often repeated fact that improving accessibility leads to innovations that improve the world for everyone. Necessity is the mother of invention is, after all, a proverb so frequently quoted that it has become a cliché. And yet, people with disabilities still find ourselves left out of research and design, and all too often we don’t get a seat at the product development table. This leaves our inventions overlooked, unrecognized, and sometimes unrealized.

     

    Good morning, everyone:

    After months of troubleshooting various performance issues, we're pleased to announce that all of the outstanding back-end issues we are aware of are fixed. You should no longer receive errors on browsing user profiles, and posts should load much faster.

    If you're not technical or interested in the gritty details, you can stop reading, now, in the knowledge that everything should now work as expected. For those of you who are technical, the problems were caused by two things. First, a lack of indexes on the users and posts tables. Analysing logs revealed some database queries were taking upwards of 8 seconds, especially when loading user profiles. If you've landed here from Google, because lemmy-ui is giving the unhelpful message "an error has occurred on the server" without actually showing you the error, and you're seeing enormous queries referencing dullbananas's or i_love_jesus in your logs, get into your postgresql database and add some indexes:

    CREATE INDEX idx_post_aggregates_creator ON post_aggregates (creator_id);

    CREATE INDEX idx_post_aggregates_scaled_rank ON post_aggregates (scaled_rank);

    CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_post_saved_person_post ON post_saved (person_id, post_id);

    CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_community_moderator_community_person ON community_moderator (community_id, person_id);

    CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_local_user_admin ON local_user (admin);

    Second, be careful when increasing your shared memory size in docker. If you have shm_size specified as "48 gb" or "48gb" in your docker compose, your shared memory will not increase, and you won't get an error message of any kind. Shm_size must be "48g", no space, and no b. For some bonus fun, shm_size only updates if you recreate the entire docker image. Restarting is not enough! You should always use df on the docker you're working with, to insure /dev/shm is actually the size you think it is. Because it probably isn't!

    Happy holidays, everyone. Here's to a 2026 of stability and new features.

    view more: next ›