Next generation imageboards

>new generation
Fag, we still in same imageboard since 2003.

shameless self-bump out of interest

File: hey_leon_by_gannadene-daj3rbh.jpg (2MB, 1600x1600px) Image search: [Google]

2MB, 1600x1600px

We come to image and text boards to get away from cancer like that, anon.

I need one with modern webm, and new file format support, and extremely simple.

>>57159953
>extremely simple
Kek.

>>57159915
I'm not talking about making glittersome and cute, normie-compliant UI. I'm talking about engine that would have some highly usable functionalities like watching threads for changes and getting notifications when new posts occur.

>>57159853
Lynxchan is pretty fast.

>yotsuba blushing
this is weird.

>imageboards
>next gen
for what reason?

>>57159853
>and it's dead with last commit 3 yrs ago
welcome to reality. nobody cares about you or your projects.

every couple of months there's a kid making this exact post dreaming of making the next imageboard, and as expected, it dies with nobody giving two shits about it.

don't waste your time

>>57160552
>click to watch this thread
>anon, someone has responded in the thread you are watching
>live updating threads without shitty timeout-based ajax requests

>>57160608
I'm aware of how software market works. That's the reason I was curious if there were any attempts that were successful. After all chans like 4chink and infinitychan have huge traffic and php is hardly the solution for such use cases.

>>57160547
>node.js
Someone did fall for the meme concurrency solution, huh?

>>57160670
Don't forge memeDB. An imageboard should be meme to the core.

File: 1415224605534.png (13KB, 427x474px) Image search: [Google]

13KB, 427x474px

>it's an ideas guy thread

It simply would not catch on unless it was unique enough to stand out from the crowd

>>57160670
>>anon, someone has responded in the thread you are watching
>>live updating threads without shitty timeout-based ajax requests
>install 4chan X
>keep thread open
>notified every (You) I get
I can see how push notifications would be useful though. It's just not particularly revolutionary.

>>57160706
Imagine the conspiracy theories on /pol/ about missing posts on lost acknowledged writes with memeDB.

>>57160723
Meme off, it's not an idea, it's a query out of interest.

>>57159853

The closest to an improved imageboard was a Russian website but it improved only on support formats you could post and some other stuff

I seem to recall they added upvotes or something and that killed it or something to that effect.

The thing with Websockets is that it is IMO overkill for something like 4chan unless you are going for realtime. 4chan's needs are quite different than an average site just hosting an imageboard.

I really think that if a newer imageboard comes into existence, it should not be written in PHP despite PHP 7 being a lot better than what PHP 5 was and PHP being scalable enough seeing how Wikipedia uses MediaWiki. A modern imageboard needs multithreading and async/atomicity built in to really be more efficient. Hard realtime posting and different formats in terms of evolving the format is less important in my eyes.

Which means any new imageboard should probably be written in some compiled language via C, C++ or Rust IMO.

4chan's hosting issues really could be lower provided even it went to switch to PHP 7.

>>57159977
4chan-x.net

File: Screenshot_2016-10-20_20-18-27.png (135KB, 1366x768px) Image search: [Google]

135KB, 1366x768px

>>57159853
>>57159953
Funny because I started exactly something like that. :^)

The old outdated source code can be found here: https://aww.moe/4jw22n.zip

