/site/ - Site Meta

Official 8chan Site Meta. (Bring bug reports, complaints, and requests here)

Index Catalog Archive Bottom Refresh
+
-
Name
Options
Subject
Message

Max message length: 12000

files

Max file size: 32.00 MB

Total max file size: 50.00 MB

Max files: 5

Supported file types: GIF, JPG, PNG, WebM, OGG, and more

CAPTCHA
E-mail
Password

(used to delete files and posts)

Misc

Remember to follow the Rules

The backup domains are located at 8chan.se and 8chan.cc. TOR access can be found here, or you can access the TOR portal from the clearnet at Redchannit 3.0 (Temporarily Dead).

Ghost Screen
Celebrating its fifth anniversary all September


8chan.moe is a hobby project with no affiliation whatsoever to the administration of any other "8chan" site, past or present.

Infinity Rebirth Anonymous 04/21/2025 (Mon) 01:14:16 Id: 650d2e No. 11515
I believe it was about at this point ten years ago that one little man had one very big dream to create the perfect imageboard experience. To do this, he enlisted the most competent man known to him and surely to all of us, Joshua Moon, but unfortunately even Joshua's limitless intelligence and unwavering willpower was not enough to reach the promised land, and the result was a disasterous fifteen thousand dollars lost between both the little man and his benefactors supportive userbase. This crushed the little man's dreams, just as his little, brittle bones are crushed daily by the weight of his own blubberous body, but he has long since rolled on to greaters pastures and now enjoys a simpler, nobler life of routinely masturbating to anthropomorphized raccoons in diapers and constant substance abuse. But that dream for a perfect imageboard, long trodden on, smashed, and slammed, remains. As you will all agree, this website has a number of quality of life features that simply will never be implemented on 4chan under its existing administration. By that same token, the long-term posters here has grown accustomed to the bugs and quirks of the website, and the small userbase hasn't justified the development of additional features such as userscripts, extended functionality, and robust moderation tools. I am looking for some programmers, those familiar with JavaScript and Nose.js, to implement some of the features that have been discussed here in the past couple of days. The objective is to modify LynxChan and Aleph to improve the features and security while compromising as little of the usability as possible. Some of these features discussed include: >anti-spam measures such as proof-of-work CAPTCHAs and heuristics analysis >anti-samefag measures to preserve the anonymity of good-faith users >a sound player to support existing 4chan files >hotkeys to open and close reply boxes >new CAPTCHAs that less obnoxious and no longer occasionally wrong >recoloring the greentext to be a little less green Most of these goals, aside from that last one, are attainable, and I heavily encourage those with the capacity to participate. This thread is to be used for discussing the implementation of the above and other desires in technical terms as well as set up correspondence. This project has no official sanction as I am just announcing it, so it will be maintained in separate repositories that would hypothetically be merged in the future. I stand ready, with my finger on the trigger, on an Easter Sunday to christen these two projects, but I hesitate, unable to think of a suitable name that so perfectly encapsulates the wonders we shall create. The first set of dubs shall name the front end project , while the second set of dubs shall name the back end.
>>11515 >anti-samefag measures to preserve the anonymity of good-faith users what do you have in mind beside IDs?
>>11533 It would still use IDs, but they are disabled on all posts by default and only activate on a per poster basis if a poster replies to their own posts multiple times or replies to any single post more than twice.
>>11535 actually that's a pretty good idea, non intrusive and all so like is someone is more than 50% of posts past the 10th post and more the 30% past 20th the post it get it's ID revealed or something like it maybe add a time related filter to prevent people heavily contributing to slower board from being flagged as well that way you have granularity to adapt fairly to specific situation like people doing an info dump at the start of the thread not being flagged by starting it past 10th post
I'm studying for exams at the moment, but when that is done I'll get started. In the meantime, my thinking on the design of the anti-samefag mechanism as described in >>11535 is starting to take form, but almost none of my programming experience has been concerned with web development. While all my database experience is with MySQL, I'm going to assume thatthe fundamentals are similar to Mongo. Message data would be parsed on the client rather than the server during a post to search for all strings containing two '>' characters followed by a string numbers. This data would be stored in a table that keeps track of the userID, user post number, and one of the quoted post numbers so long as it already exists as a user post number. Before becoming a record, each quoted post number is checked against the user post numbers that share the same userID, and if this returns true too many times, then the user ID is enabled. Such a system would only be implemented on threads with low velocity, if thread velocity is a metric measured here. In events of spam, where the UID/Post ratio is very high, all (1)s without any replies (as these are the most likely to be spamposts) would be given a special ID for filtering. Some genuine posts would be caught up in it, but for the moment it would work. This is something that might be fine-tuned by factoring in the ASN, but it wouldn't do much good with very large botnets. I'd like to discuss other possible metrics that could be examined to evaluate samefags and spamfags that wouldn't be too computationally taxing. >>11539 You could probably have a bracket system where depending on the size of the thread, different prevention and mitigation systems are enabled/disabled. Sounds like a lot of work, but it's easy enough to conceptualize.
Oh yeah, and someone PLEASE help me with Mongo.
>>11811 >Sounds like a lot of work a function that count the number of posts per ID and compare to the global number of posts don't sound to hard honestly, even with exceptions and brackets, guess it would eb interesting to actually try
>>11811 >>11812 This is a bit late but the biggest difference between SQL and MongoDB is that SQL is a relational database while MongoDB is a document store. If a SQL database is a collection of big arrays of records, then MongoDB is a collection of big arrays of JSON objects. To get any efficiency in MongoDB, the important thing to know is that you still need to set up all of the same database keys. Even if you're not using a database schema to set everything up as in SQL, you'll still need everything indexed. Otherwise it's similar enough, just work through the API documentation and you should be able to make sense of it all. The MongoDB website's tutorials include analogies to SQL. MongoDB has a "development checklist" that might be useful: https://www.mongodb.com/docs/manual/administration/production-checklist-development/
>>13855 Thanks, I still plan on getting around to this after I finish with multiboards.


Forms
Delete
Report
Quick Reply