• OldManGenghis@monyet.cc
    9·
    1 year ago

    Finally got the chance to talk to my cousin who was diagnosed with cancer. I try not to ask him anything related to cancer but it seems like every topic I ask is affected by cancer. He was so close to finishing his degree but that has to wait, he can’t do anything due to cancer fatigue.

    It feels like his world has stopped. We were very close when we’re younger as we are the same age, everything was a competition even to a lesser degree when we’re older.

    It’s not fair.

  • Annoyed_🦀 @monyet.cc
    8·
    1 year ago

    My uncle: you got girlfriend already or not?
    Me: no wor
    Uncle: why not find one?
    Me: got that easy find meh?
    Uncle: so hard to find meh?

    just kill me plz ( ._.)

      • ruk_n_rul@monyet.cc
        11·
        1 year ago

        Just one for [email protected]. I think I will cook a bot myself though, because I would need the bot to:

        • use templates
        • fill the templates with texts/images/links off of a spreadsheet
        • generate images, also off of templates (scripting done for this one)

        Plus I want to write it in Python 3. There’s a really good lemmy module by db0.

        I’m not in a rush so I’m fine with continuing to post manually for next week or 2 as I slow cook this.

        • zen@monyet.cc
          2·
          1 year ago

          if you are referring to https://github.com/db0/pythorhead then you must take care, both this and lemmy-js-client (and the whole lemmy stack itself) is under affero which is a viral license that has been touted as a preventive measure against big tech.

          ianal, but i think any network interaction with code derived from those 2 libraries must be placed under the same affero license.

          wefwef/voyager was hit by this exact licensing issue.

          • ruk_n_rul@monyet.cc
            11·
            1 year ago

            I’ll keep that in mind, thanks.

            Section 6 & 13 of the license is a bit of a headache though. Do I need to upload the whole bot script to, say, github, before I even start posting using the script?

            • zen@monyet.cc
              1·
              1 year ago

              i don’t think so. i think what’s important is that it stays under the same license, which means sooner or later you’ll have to disclose source, but i don’t think anyone is going to be so picky as to say you have to do it at the very beginning.

              in other words, as long as you are not intentionally withholding source, it should be alright, but again, ianal. anyway, yours is just a hobby project so no need to be so strict about it.

              i am just bringing to your attention the nature of the license involved, so maybe if you’re not that comfortable with it, you could look around for a more permissively licensed python lemmy library (if there’s even such a thing, considering the whole lemmy stack is already under the same license).

        • Naomikho@monyet.cc
          1·
          1 year ago

          Good luck with the cooking! There was a lemmy python API but I’m not experienced with python so I went for lemmy js client instead. I do plan to implement those features eventually too, but my technical knowledge isn’t great so I would need a lot of time to figure things out.

  • dukeGR4@monyet.cc
    1·
    1 year ago

    Went for a massage, the Vietnamese masseur asked me to relax then jump on my back…. Then used her elbow to press into my muscles with her weight, I was screaming and she asked : is it painful?

    Despite all that it’s a strangely comfortable massage if not a bit painful, focusing on acupuncture points. Some reason when you press really hard into these points your body releases lots of endorphin? Or sth like that? It feels very sore and syiok.

    The eye and hair massage was really good, didn’t know you could massage the brow ridge area. She even massage my tits lol it was so itchy I wanted to laugh

  • dukeGR4@monyet.cc
    1·
    1 year ago

    A used camera I recently purchased increased its market value by almost 50% in 6 months…

    not sure if I should sell it now or keep it.

  • Naomikho@monyet.cc
    1·
    1 year ago

    🎉Finally released the post auto-scheduling feature for Monyet.cc! I can already smell lots of required enhancements and other features that will require implementation… probably time to create a dedicated backlog for MonyetBot lol

    • zen@monyet.cc
      0·
      1 year ago

      unfortunately, something has gone wrong:

      https://lemmy.zip/c/[email protected]

      https://lemmy.world/c/[email protected]

      https://lemmy.ml/c/[email protected]

      https://lemm.ee/c/[email protected]

      https://beehaw.org/c/[email protected]

      all of them have the 28th july daily thread, but not today(29th july)'s, also looking at the sidebar on those instances, monyetbot is not listed as mod.

      you mentioned testing monyetbot on a dev instance. is the dev instance by any chance running the same database as this one (as in, all communities/posts/users from here are viewable there too, up to the time the db snapshot was taken, that is) and does not have federation disabled (2 instances with the same name both sending federation traffic could possibly badly confuse other instances)?

      the easy fix, without having to do too much debugging would be to try registering a new bot user, and see if it can be added as mod and accepted by the other instances, or you could try unmodding and then remodding monyetbot first.

      (unmodding and remodding would help if it was the modding that did not federate, another issue could be the membership of monyetbot in the community not federating, so perhaps try making monyetbot unsubscribe and resubscribe)

      edit: if this is not given attention, i think all future daily threads by monyetbot will not be available on other instances (oh god, i so hope i am wrong)

      edit 2: the instances are a mix of 0.18.2 and 0.18.3, so i don’t think the new version is the issue here

      edit 3: i think the main questions to ask are:

      • is the dev instance you tested the bot on running a snapshot of the monyet.cc db?
      • does the dev instance have federation turned on?
      • did you mod the bot on the dev instance in a community called cafe before doing it here on the main instance?

      if the answer is yes for all 3, then the modding event may have been sent out to other instances from the dev instance first, and so now the modding event from the main instance is no longer accepted by them, and with that all posts from the bot no longer federate (and neither do replies to those posts 😢 😭)

      • Annoyed_🦀 @monyet.cc
        0·
        1 year ago

        If you check the bot via other instance, the user simply didn’t exists. It likely due to this is the bot first post so it take some time to register the user to other federated instance…me think

            • zen@monyet.cc
              1·
              1 year ago

              i think it has been more or less confirmed, that for some reason monyetbot is not appearing as user on other instances, and with that all posts started by monyetbot will not federate, and neither will comments to those posts

              edit: i don’t think posting any more comments under monyetbot will solve the problem, as the search box is supposed to find users even with 0 comments, so other instances are just not accepting monyetbot

        • zen@monyet.cc
          0·
          1 year ago

          can you search for the bot username @monyetbot@monyet.cc in the search box of those other instances?

          if it does not appear, then we’ll very likely need to change bot usernames due to it not being accepted by other instances

          edit: just checked https://lemmy.zip/u/waiter_bot@monyet.cc is okay, so it is not that other instances are auto-rejecting bot users

            • zen@monyet.cc
              1·
              1 year ago

              maybe instances are rejecting bots that have admin status?

              but that would not really make sense

            • zen@monyet.cc
              1·
              1 year ago

              that’s because all of my new comments have been on this thread, which is opened by monyetbot which other instances consider non-existent, and so all comments on this thread are auto-rejected because the opening poster is rejected

            • zen@monyet.cc
              0·
              1 year ago

              correction, i also posted in announcements, but that is not federated to lemmy.zip: https://lemmy.zip/c/announcements@monyet.cc

              it is federated to lemmy.world though, and my last comment on there is from announcements

            • zen@monyet.cc
              1·
              1 year ago

              it may be a related issue, but as crabby has discovered, the monyetbot user itself is rejected by other instances, and other instances can’t list a user that doesn’t exist in their db as mod

      • zen@monyet.cc
        0·
        1 year ago

        oh great, lemmy turned all those links to other instances into links to our instance, so if you click on them you don’t see the issue

        • Naomikho@monyet.cc
          1·
          1 year ago

          I can see the issue if i open in incognito mode, but MonyetBot has been moderator of cafe for a while on monyet.cc actually. I’m not sure if both instances can affect each other though, as dev is monyet.lol, not monyet.cc

      • Naomikho@monyet.cc
        0·
        1 year ago

        No, the dev instance has its own database. Its whole ecosystem is separate from this one. It does not run the same snapshot. Last I remember, I think it did not federate, but I might be mistaken here… For the last question, the answer is yes because I had to emulate the scenario as closely as possible.

    • Naomikho@monyet.cc
      1·
      1 year ago

      Ah yeah… that was the initial name for the account :/ So there’s nothing that can be done to fix it right?

      • zen@monyet.cc
        0·
        1 year ago

        i can’t think of anything else besides the very risky option of editing the db directly, but you’ll probably have to ask the lemmy devs for the correct sql statement that would solve this.

        or, as a more temporary option, maybe this could be solved at the webserver level, by redirecting all requests to /u/frank_bot to /u/monyetbot (must take care to distinguish between requests to backend and frontend, both *ends respond to that http request (with different content types)) but that would just involve an nginx expert instead of an sql expert, and i am neither.

        • Naomikho@monyet.cc
          3·
          1 year ago

          @[email protected] I updated the db and it seems like it’s fixed. Thanks for helping! The solution was the actor_id for the user account was still pointing to Frank_Bot URL, which is already invalid.

          • zen@monyet.cc
            2·
            1 year ago

            oh that’s nice, may i know what sql statement you used?

            anyway, time to upvote everything in this thread so it federates over 🤣

              • Naomikho@monyet.cc
                1·
                1 year ago

                Oh wait… sorry @[email protected] I just realized I made a mistake there. T_T You actually cannot change your account name(only your display name) which I now understand the reason. I changed the account name a long time ago so I forgot that I changed the account name manually via the database without updating the actor_id and inbox_url correctly. E.g. the actor_id should be https://monyet.cc/u/MonyetBot instead of https://monyet.cc/u/Frank_Bot, which was the old URL.

                The reason you can’t change your account name is most probably everything relies on the actor_id to work, and if the actor_id is invalid, it won’t be able to federate. Even if they updated the actor_id and inbox_url, all your past post, comments and messages etc. should be tied to the old url, which won’t carry over after you change your account name.

                • zen@monyet.cc
                  1·
                  1 year ago

                  luckily we caught this early before monyetbot had a lot of posts. anyway, i think what’s even more important is the keypair in the db, so it is good the problems monyetbot had were not related to that.

                  by the way, you may want to do a sql dump and search if there’s any other reference to frank_bot that can be updated. i heard lemmy 0.18.3 (out last night) has quite a bit of db optimizations, so don’t want any outdated reference to cause issues with that.

          • zen@monyet.cc
            1·
            1 year ago

            alright, but please update even if it doesn’t work out, as being curious, i also like to know about all the other attempts at solving things