Does anybody manage lua-users wiki?

[Berwyn Hoyt]

Hello, does anybody still manage the lua-users wiki? There's a problem and it has no webmaster link.

The primary problem is that the Wiki locked -- which is listed as Bug #1 on the Wiki Bugs page, but the fix link there doesn't fix it:

• Software error:
  Could not get editing lock at (eval 35) line 764.
  For help, please send mail to this site's webmaster, giving this error message and the time and date of the error.
  

My reason for trying to edit the content is that I'm trying to update the SplitJoin page because it has bugs in the "Split by pattern" section which doesn't work on either Lua 5.1 or 5.4.

My patch (-+) is as follows (only the two code lines are changed):

== Method: Split by pattern using {{string.gsub}}/{{string.match}}  ==

Break a string up at occurrences of a single character.  If the number of
fields is known:

        {{{!Lua

- str:match( ("([^"..sep.."]*)"..sep):rep(nsep) )

+ str:match( ("([^"..sep.."]+)"):rep(3) )
}}}

If the number of fields is not known

        {{{!Lua

- fields = {str:match((str:gsub("[^"..sep.."]*"..sep, "([^"..sep.."]*)"..sep)))}

+ fields = {str:match((str:gsub("[^"..sep.."]+", "([^"..sep.."]+)")))}
}}}

[Sainan]

> Hello, does anybody still manage the lua-users wiki?

Yeah, I believe jo...@neggie.net does.

> Software error: Could not get editing lock

Maybe someone else is trying to edit it as well? :P

-- Sainan

[Berwyn Hoyt]

@Sainan: I sent jo...@neggie.net a message about it in June but my mailer has no record of him replying and it was never fixed.

It's been like that for months, so no, it's not somebody else trying to edit at the same time.

For the record, the patches I sent above were buggy. They should have been as follows:

== Method: Split by pattern using {{string.gsub}}/{{string.match}}  ==

Break a string up at occurrences of a single character.  If the number of
fields is known:

        {{{!Lua

- str:match( ("([^"..sep.."]*)"..sep):rep(nsep) )

+ str:match( ("([^"..sep.."]+)"..sep):rep(nfields)..'?' )

}}}

If the number of fields is not known

        {{{!Lua

- fields = {str:match((str:gsub("[^"..sep.."]*"..sep, "([^"..sep.."]*)"..sep)))}

+ fields = {str:match((str:gsub("[^"..sep.."]+", "([^"..sep.."]+)")))}
}}}

--
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lua-l+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lua-l/_r7LZbox9BVPNrW26cMXrt__MFe3MrEvSu78NyTP9c1Caw-xko0Smjtp9hit7gLko6awI9OVEa71vDlK5C1cMz87gh2GPUQJO5XUdGNt3Ns%3D%40calamity.inc.

[John Belmonte]

Hi Berwyn-- I bcc'd you on a July message "Cannot upload files to lua-users.org", but that was probably easy to miss.

Write access on lua-users.org isn't working, since the site hasn't been adjusted for the SELinux environment of the new host.  I've just changed the wiki pages to show "site locked" to make that a little more clear.

While it will take some dedicated focus to work through the SE stuff, the bigger issue for me is that when write access is restored I'd be back on spam duty, which I've carried since the site's inception (2001).  Malicious edits are usually done in bulk (either many pages or the same page repeatedly over time), where the appropriate thing to do is restore to a snapshot, and replay any good edits that may have occurred in the meantime.  This recovery is an entirely manual process, as is frequently checking the site for bad edits.  The community file area has been subject to malicious changes as well.

So I think a condition for restoring write access is finding at least two people willing to learn this process and keep vigilant going forward.

To view this discussion on the web visit https://groups.google.com/d/msgid/lua-l/CAKToXm-kyivjdQxmpV6Lwt6CXMOT7%3DMdY630j%3D73dXdNacZSvQ%40mail.gmail.com.

[Berwyn Hoyt]

Thanks for the reply, John.

I hear your call for maintainers ...

Would the spam duty problem be largely resolved if edits were hidden behind a captcha?

Many thanks,

Berwyn

To view this discussion on the web visit https://groups.google.com/d/msgid/lua-l/CANtbB94Q6fs7mG13adgEdmEAiD3RYD0bteuaCbz_Muu%3D9TuYdg%40mail.gmail.com.

[Bessa]

Ok, thank you!

[Родион Горковенко]

Hi Friends!

I've read about the sad situation about lua-wiki and spam issues - there is not quite straightforward solution - not sure it is worth trying "as is", but perhaps some of us may hit upon some similar idea.

Some time ago here was created community-driven wiki-like site about algorithms: https://cp-algorithms.com - it uses github as "backend" so any new material is created via "push-requests".

There was some tiny engine fetching markdown files from the repository, processing and deploying to the site - actually it was I who created the first version of this thing.

In that way issue with spam is more easily resolved: spam additions don't get into content without approval (and there could be several housekeepers with approving rights).

As for engine - there are of course numerous ways to do this, depending on where and how this should be deployed (one of the options would be "github pages"). The mentioned CP-algorithms for several initial years used completely free resources at all.

Obvious issue is that most probably existing content will require certain efforts to migrate. I don't know which source format lua-wiki uses - quite probably not the pure markdown.

Anyway if this sounds like a feasible solution, I would be glad to take part as much as my poor skills allow in helping the matter.

sincerely yours,

Rodion  

To view this discussion on the web visit https://groups.google.com/d/msgid/lua-l/CANtbB94Q6fs7mG13adgEdmEAiD3RYD0bteuaCbz_Muu%3D9TuYdg%40mail.gmail.com.

[Berwyn Hoyt]

A very good idea, Rodion. Thanks for being willing to work on it.

John Belmonte, can you release visibility to Rodion so that he can assess the viability of translation to markdown?

To view this discussion on the web visit https://groups.google.com/d/msgid/lua-l/CAL2n1tyJ0zGnevFFnq06dD-y%3DE%2BamxQ0UCoU5TjtzqccTPn6Aw%40mail.gmail.com.

[John Belmonte]

Ok, I've removed that global edit lock, so it's possible to view page sources again.

To view this discussion on the web visit https://groups.google.com/d/msgid/lua-l/CAKToXm8LwuE5-rOpRCwC9UjLMyTVSaX22H0VLvE9k355AE9sCQ%40mail.gmail.com.

[Berwyn Hoyt]

@John Belmonte, I'm afraid it still does not appear to be unlocked. Even if I go the the unlock page first, updating content still give the error:

Software error:

Could not get editing lock at (eval 35) line 764.

For help, please send mail to this site's webmaster, giving this error message and the time and date of the error.

To view this discussion visit https://groups.google.com/d/msgid/lua-l/CANtbB97%2BAwS7L%2BBrCSWDP9i0vOXx26xFM2vf%3DXObHwZk5%3D9Yhw%40mail.gmail.com.