(untitled)

Hello, I am thinking about making my own imageboard site. I know basic code and stuff like that but the only problem is… I don’t really know where to start.. I don’t know I haven’t made like you know an actual real website b4. Sorry if this doesn’t make sense,, But tips could be useful But my final question is, is an imageboard too hard for a newbie like me to make???

Try making a simple website with html+css first. (e.g. a thread with dummy posts) Add a form somewhere, and write a CGI script to handle it (e.g. write a post, and have the server return a formatted page) Add a database to store the posts. You might need to follow some sql class if you aren't familiar with it, or you could use a directory structure. (sql is a better idea) Add more fluff: file upload, thumbnails, moderation interface, spam protection, etc. Making an imageboard isn't too hard, but you will need to learn some things along the way. I even see it as a good project to learn web development.

i actually just made an imageboard this afternoon cus bored (https://jahanrashidi.com/board/ to self-promo) and made it all in html+css+php it's kinda soykaf but the way i made it is there's a database with three tables, one for posts, one for replies, and one for boards. each board uses the same php file with only the path of the board changing for each, and then the other info about the board (name, desc, etc) is fetched from the board table. then the posts matching the current board are fetched from the posts table, for each post replies are fetched from the replies table, etc. i didn't add file uploads (just hotlinking) cus i'm low on storage, but if you wanted to do so (like on respectable boards) you could either upload the file to the database too (not recommended) or upload it to a directory on your server and save a link to that in your database. for the frontend and html structure just look at other imageboards and see how they structure things, ctrl+u f12 etc

>>78741 also forgot to say, you need to be careful with all info being uploaded to the server, sanitize text before storing to avoid people making a mess, and use prepared statements (https://www.w3schools.com/php/php_mysql_prepared_statements.asp) to avoid sql screwing

>>78740 Ah, thank you. :) I will try this when I have time to get on my computer.

>>78740 >CGI script It's my impression that CGI scripts are pretty much obsolete and it's better to use a language's standard library server. That's how I approached my imageboard.

>>78818 both work don't worry just do it somehow and itll be fine

>>78738 You write like a retard and your post shows you don't actually have the slightest idea as to what you are trying to get yourself into. In all likelihood you just found imageboards for the first time, thought they are k00l, and then had a wet dream about making your own. It's not much different from naive a gamer suddenly getting the fancy of making his own game because he likes games and is too clueless to know what that entails. But to answer your question, and I'm assuming that by "imageboard" you really meant "functional imageboard that could realistically be deployed": yes, an imageboard is very difficult for a complete newglitterboy like you to make. In truth, it is one of the easiest projects when you know what you are doing, but you clearly do not. I doubt you understand how sockets work, I'd be surprised if you know what TCP/IP is, and I bet you also don't know how to work with a database and lack the creativity to use an alternative method of storing post data. And to top it all off, you look like you couldn't write a decent HTML doc to save your life. If you indeed have any real interest in doing this beyond a sudden fascination with hacker aesthetic, I could help you get started, but I sincerely doubt it. Show me some work first, do what >>78740 said and make a basic page showing what a thread would look like.

>>78844 >I doubt you understand how sockets work, I'd be surprised if you know what TCP/IP is He wants to write an imageboard, not a web server.

>>78738 It's okay for a first project. Don't overthink it. If you want to do it, do it. >I don’t really know where to start. 1. Pick language. Any mainstream one is fine. 2. duckduckgo "[language] server-side web programming" 3. Use the tutorial you find to set up a page that says "hello world" plus a random value. This will teach you to output server-side variables to the client. 4. Use the tutorial you find to set up a page with a form that sends a single input to the server via a POST request to which the server responds by sending a page that just says whatever was in the input 5. Search "[language] html sanitization idiomatic" and use that to learn to sanitize the user input before outputting it. Make sure sending "<b>pwned</b>" results in that full string being output, NOT a bolded "pwned" or "&lt;b&gt;pwned&lt;/b&gt;" 6. Change the form to send multiple inputs like "name" and "comment" and whatever else you want on your board. Modify the server to output all those inputs. 7. Pick a database technology. It doesn't matter which. Google "[language] [datebase] tutorial" and write code to insert something into the database and then retrieve it. 8. Modify your form page so that your server will now add the name/comment/etc to the database, and then returns a webpage with all of the inputs in the database. 9. Search "[language] [database] injection sanitization idiomatic" and follow what you find to prevent query injection attacks. 10. Congrats! You've now essentially made a single thread. That should be enough to get you started. From there, you'll need to add something to your server/database to distinguish between threads and replies and associate replies with their parent thread, and only display replies associated with a thread. Then you'll have a single board, and can add functionality for having multiple boards. For the design of the webpage, just read an html5 and css3 tutorial. There's not a lot to it. If you're going to host it anywhere, you'll want to add some moderation tools, but by the time you've written the rest of the board software, you should be able to figure out how to do that.

>>79026 Same. I've had a set of files on Box since like 2008, when it was still box.net. I didn't log in for many years at one point and there was zero bullsh​it about it.

Either I'm jumping between parallel universes or there's always some thread about OP wanting to make their own imageboard but has little to no skill on how to get started. Similar thread (with a similar answer): >>>/λ/res/38990.html#39054 >"I know basic code and stuff like that" No offense, but your choice of wording makes you sound like you're either lying or you're trying to talk yourself up to us about a skill you clearly do not have. Even if you were telling us the truth OP, then you would've already been able to start on your own and conduct research on how an imageboard works, even if you only know "basic code and stuff like that". >"I don’t really know where to start.. I don’t know I haven’t made like you know an actual real website b4." [Side tangent: I could tell you're new to imageboards/*chans in general by just this sentence alone. Why do you type this way on the internet to strangers when you have more than enough time to stop and think about what you want to say, before even typing it. I could honestly care less if this was in-person or over a voice call (I live in an area where everyone talks this way), but the fact that you took the time and effort to type those fluff words in order to sound "le quirky" on an imageboard, is just painful. No one wants to read that, ESPECIALLY if you're asking for help...] Anyways, look up tutorials on Website Development, make a few toy websites and when you feel ready to learn how to make a Web App like an imageboard, look up a tutorial on an easy to use Server-Side Lang like Python, PHP, or Node.js. Then look up a tutorial on a simple database you could use like SQLite (requires learning SQL) or MongoDB (no-SQL required database). >"But my final question is, is an imageboard too hard for a newbie like me to make???" If you don't even have the foundation down, then clearly, yes. How are you going to get started, when you don't even know how or where to start? Learn the foundation, and it will all come to you. Making Web Apps is tedious, but not hard if you have the foundation. Since the topic of this thread keeps getting posted over and over and over again, if you or anyone else need help I left my email. Other tips: [*] Stay away from Web Dev General threads on /g/. [*] Most tutorials are found on youtube or freecodecamp, but if you really want to make it stick, then you should continue building projects after following those tutorials. [*] Do not, and I repeat, DO NOT USE Single Page Application frameworks like React or Next.js for something as small as an imageboard. The trade-off for productivity/plug-n-play is not worth for the bloat it comes with for some applications.

Try starting with making a basic html/css website. I found this site to helpful with things like this: https://landchad.net/

>>78738 Please take inspiration from Picochan https://github.com/neeshy/picochan Do not copy vichan because the codebase is a mess.

>>78738 >Hello, I am thinking about making my own imageboard site. How come you want to? What doesn't satisfy with the current imageboard options available? What would your imageboard offer that none of the others do?

>>79164 Not op but remaking existing software is fun and teaches you about concepts you'd otherwise take for granted while giving you a definitive, familiar goal. Not everything has to be about innovation, especially for beginners like op.

>>79165 I agree, but i think the real problem is going around saying "i wanna do X" and then just dancing in the limbo of indecisiveness regarding what tech to use and never starting