(Live: http://nanoboard.ga/)

>>57162220
nice reddit clone

>>57162246
Well, I'm not using a tree hierarchy anymore. I gave up on that design. Also, Reddit wasn't the first to use non-flat threads and there is nothing wrong about it.

Obviously, there won't be any kind of sorting.

>>57159853
There are 10+ on the other site being developed.

>>57162751
Post links, I'm interested.

>>57162790
Just go there. The most interesting is probably nntpchan but I development may have stalled. There was one based on php and another on node.js. They push out new image board stacks every week but they have trouble getting them to scale well.

>>57162927
Yeah, I already knew about nntpchan. But its codebase doesn't feel right (HTML 45.1% JavaScript 28.7% ... C++ 12.2% ?)

Still can't be worse than Futaba/4chan though.
http://pastebin.com/4JVjS02b

So I still disagree with >>57162751

File: canvas.jpg (37KB, 480x332px) Image search: [Google]

37KB, 480x332px

Anyone remember this piece of shit?

LOL, Moot is such a genius

>creates an English copy of Futaba, 100% copy, didn't change anything, not even the color theme

success

>tries an original idea this time, without copying the Japanese boards

total failure

>>57163046
Well, the fact he knew about Futaba isn't nothing

>>57159853
keep it simple, stupid

>>57163212
4chan isn't actually simple

>>57159853
I was thinking of adding push notification to an imageboard project I've been working on, but the thing is, it's not secure to allow any browser to register for push notifications without an account. And having an account on an imageboard is not quite what we want.

>>57159853
>realtime push notifications via websockets

I actually implemented this, and my own JSON API to support it, wholesale in efchan's fork of the earlier Tinyboard builds, although the current version went to vichan instead and back to the refresh-update model.

That chan isn't fast enough to warrant it at all, but it was a fun thing to try, and let the mods sit on a page which updated, realtime, with every post on the chan.

Technically that kind of pub/sub scales O(n^2), but so does everyone crazily refreshing via Javascript, even if it's to 304 to your cache. Open TCP sockets aren't that big of a deal when your servers are set up right, especially if you're familiar with IRC hosting.

However almost everyone, even 4chan, proxies via CloudFlare for some CDN and DDoS attack buffering, and high volumes of Websockets via CloudFlare will mean they'll want to you switch to a higher plan. I didn't do anything of that, it just went to a really fast dedicated I had lying around a porn host.

>>57161188
The big CPU drain is thumbnail scaling. The big bandwidth cost is thumbnail hosting. HTTP/2 helps, so does WebP, with the latter. Neither of those are related to PHP.

There's a big advantage overall in keeping the basic pages static, when a lot of those hits can just be served by nginx and only POSTs hit the scripts.

In my mind, the threading model is what makes a *chan a *chan - for better or worse. There's some room for experimentation, certainly.

>>57159853
Real-time imageboards are a thing as in you see what another anon is typing. Some interesting ideas could sprout from this but as of now you either like it or hate it.

>>57163535
>>57161188
>Websocket is hard/overkill
I disagree. It's not hard to achieve 30000 concurrent connections on a single server.

Some can even handle 10 millions: https://en.wikipedia.org/wiki/C10k_problem

>>57163046
wow. I just realized that at least moot didn't make the mistake of turning 4chan into his flawed project which is canv.as.

>>57159977
custom scripts have had those functionalities for ages

do you put noko in the email field too?

>>57159977
You literally can do that

>>57163912
email field???????????????

its no longer 2012 grandpa

https://github.com/bakape/meguca

I mentioned the board I made in the last "4chan is doomed" thread a while ago and some people were interested so I put it online. It uses websockets.

http://sepli.net/

>>57162220
>>57164645
Looks shit.

>>57164241
>Go
>Node.js
Two runtimes? Also, bloated af - """ga.js""" - webdev things.

>>57164241
Screenshot?

File: 7KDrqxf.png (328KB, 671x1047px) Image search: [Google]

328KB, 671x1047px

>>57165137
>can't click a link

File: Screenshot from 2016-10-20 18-23-04.png (109KB, 1680x1050px) Image search: [Google]

109KB, 1680x1050px

>>57165244
well fuck this

I'm working on something like that right now.

some of the features that i've implemented

oAuth2 facebook and twitter integration
optionally you can make a tweet every time you post that will be something like "Hey check out the post I made on chanr.io *link to post*"
location sharing
avatars
notifications
back up threads on the cloud

these are some of the few i have done so far

File: 1466995590043.png (571KB, 1120x1080px) Image search: [Google]

571KB, 1120x1080px

>>57165386
>oAuth2 facebook and twitter integration
>cloud
Nope.

>>57159853
The only possibly useful feature is push notifications so you no longer need JS "extensions" to poll for new posts. Even so, imageboards aren't IRC or chat rooms and a lot of threads aren't even fast enough to benefit from real-time updates, so from a user functionality point of view the polling solutions we have now are just fine. Push would potentially be useful since it should decrease load on the server from all the clients polling for updates.

File: snapshot_09.43_[2016.07.28_08.09.01].png (4MB, 1920x1080px) Image search: [Google]

4MB, 1920x1080px

>>57165294

File: 10cdb183287ee29f3fe8095f8519771d703f77e7_hq.jpg (64KB, 757x1024px) Image search: [Google]

64KB, 757x1024px

>>57166263
>3.82 MB shitty png

File: 1418673922875.png (125KB, 318x368px) Image search: [Google]

125KB, 318x368px

https://github.com/microsounds/akari-bbs/tree/thread-mode

>>57159853
websocket would be nice and remove a lot of overhead.

I would also like some kind of session based private messaging, contacting anons is really tedious.

File: AcBu8A5.jpg (103KB, 1024x1462px) Image search: [Google]

103KB, 1024x1462px

>>57166375
why is this so perfect

>>57166327
>lineart that is >50% solid white ruined by jpeg artifacts

File: 10cdb183287ee29f3fe8095f8519771d703f77e7_hq_waifu2x_art_noise3_tta_1.png (429KB, 757x1024px) Image search: [Google]

429KB, 757x1024px

>>57166597
It's still shit but it isn't an global warming cancer.
FTFY

File: 1463792728787.png (711KB, 1600x2162px) Image search: [Google]

711KB, 1600x2162px

>>57166675

File: 4OHlldg.jpg (48KB, 543x960px) Image search: [Google]

48KB, 543x960px

>>57162220
>Reddit chain reply system

>>57166832
>reddit invented tree threading

there is so much underage in this thread it's painful

2x3chan uses InfinityNext

Lainchan uses its own software too

>>57166832
>4OHlldg.jpg

Don't.

>>57166859
I never said that it was.

>>57166889
Then there's no reason to look down on it as it's a lot less of a clusterfuck than 2channel style post anchor links.

File: 1476522954906.jpg (16KB, 547x480px) Image search: [Google]

16KB, 547x480px

Infinity Next. Needs a lot of work though. The developer goes by Joshua Moon.

There's also Lynxchan, and I'm sure that the Next frontend could be ported to lynxchan, giving it a modern interface for users.

They all have caching problems and are fucking trash. Somehow the person who worked on Yotsuba is a true god of the php spaghetti and made something that works.

T. 8gag /tech/nician.

>>57166375
>C - 80.8%

why

File: 14770090403112.png (654KB, 1600x2162px) Image search: [Google]

654KB, 1600x2162px

>>57166931
>Not being a complete retard
>Talent
>Autism
>Perfectionism
>Performance
I wonder.

>>57166931
Having someone else run your bag of unsafe bag of memory leaks and buffer overflows on their Internet-facing personal VPS is how some people prove their talent/autism/perfectionism to themselves.

I mean no one would use C if they weren't a grizzled 50-something Unix hacker and infosec expert, right?

>>57159853

Some kind of automated "general thread" creation would be pretty cool too, maybe a shortlink so we could favorite it too

>>57167230
The imageboard I wrote just uses tags. No more boards, no need for general threads.

>>57167284
Link?

>>57167289
>>57164645

Source is here: https://github.com/nkeronkow/tolxanka

>>57159853
>Are there any specific reasons why aren't imageboards built with newer technologies?

Because they honestly don't need them.

>>57167487
I agree. But there are reasons I don't want an imageboard built with PHP.

>>57167539
Name one.

>>57168079
4chan?

>>57168144
A reason, m8. Not a site built with PHP, but the reason WHY you don't want a site built with PHP.

>>57166832
Tree threading + post number links like 4chan has would be awesome desu.

>>57167136
You seem to be forgetting that all your bloated and inefficient meme languages were implemented in C. Manual memory management is only unsafe if you're too dumb to count.

>>57168575
4chan uses PHP and full of SJWs.

>>57168653
So you still don't have a reason for why you don't want an imageboard built with PHP?

>>57168631
You didn't implement any of my meme languages and posturing at being a lolhardcoreexpertunixssystemrogrammer by writing your toy programs in C instead of a language you're personally qualified to use isn't going make anyone with an IQ over 12 run it on a public facing server.

>Manual memory management is only unsafe if you're too dumb to count.

If you've ever spent any time running through the CERT database rather than pretending to be a competent programmer on an anime shitposting board you'd know then that practically every major piece of software written in C was engineered by people too dumb to count. The only conclusion to draw is that people not bound by legacy code who opt to write new application code in C in the year of our lord 2016 are all exactly the sort who should be forcibly shoved back in the JRE/.NET playpen.

>>57168875
>If you've ever spent any time running through the CERT database
Retarded.

>>57165386
6/10 troll

File: extension.png (77KB, 604x839px) Image search: [Google]

77KB, 604x839px

>>57160670
>>click to watch this thread
>>anon, someone has responded in the thread you are watching
See pic related.