Okay, there’s a frustrating backstory that I won’t bore y’all with, but in this case, my Lemmy-mates have suggested that I should share image-content more slowly, rather than do roundups like this.

To explain: I personally hate withholding content when I have a load of some resource to share. I feel like a fraud, an a-hole, a userer, and all that stuff…

Yet I’ve been told repeatedly that it’s better to just (in my words, ‘act like a drone’) drip the content, and yes, it’s not hard to see the logistical point, but… bah.

I guess, end of the day, I always like to include something interesting about my posts, and it would be harder to do that via the “drip” posting method, which… pretty much circles back to why I post the way I do, which is to aim for roundups.

Bah… Baa-Ram-Ewe!

  • JohnnyEnzyme@lemm.eeOPEnglish
    2·
    16 days ago

    Thanks, mate!
    So, both the acct and destination community were hosted by Lemm.ee. It’s one of the big-five or big-four instances (whatever) across the Lemmysphere, FWIW.

    I suppose I could test this from FF (I’m on Chrome) if you think that might work, altho it did work fine in Chrome just a week ago. *shrug*

    • Elevator7009@lemmy.worldEnglish
      3·
      16 days ago

      Every single time I have used the Lemmy Scheduler I did it from Safari or Firefox. I do not have a lemm.ee so I cannot test posting from there unfortunately. I’ll try to post TO lemm.ee and edit this comment with my result

      • JohnnyEnzyme@lemm.eeOPEnglish
        3·
        14 days ago

        Gooottt iiiitttt!

        Okay, when logging in again just now, I realised that last time I seemingly made the mistake of filling in the instance field with my community name, instead (i.e. [email protected]). So then-- seems to be working properly okay, now. :D

        @[email protected]

        If I may-- I would suggest that the service check to see if at the very least, the field entry for “Instance” looked like a proper URL. Even better I’d think would be to actually ping the entry, or something like that.

        Because you know… careless idiots like me. ^^

        Not just that, but I’d think it really useful to check that stuff right up front when a user logs in, including checking their ID & PW to see if it successfully logs in. Otherwise I suppose users are bound to see these “500” errors if they screw part of that up, I guess.

        EDIT: Nah, even when I seem to schedule things, the tool just doesn’t seem to work anymore in terms of known time-differences.