I'm close to finishing my imageboard implementation. It has all the features of 4chan except for /f/ and /rs/ and so I have a few questions:
1. How is /rs/ implemented? Does the site scan the links posted in each board? Unlike /f/, /rs/ doesn't have an upload form.
2. How do the implement capcodes (what is their input syntax) and how are site moderation and administration performed? Where do they login? Do they have username and passwords? What's the admin/mod panels look like? Can moderations be done in-site and not only through a dedicated admin panel?
The board has everything except images stored in memory so it should be fast. If there's enough interest I might be able to open source it once it's done.
inb4 back to Le ima/g/eboards.
Name:
Anonymous2012-12-04 14:59
post it now.
Name:
Anonymous2012-12-04 15:19
>>2
I will once it's finished. Any ideas on my questions?
How do the implement capcodes (what is their input syntax)
I can't be bothered to check, but I think they're entered into the email field and just checked in the same step as ``sage'' and so on. if $email == "#pubies" { make_stuff_red(); }. how are site moderation and administration performed
Use flat files and delete them when you want to delete a post. Your image board will never be popular enough to need anything more advanced.
Name:
Anonymous2012-12-04 15:27
1. There is no /rs/ anymore.
2. What do you mean capcodes? Site moderation either uses a different set of pages or an actual software to make changes on the db.
Of course they will have some form of authentication, or else as soon as someone discovered what they were using shit would hit the fan.
A panel looks whatever you want it to look like.
Moderation can be done any way as well.
No one wants to upload images to other site just to post here.
There is no interest in the license or code availability of your pet project.
You can post it here though
Name:
Anonymous2012-12-04 15:37
>>4
I was asking as a comparison. I have already implemented them.
>>6
1. What do you mean there's no more /rs/? It's still there!
2. Look on 4chan's FAQ on capcodes
No one wants to upload images to other site just to post here.
I don't understand what you're saying.
All I'm offering is to open source the imageboard once it's done.
1. Probably. Just like autolinking, just a bit more stuff happens.
2. I don't know and however they are elsewhere. They have a login page. Yes, otherwise there would be no use for the login page. It is a panel full of the controls you would expect on an admin/mod panel. Yes.
Your problem seems to be "I want to reimplement this admin balls to the letter". Just do what makes sense.
Don't do in-band site management. Writing an admin panel is a lot of effort (much more than the rest of the code altogether), won't ever be as powerful as you need it to be, and just creates a completely unnecessary attack vector. Just write some scripts you can run serverside and do your adminstration over SSH.
>>18
Why do people post worthless shit so much here? I swear it's more frustrating than /b/ sometimes.
Name:
Anonymous2012-12-04 22:11
Perhaps we can harness this power...
Infinite Degradation Algorithm
FrozenVoid can write the paper.
Name:
Anonymous2012-12-04 22:13
yet another useless imageboard engine, now in python.. there is a plenty of them written in php, perl etc etc
Name:
Anonymous2012-12-04 22:19
>>12 Will it ever get used?
Most likely yes, I'm thinking of setting up an imageboard specific to my country..
>>13
Isn't the best admin/mod workflow is to have the same interface as regular users but sparkle bits of admin controls here and there? Currently I have a separate admin panel that's going to be in a separate subdomain altogether, but I'm planning on adding in-site admin/mod controls.
Just write some scripts you can run serverside and do your adminstration over SSH.
Although this would probably be the most secure option, administration and moderation would be tedious as I would have to, e.g, go back and forth just to check if a reported image is really against the rules etc.
Name:
Anonymous2012-12-04 22:34
>>22
Wait... your country doesn't have a few 4chan copycats? Where do you live?
Also, the SSH administration is better for at least a small number of moderators, gets shit done much quicker, that problem with images is easily avoidable. My guess is you're not that comfortable with other languages so you might as well stick to what you know for now.
Name:
Anonymous2012-12-04 22:44
>>23 My guess is you're not that comfortable with other languages so you might as well stick to what you know for now.
What do you mean by this statement? I know C, PHP, Python, Lisp and OCaml but how is my comfort with other languages has any relevance to whether or not to do SSH administration? Should I implement it in a language other than Python?
Name:
Anonymous2012-12-04 22:46
well, i remember a bit how moderation works in wakaba, it has an admin panel (poorly made) and when you login on a special admin page you have the access to the panel and additional buttons over every post which let you delete/ban etc
afaik yotsuba source code isn't available but you can install another board engine and check how it works. also most popular engines are kind of old, there are some new ones with plenty of fetures but personally i like wakaba and kusaba more. and then, those new engines usually are either poorly documented (and not in english) or aren't open source because they are mostly written for one site only. other people use heavy modified wakaba/kusaba
Name:
Anonymous2012-12-04 23:38
Ideal imageboard
- completely written in C with FastCGI
- under 1 MB
- full BBCode support
- ability to upload any file ``type''
- totally Javascript-free
- no ``HTML5'', Flash®, Silverlight®, Java Applet ``Beans''®, Ajax, etc.
- encryption by default
- zero CSS-styling (let the users set their own)
- UTF-8
- licensed under the Affero GPL
- no non-free dependencies
- administered with flat config files; a gooey may be written with FIOC
- no databases; just directly modify the HTML files
- no ability to ban users (moderation ∝ spam⁻¹∙freedom of speech)
- non-Google free (as in freedom) captcha enabled by default
- permanent archival of text; use something like Sphinx for indexing
- absolutely no IP logs can be kept, not even an option
- fast-loading \{Latex} support by server-side conversion to svg; then <embed> the svg cleanly
>>30
Surprisingly, this is something they like to scrimp on.
``FastCGI? No, that's an advanced feature for Platinum accounts and above! Same with other artificial limit remov^W^W^W features like SSH and more than one MySQL database!''
Regardless, a BBS protocol might be better. And no BBcode, \{Latex}, <html>. Only Asciidoc or Creole. And FreeBSD, MIT, CC0 licenses. Shit stuff as copyright is an abobination. Endorsement is better. I like the creator endorsement idea: http://questioncopyright.org/creator_endorsed
inline static const interbang new int(static_cast<int>(8253));
Name:
sleepy2012-12-05 4:12
>>37
Well, I mostly meant menu instead of CL based, although both can be used. But for the protocol part, it would be to encrypted the connection, than using telnet, and extend upload/download of file types with atomic or partial continuation (checksums everywhere!).
The more I think it about it, it is an interactive gopher. Of course, SSH would always be used to extend it further.
While typing, I was enlightened. vi like menu. :wq