I had a complete mental collapse, as well as some legal troubles that lead me to completely delete all of my Lemmy accounts. I was formerly jawa21, and decided to get an upgrade to jawa22. Like it or not, I am back for good and I am currently working on more edits to post here.

    • jawa22OP
      1·
      7 小时前

      It’s kind of funny. My original IRC handle was jawaslayer, because “Who would slaughter innocent Jawas?”

  • teft@lemmy.world
    28·
    2 天前

    Are you a transporter clone, a replacement chief from the future, a parallel universe ensign, or a genesis device regenerated vulcan?

    Welcome back regardless of your cloning techniques. We missed you.

    • jawa22OP
      22·
      2 天前

      I am a genesis device regenerated Vulcan transporter clone from the future that was recently promoted to cheif. I hope that helps.

    • jawa22OP
      11·
      2 天前

      Thanks! I’ll have you know that the weird spot you made in Kirk’s armpit still haunts my dreams, btw.

    • jawa22OP
      9·
      2 天前

      Thanks! And, umm, I’m not sure how to put this but your captchas for sign-ups are broken :p

      • Admiral Patrick@dubvee.orgEnglish
        5·
        2 天前

        On my instance?

        The only issue I’m aware of is the hosted instance of Tesseract I run (for anyone to use) was down yesterday evening / last night because the hosting provider had a DC migration go terribly wrong. My main UI and API are hosted in a different DC and shouldn’t have been affected.

        Just curious b/c if there’s a problem I want to fix it lol

        • jawa22OP
          4·
          2 天前

          I tried for a solid 20 minutes to get beyond the captcha. It threw an error every time saying it was incorrect, but not a normal "failed " type error. It was completely broken. And yes your instance

          • Admiral Patrick@dubvee.orgEnglish
            4·
            2 天前

            Huh. I do show the HTTP 400 responses in the logs for the registration attempts, but not sure why. Maybe my rate limit got triggered? (it’s set pretty low, but hasn’t changed in over a year and have had successful signups since then). I don’t show that it even created the local user, which means it didn’t even process the request.

            AFAIK, nothing in my infra relies (exclusively) on my assets in the NYC DC that was down.

            FWIW, I just did a test signup, and it worked.

            So only things I can think of is:

            1. It failed to send the verification email (I think Lemmy fails if it’s configured to send an email for a specific operation and the email server doesn’t respond).
            2. Rate limit (which you’d think would have been HTTP 429 from the API, but wouldn’t be the first HTTP standard the lemmy devs didn’t adhere to).

            Either way, I’ll keep an eye on it (thanks for letting me know), and again, welcome back.

        • jawa22OP
          6·
          2 天前

          It worked with a browser, but not the Voyager app. Odd!

          • OpenStars@piefed.socialEnglish
            2·
            2 天前

            There seems many issues with Voyager lately it would appear.

            I tried to see it myself, after having recently deleted its storage for other reasons. So as a guest, using its default of Lemm.ee (or perhaps I had set it to that?):

            1. it doesn’t show the tenforward community in the left-hand side-bar list of all communities
            2. when I found the community by searching, I couldn’t find this post in it. https://lemm.ee/instances claims that Lemm.ee is federated with your instance though, and likewise in reverse? https://lemmy.blahaj.zone/instances
            3. I tried to switch instances to lemmy.blahaj.zone, but Voyager has never heard of any such thing, it reported.

            All of this is on Android for me. And the app looks up to date as of April 29.

            I’m not saying that literally everything is broken in Voyager, but all of these things above seem to be, for me. You may need to try a different app. I use the web browser UI of PieFed, or still the web browser UI using a Lemmy alt. Thunder is nice, and is FOSS, though definitely has a different look and feel to it, like the images are shortened in height unless you click them to display unlike Voyager. There’s also Interstellar that offers support for PieFed (which Thunder will add officially soon-ish) and also Mbin instances, but it displays images more like Thunder.

            You might need to switch apps, if Voyager doesn’t push a bug fix soon!:-)

            • aeharding@vger.social
              6·
              2 天前

              Hi! I’m the voyager dev. I haven’t heard of any users with the issues you are listing, and I haven’t heard no problem logging into browse as a guest. Also you can explore local communities in the “explore” tab of search. Otherwise it will show top 50 federated communities when logged out for better default user experience.

              Also I’m not sure why you didn’t see the post in the community. I’ve never had or heard of issues there.

              The gifv image thing is a bug though.

              If you have issues in the future, please explain them on !voyagerapp@lemmy.world or GitHub issues, with detail and screenshots if possible. It will help make the app better for everyone, instead of a random comment that I might not see :-)

              e: typo

              • OpenStars@piefed.socialEnglish
                3·
                1 天前

                Thank you for responding:-).

                Clearing the cache and data and restarting my Android device makes this post show up. So now I’m not reproducing it not showing up, but at least if it helps to know that doing so will solve that issue, I thought I would pass it along. This is app version 2.33.0.

                I still can’t seem to find blahaj though. In fact, clicking around on the labels, I see all sorts of instances on all of those buttons, except when I click lgbt I don’t see any instances. I can see furry, activism, niche, general, tech, all of the offers, except nothing for lgbt. From my device I can access https://lemmy.blahaj.zone/ in a web browser, but not in Voyager using an instance search (clicking instance at bottom middle, saying lemm.ee by default, then click GET STARTED, then PICK ANOTHER SERVER) or an attempt to see a listing of instances by clicking lgbt in that top bar.

                I hope this helps you diagnose this oddness - I don’t use any Lemmy apps, or really even Lemmy itself anymore, but when I did I considered Voyager the most strongly developed and visually appealing of all the Lemmy apps, so I hope it continues to be that way for as long as humanly possible:-).

              • OpenStars@piefed.socialEnglish
                1·
                1 天前

                Omg thank you that’s amazing! 🥰 I think you just made Thunder my absolute favorite Lemmy app.

                Which doesn’t do me much good now that I’m on PieFed, but soon™… the official support is coming, and then it can offer me an alternative to the web view.

                And now that I know to look for it, I see this setting in Interstellar, which already offers support for PieFed.

                Thanks again! 😀👍

            • aeharding@vger.social
              1·
              14 小时前

              Where did you hear this? Voyager has excellent markdown support with an implementation that closely matches Lemmy-ui.

            • MelodiousFunk@slrpnk.net
              4·
              2 天前
              Tap for spoiler

              Here is some markdown, posted from Voyager

              • there are some media types that seem to get mishandled
              • some of that was addressed in a recent update to both the app and Lemmy itself
              • some things still “fail to load” occasionally

              t
              l
              ;
              d
              r

              Voyager isn’t perfect, but this isn’t a markdown issue.

    • jawa22OP
      9·
      2 天前

      Not much better, but better. Thanks to some kind people here I was able to get help. It was a rough time, eating like a broke college student at 43.