GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by Administrize (admin@cawfee.club)

  1. Embed this notice
    Administrize (admin@cawfee.club)'s status on Sunday, 26-Jul-2026 21:30:51 JST Administrize Administrize
    Sorry for Cawfee suddenly being slow again, I don't know what's causing it or where to even debug this. Reboots didn't help, disk space is probably not it, and we're not getting scraped as far as I know.
    In conversation about 15 days ago from cawfee.club permalink
  2. Embed this notice
    Administrize (admin@cawfee.club)'s status on Sunday, 26-Jul-2026 21:30:50 JST Administrize Administrize
    in reply to
    • Administrize
    If it's too much of a pain in the ass, bloat.cawfee.club feels a bit faster, maybe even is, and I bet it burdens the server a bit less.
    In conversation about 15 days ago from cawfee.club permalink
  3. Embed this notice
    Administrize (admin@cawfee.club)'s status on Tuesday, 03-Jun-2025 08:19:42 JST Administrize Administrize
    Hey. During the weekend, I ran the numbers in order to find out what are the top (Mastodon) instances that have us blocked, solely in order to block off some deaf driftwood clogging our pipes. I was surprised to see that even mastodon.social, the flagship, was just around 1% of objects created in the database in the last few months. So there we go, I'm opening up federating with all instances (that we didn't block before). The additional load shouldn't be too high, but I'll keep an eye on it.

    mastodon.social is getting blocked anyway lol.

    During the last few weeks (since getting Cawfee back up), I also monitored the Known Network timeline a little and it's pretty evident that poa.st and misskey.io are kind of dominant there. So for the sake of wolesome diversity, those two instances are getting removed from the Known Network. No hard feelings against anyone there, you can still follow the accounts etc. It's mostly a gut feeling. (Maybe it will slow down the influx in unexpected ways, although I wouldn't bet on it.)
    In conversation about a year ago from cawfee.club permalink

    Attachments

    1. Misskey.io
      Misskey.io は、地球で生まれた分散マイクロブログSNSです。Fediverse(様々なSNSで構成される宇宙)の中に存在するため、他のSNSと相互に繋がっています。 暫し都会の喧騒から離れて、新しいインターネットにダイブしてみませんか。 お問い合わせはこちらhttps://go.misskey.io/support Powered by Misskey

  4. Embed this notice
    Administrize (admin@cawfee.club)'s status on Saturday, 31-May-2025 07:29:35 JST Administrize Administrize
    in reply to
    • r
    • Vokainen
    @vokainen099 @r Sure.

    >How much space did it save in the end?
    If I remember correctly, 34 GB. The objects table got pretty much halved. As for activities, only about 2 GB got removed after 16 hours of running it on my laptop. When it ran directly on Cawfee for weeks, it was probably even less, but that's the throttled block storage for ya.
    Of course you'll have to squash/repack afterwards to reclaim the space.
    >Did you also pass the --prune-orphaned-activities argument?
    Yeah. That's the slow part. The queries have multiple joins, phnt said it can't really be done any other way. But years ago when only Akkoma had this, I took their commits and it took less than a day. (https://info.cawfee.club/soti-2024-04.html) The Pleroma implementation is different.
    It didn't even get to the second query.
    In conversation about a year ago from cawfee.club permalink

    Attachments


    1. https://cawfee.club/media/35/de/bf/35debfbe76191c79545cb41a2d202f15263c2dc439702886c31c0dd3896ce1ef.png
    2. Domain not in remote thumbnail source whitelist: info.cawfee.club
      State of the Instance (April 2024)
  5. Embed this notice
    Administrize (admin@cawfee.club)'s status on Wednesday, 14-May-2025 21:50:09 JST Administrize Administrize
    One two. One two. Is this thing on?

    *ahem*

    Brothers, xisters, welcome back. As you probably know, Cawfee Club has unprecedently been down for a month. What started as a weekend maintenance, kept dragging on and after a week or two, I became increasingly despondent and my mental state spiraled downwards. It was pretty much this feedback loop when the longer the instance was down, the less I felt like fixing things. So yeah, you could say it's my fault.

    I could apologize endlessly, but for now, just seeing the levels of activity on here so high after only a few hours moves me beyond words. I really love you guys, and I missed you a lot.

    A thorough explanation will come later. For now though, there's a particularly vile bit of disinformation I have to debunk - this downtime was NOT caused by updating Pleroma. I did not update Pleroma. I'm looking at you, hakui.

    That being said, we'll be federating in whitelist mode for at least a day or two so that the server is not overloaded by catching up on too many posts. I'm open to adding any instances to the whitelist, just tell me the domains in response to this post.
    In conversation about a year ago from cawfee.club permalink
  6. Embed this notice
    Administrize (admin@cawfee.club)'s status on Saturday, 23-Dec-2023 19:00:49 JST Administrize Administrize
    And we are back! The maintenance was a huge success and over 60GB of flotsam was removed from the database. In case of any problems, report them immediately. :cirnosmile:
    In conversation Saturday, 23-Dec-2023 19:00:49 JST from cawfee.club permalink

User actions

    Administrize

    Administrize

    Basically @grips.Announcements, administration log, downtime notices... all that stuff.

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          225741
          Member since
          23 Dec 2023
          Notices
          6
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.