Lainchan Homepage Project

Hello /λ/ainons I've been talking to Kalyx about the homepage and about the /all/ problem where lainons just go to all and only post on those threads. This thread >>4618 gave me an idea. If we could have a homepage with posts mixing /all/ and /random/ we can have people see what is being talked about and also what other interesting threads their are An old thread is NOT a dead thread . and then /news/ will be dedicated to all news that has ever happened and for urgent matters we have site wide announcements. I am willing to pay $25 in BTC to a lainon who works on a board where it goes 1 /all/ thread, 1 /random/ (/random/ not /r/) thread so on and so forth. I'll pay $15 for it to be useable and then the next $10 for bug fixes, etc. Having the homepage be this /all/ + /random/ page will also present exactly what the site is about to anyone who stumbles upon lainchan.

Not too hard, see the rand and ukko themes: https://github.com/lainchan/lainchan/blob/master/templates/themes/rand/theme.php https://github.com/lainchan/lainchan/blob/master/templates/themes/ukko/theme.php The way to do it would be to have two queries and just display posts alternately from them (ensuring no duplicates).

>>6300 >two queries >inb4 >saging a sticky

>>6301 What's wrong with two queries? Two sets of data are wanted: a list of threads sorted by last post, and a list of threads sorted randomly. Getting one from the other would require manually shuffling (or sorting) a single list on every page generation, which would be slow. Databases, on the other hand, are good at producing results quickly.

>>6305 No, one set of data is wanted: a list of all threads. >manually shuffling (or sorting) a single list on every page generation, which would be slow Not really. >Databases, on the other hand, are good at producing results quickly. This is correct. But >The way to do it would be to have two queries and just display posts alternately from them (ensuring no duplicates). >ensuring no duplicates you're neglecting the cost of this. I'm working on this, BTW.

If this happened I would probably just find the old /all/ on github and make an add-on out of it. I read all threads so it has the functionality I want.

>>6309 Great! Could you have it where we can decide to hide threads from certain boards? So we can opt out of having lewd boards, test, layer

>>6311 youd still get all threads, youd just also get /random/ threads so its not just the bumped threads being bumped. we should probably also have a catalog\search for this upgraded /all/ board

>>6311 I've pretty much just copied ukko and now I'm rewriting the crappy code. It's starting to look OK. >>6313 I'm thinking about the catalog, too.

>>6314 Sounds great lainon!

>>6314 >>6309 so uh, h-how's this going?

>>6394 I've put the code I have so far in a branch on GitHub (https://github.com/mgrabovsky/lainchan/tree/mixed-theme). It works but it's not as pretty as I'd like. I'm currently focusing my forces on bringing a catalog to /all/.

>>6396 I believe once this is conoleted we won't have an /all/ as itd be redundant. Might wanna work on a catalog for this instead

>>6399 I think /all/ is here to stay. This is just something to put on the front page, right?

Remember guys Kalyx wants to make sure every board gets a chance, he has strong feelings about "keeping popular threads pinned to the top with all". I'm working on this too.

>>6262 What's your idea about the layout? Should it be a like regular board or more like 4chan's "Popular Threads" with pictures?

>>6402 like the /all/ board. an infinite feed but having 1 recently bumped, then 1 random. >>6401 Kalyx actually doesnt like that people only visit the popular board and only the bumped threads get attention. So this new mix board will bring attention to threads from all boards but include the ones that aren't getting attention because their are tons of threads that are interesting but get no exposure because noone looks around for them.

>>6400 I'm not sure. I don't think we'll need the /all/ board once we have this completed because the idea is for this to work just like the /all/ board but to include a /random/ (not /r/) after each /all/ thread. But we'll see what he thinks after its done.

>>6400 Nice dubs. But, /all/ is not here to say. This post summarizes why: >>6406 Also, I agree with >>6407 This new feature will negate the use of both /random/ and /all/, and shall usher in a new age on Lainchan. I AM SO EXCITED!!!

>>6409 Hopefully the lainon working on the app has had time to work on it too. I would like to see this on the app as well.

