[FluidNC Issue#1448] Problem: problem with wiki “forgot password?” page

#1 – bdring 于 2025-02-08

You account has been approved.

Here is the normal process to follow.

http://wiki.fluidnc.com/en/wiki_contributions

#2 – RichMorin 于 2025-02-13

I just went to http://wiki.fluidnc.com/en/wiki_contributions and followed the “Discord” link (to http://wiki.fluidnc.com/en/support/discord). There, I clicked on the “link to an invitation” and reached https://discord.com/invite/MDsRDeNsTE, where I saw “Bart Dring (bartdring) invited you to join FluidNC” and an “Accept Invite” button. Clicking that caused the banner to read “Unable to accept invite”. Clicking “Accept Invite” again had no perceptible effect. In short, it’s still broken (for me).

-r

https://discord.com/invite/MDsRDeNsTE
> On Feb 13, 2025, at 07:44, bdring @.*> wrote:
>
>
> Closed #1448 as completed.
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID: @.*>

#3 – bdring 于 2025-02-13

I’ll email you the name and password.

#4 – RichMorin 于 2025-02-13

Thanks; sorry for the hassle (and thanks for your efforts on this and more generally, FluidNC). FYI, I’m an aspiring Maslow 4.1 user (still waiting for my machine). I’ve been chatting with the folks on the Maslow forum about my notions of adding a RasPi 5 and some associated devices (e.g., cameras, laser) to the sled. After I review some FluidNC info, I’ll probably pester folks for follow-up information (no good deed goes unpunished…).

-r

> On Feb 13, 2025, at 10:59, bdring @.*> wrote:
>
> I’ll email you the name and password.
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID: @.*>
> bdring left a comment (bdring/FluidNC#1448)
> I’ll email you the name and password.
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID: @.*>

#5 – MitchBradley 于 2025-02-13

In my experience, anytime a Pi is involved, add Linux system administration to whatever list of tasks and problems you already have. And I say this as someone who has been using Unix and its descendants since 1978.

#6 – RichMorin 于 2025-02-13

In 1978 I was still using Drum Scope on a CDC 3800 and 6400, RT-11 on my home LSI-11’s, and VMS on a VAX 780. I touched my first Unix terminal in 1982 (and mostly use macOS these daze). That said, I agree that adding a Pi (and Linux) into the mix will definitely add tasks and problems.

However, some of the stuff I’d like to do will require a machine and OS that can support fairly arbitrary sets of code (e.g., in Elixir and/or Python). So, “needs must when the devil drives”. In other news, I really hope that the Maslow and FluidNC code bases can be brought into alignment, as that would (IMHO) benefit them both.

#7 – MitchBradley 于 2025-02-13

For your own use, Pi/Raspbian/whatever is great, but supporting it for a customer base is a totally different ballgame. For awhile I maintained the Pi version of CNCjs, and eventually gave up. Version churn in packages and OS releases, coupled with most people’s unfamiliarity with shells, init scripts and stuff like crontab, just got to be too tedious to withstand.

#8 – RichMorin 于 2025-02-13

Thanks for the feedback; it sounds all too plausible. Although I don’t know whether I’ll go there, the Nerves folks have had great success in supporting large sets of fail-soft embedded processors via remote administration. Then again, that’s a rather unusual “customer base”…