this post was submitted on 03 Feb 2025
21 points (95.7% liked)
[Closed] Moved to !fedigrow@lemmy.zip
1584 readers
1 users here now
This community has moved to !fedigrow@lemmy.zip
Original sidebar info
To discuss how to grow and manage communities / magazines on Lemmy, Mbin, Piefed and Sublinks
Resources:
- https://lemmy-federate.com/ to federate your community to a lot of instances
- !fedibridge@lemmy.dbzer0.com to organize overall fediverse growth
- !reddit@lemmy.world to keep tabs on where new users might come from :)
- !newcommunities@lemmy.world
- !communitypromo@lemmy.ca
Megathreads:
- How (and when) to consolidate communities? (A guide)
- Where to request inactive or unmoderated communities? (A list)
Rules:
- Be respectful
- No bigotry
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No 500 errors on my end. What instance was the account you were you trying to schedule from on, and what instance was the community you were trying to schedule a post to on?
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*
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
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. !eurographicnovels@lemm.ee). So then-- seems to be working properly okay, now. :D
@rikudou@lemmings.world
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.