Should I make a pull request once I'm done with this?

>>6425 Yes you should. Also make sure you use the new merged vichan.

>>6425 also can you include the search in the bottom bar on the left instead of in the catalog

>>6430 Not sure about that. I can put that on my to-do list, but I don't think it's currently viable.

>>6436 Alright, thanks lainon.

>>6436 lainchan github was updated again. make sure you use that. Also, any updates?

>>6617 I'm finding the courage to send the PR. Also, GitHub doesn't seem to be updated yet.

>>6619 whats holding you back? send it lainon.

>>6619 it will be updated soon. send it so darkengine can look at it and go about implementing it.

>>6620 >>6621 It's there, waiting for scrutiny.

>>6624 Its where?

>>6642 GitHub.

>>6649 you sent the pull request? or you mean the one here >>6396

>>6659 Sent the PR.

>>6262 It's a nice concept, I would like it on a high volume site like 4chan. This site is too slow for it. There are those among us who keep up with /all/ enough that over time we see pretty much every thread, every post on lainchan. It's our way of viewing just the new content instead of having to hit up every board. Mixing in random soykaf would kind of force old content on us that we chose not to read or respond to in the first place. I don't really mind if people hit /all/ first after taking a break either. They are sort of misguided in doing so, because they'd probably have better luck finding content interesting to them by hitting select threads on select boards. It's not like responding to a bumped thread increases their chance of getting responded to that much more than bumping an old thread to the top would.

>>6301 Two queries would be most likely faster then one query mixing those rows. Programatically joining those results is a O(n) operation, just pick them in order first from from set A, then from set B, again from set A and so on. Btw I somehow thought about merge sort when writing that.

>>6909 See >>6309 >Programatically joining those results is a O(n) operation, just pick them in order first from from set A, then from set B, again from set A and so on. What about duplicates?

>>6910 you are right :(

>>6913 Make a request to get ALL threads, take the x latest, random sample zhile resampling the duplicates from the existing set

I had a thought, why not alternate between the newest and oldest posts on /all/? old posts are guaranteed to have been seen less, and it'll give good content another chance before it 404s.

>>7633 This I like. Do we have the required mad skills for doing it?

>>7640 I imagine it wouldn't be much more than making a small modification to the current /all/ page. I don't personally have much experience with web stuff though, if that's what you mean.

>>6262 I think that the /all/ and /random/ mixture would be great. HOWEVER, I think that a much better homepage would be pic related. Not to invalidate peoples' work, of course. We should use it, just not as the homepage, but rather to replace both /all/ and /random/.

>>7755 THIS is the homepage I've wanted since forever. If someone made THIS we would use it.

>>7757 Well kalyx, what is shown in the OP, can we use it? But not as the homepage, but rather a replacement for both /all/ and /random/? Like, we institute it under where /all/ used to be, and delete /random/, because the new /all/ would be a mixture of both of them?

When I see a new thread I wonder which of the older threads it 404d.

>>7757 Tried working on it for a few hours and pretty much have it. There's some fuarrrkery going on with displaying posts and the board list. It might need a little css update too. I can upload as a wip branch on github if you want :D

This may not be much but it would be nice to have an option to go to the catalog when inside a thread.

>>8626 Well, that sounds like a good simple feature to implement while you familiarize yourself with the code. Why don't you make a branch for that and submit a pull request?

bump

Going to kick off this S.Q. General with a request idea - (2 threads in 1 as I did not want to make one just for a request) Being a retard I can't program at all... But I have a shwayyyy idea for a little programming project - some might find this an interesting challenge and I expect it is not a hugely hard program! The idea goes like this: (was something I did in a pseudo way for my degree show at art collage yrs ago - on 7 x 286 machines in very low res). Make an application that draws every possible pixel combination on the screen (B+W only (for now) 640x480). In the drawing of every pixel combination (which will take forever minus a day) there will be every bit of information ever - text, images, photos, diagrams, RAW PCM of every audio too! Hence I called the work Silicone Monkey! Any Takers?

>>10673 Ignore this soykaf - missposted! will do it right...