@JoeFranz have you checked the logs and see whats throwing errors? That is where I would start.

@leftyleo not to hijack this thread. But since you were thinking of going from 64 to 32 bit os…
I am getting the same error on a fresh sd card on a rpi 3B with buster 32bit installed. It has manually installed MagicMirror, node, etc., no extra modules, just the config sample copied to be config.js.
…
[05.09.2022 20:19.03.191] [LOG] Starting node helper for: newsfeed
[05.09.2022 20:19.03.192] [LOG] Sockets connected & modules started …
[05.09.2022 20:19.05.030] [LOG] Launching application.
[2092:0905/201909.167187:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[2132:0905/201909.521340:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[2106:0905/201909.609131:ERROR:command_buffer_proxy_impl.cc(126)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
…

@hogedir With a raspberry 4 you can have two displays. I’m thinking they can be set up as an extended desktop . Then it’s no big deal with the default magic mirror.
Top_left and top_right would end up being left and right…
I haven’t tried this with MM. But I have used my pi with two screens. But in my mind it ought to work with MM.
Just don’t use the middle_center or any position that would span across both monitors.

@sdetweil said in Electron v20 will coming with next release but...:

@kayakbabe where do you see 12?

all is ok to 19

https://github.com/fivdi/epoll/issues/42
Top comment by David

I saw on those github issues posed above that

“This will result in applications that use epoll/onoff being broken after Electron 12.”

That means most of the button and input sensor type magicmirror modules will probably break.

So, I"m kinda glad I broke my new button module. and found this info right after. I think I"m going to go with a python based script and bypass the node on/off and epoll. So back to the drawing board.

@sdetweil said in help on new spam control idea:

Also how about no including links for new users until they make x number of allowed posts.

this hurts real new users struggling to get their stuff running,
worked for a couple days/weeks to get it to work and finally find this and post…
and if we put them on the mod queue then they might miss a whole day til their post arrives and someone can help them…

Good Point.

@sdetweil said in help on new spam control idea:

why whack the good new users?

Well, I was thinking that

I don’t find it horribly annoying especially if it’s the kind that just makes you pick the object from a grid of photos. It doesn’t take too long and it does keep the spam bots from posting. I don’t particularly like it… but I don’t find it horrible either – especially if it stops happening after I’m a member in good standing. You could base it on reputation points. After reputation is gained… then no more reCaptcha. Or if we don’t have the issue with bots… then forget I mentioned it.

What about reCaptcha required to submit a post for new users for the first x number of posts?

@kayakbabe It think posts that have certain spammy words or phrases could be added to moderation too like

now hiring
buy now
be your own boss
additional income
limited time
earn money
get rich
I enjoyed your post
You write very well
I offer you
I was reading this article and find it very informative

There are obvious ones that recur here but I can’t think of them right now.

Also how about no including links for new users until they make x number of allowed posts. I run some sites and we get visited by human spammers who will make two or three comments to try to get the posts with links to show. Usually it’s garbage, ipso lorem, or something that just doesn’t make sense. So I just moderate all posts that include links from users with less than 10 number of good posts. Or, I can go ahead a mark a user as moderation exempt if I determine them to be legit.

how about allow nodejs.org and www.npmjs.com too.