[Captcha] Switch forums to Solve Media? [Plugin]

[Forboding Angel]

https://portal.solvemedia.com/portal/help/pub/phpBB/

If you aren't familiar with solve media, basically it is a very easy to use captcha that is catching on pretty well and from all accounts seems to work flawlessly.

The current forum one is extremely buggy and has a habit of locking people out of their respective accounts. Perhaps solve media could be used in place of it.

An example of solve media in action:
--removed--

[AF]

The forum is here:

https://github.com/spring/spring-websit ... root/phpbb

Considering your anti-git stance, fork it on github, and then do an svn checkout, e.g.:

Code: Select all

svn co https://github.com/spring/spring-website.git

Simply requesting it be added is somewhat odd, since you have all the tools yourself, and there is nobody in charge or maintaining the site as such other than those who feel something needs ammending. It's likely this thread will simply rot as a result regardless of wether people like or dislike the suggestion

When you've tested, commit your changes, and click the pull request button in your browser, someone with commit access can review and merge in your changes, or suggest modifications.

[FLOZi]

I've made a few requests / suggestions about changing captchas and got nowhere.

[Forboding Angel]

The forum is here:

Apparently Flozi is "Too lazy" as well. Go away.

Edit: Also... Fuck Git.

[AF]

You did see the part where I told you to use an svn checkout? then do an svn commit? No git knowledge required? It's like a man coming up to you and saying "Hello Ben" and rsponding "Fuck chinese".

Anyways since you failed to grasp the fundamental premise:

If you don't do it yourself, nobody will, because nobody else will be arsed

[AF]

[Forboding Angel]

Since this discussion got all "serial"...

Seems a bit nuts to fork an entire repo just to submit some edits. Moreover, maintaining updates from your fork vs the main sauce would become a pain in the tits.

What would make more sense is just the ability to make line comments on someone else's sauce, or a bug submission (although half the time I can't fine the issues tab in git because the site is lain out in a very confusing and semi-inconsistent manner depending on what you are looking at).


Also, my patches tend to get ignored. Then even more humorously, sometimes they get implemented, but instead of using my edits, they do them themselves and we wind up with the facepalmworthy fail that is the google search in the wiki, as opposed to my original, which was MUCH nicer.

Last of all, patches to phpbb require admin panel and database access. I have access to neither.


Edit: BTW, nice infographic... You should keep that around as it really is quite helpful (on that note, thanks). I still dislike git with the passion of a thousand suns, but having explicit instructions like that makes me more inclined to at least test it.

[AF]

It's not that much work, git actively encourages you to fork, which is why it's a 1 click affair in the browser.

The other beautiful part is that pull requests are so trivially easy to respond to:



ps: Abmas typo fix was gracefully merged

[AF]

Also note the link to patch/diff files, it may be possible to supply a commit purely via a diff/patch from a local setup such as tortoiseSVN