[ an / aw / cr / fi ] [ ra ] [ au / ga / he / sp ]

/aw/ - AwsumChan Meta

Discussion of AwsumChan itself.
Name
Email
Subject
Comment
Verification
File
Password (For file deletion.)

File: 1502943094129.jpg (14.89 KB, 261x187, shittaste.jpg)

 No.9[Reply]

Is there a board you feel belongs on AwsumChan? Tell us here and we'll make it a reality (or at least a temporary one).

[We won't honor your request if it's trash or completely illegal though.]
12 posts and 3 image replies omitted. Click reply to view.

 No.304

>>299
I could do a board like that. Maybe /li/ for Lifestyle?



File: 1542427492247.jpg (154.05 KB, 960x720, lyf8jso.jpg)

 No.21[Reply]

I've been unsure what needs to be done to Tinyboard in order to make it a better software for our site.

In response, I'm creating this thread so you – the user, can make suggestions for me to implement into the site. Feel free to request anything. Hell, if you don't like what I've done, you can tell me that too. I'll listen.

The source code that we use for AwsumChan can be found at https://github.com/Circlepuller/Tinyboard
19 posts and 2 image replies omitted. Click reply to view.

 No.279

Show anchor image thing when bumplock? It doesn't seem to work no matter what I do



File: 1500959957193.jpg (164.9 KB, 1024x1170, carlonduty.jpg)

 No.1[Reply]

Yes hello, this is the meta board. Here, you can talk about AwsumChan, or ask the staff/users questions.
6 posts and 2 image replies omitted. Click reply to view.

 No.105

There was a short bit of downtime where I upgraded the server to the latest version of Debian. After upgrading some packages, the site should be running smoothly. Sorry for the inconvenience.



File: 1613318321150.png (80.9 KB, 797x820, padoru.png)

 No.301[Reply]

Did you see Vichan now has a new maintainer? and he seems to want to actually work on Vichan.
I myself am happy and can't wait for the huge mess that Vichan currently is to be slowly fixed with time.

 No.302

Forking hell and bikeshedding at its best again.

I really appreciate Circle’s leading work on Composerization, Twig cleanup, and most recently PHP8 readiness. I wish you and h00j can join up, exchange and share these changes upstream. It’d be a win-win.

 No.303

>>301
I feel Tinyboard/vichan's biggest issues aren't easily fixed, they're more deeply rooted in the design. Does this effect the end user however? No, not really. I am glad to see there's someone on the same boat with updating the codebase though and I hope to see it continue into the foreseeable future.

>>302
h00j seems to have done a solid job at adding Composer, etc. to vichan - although he probably could have cherry-picked commits and saved himself some time, hah. If I was ever approached to make a collaborative effort, I'd be down. I'm honestly really bad at getting a solidifying a plan and it's been somewhat of a writer's block whenever I have the time to sit down and work on things.



File: 1610798759477.png (201.94 KB, 1120x753, AC3.png)

 No.286[Reply]

Came across some old images, surprised this site still exists.
5 posts and 4 image replies omitted. Click reply to view.

 No.292

>>291
Perhaps Naix?

 No.293

I currently own 0.00052 Bitcoin and slowly growing, Bitcoin will reach 100K in 2024, by then I will probably have like 0.008 so 800 dollars yeehaw.

 No.294

>>293
what the fuck I posted this on /cr/

 No.295

>>293
>>294
You sure? Posting on other boards, including >>>/cr/ seems to work fine.

 No.296

>>295
I probably fucked up myself



File: 1574133364625.gif (1.25 MB, 255x136, vawtf1.gif)

 No.111[Reply]

Is your fork more stable or secure than reg vichan? What are the benefits of your fork over mainstream vichan? Also do you do php work? If i end up using your fork on my site would you be a consultant for it? Just easy shit like best setup options, a bit of help setting up cache, and very minor style changes. It should be super easy for you, and it would pay good.
9 posts omitted. Click reply to view.

 No.204

>>201
I haven't tried RocketLoader. I might look into it since it's free though.

As for directory changes, it's possible although you'll have to rebuild the HTML for the entire board as well as move all uploaded files and thumbnails to the new directory. You'll also have to change a lot of database entries like you said, but that /should/ be it. Tinyboard (and most imageboard software) don't intend for you to change the board URI anytime down the road.

>>203
While you do share a bunch of valid points, I don't see PHP as /that/ bad. I definitely agree that Cloudflare is not to be relied upon as a tool to prevent intrusion or dramatically increase performance. It does help smaller websites handle an increased traffic load though, which is really handy for those using a budget VPS or shared hosting package who have content that reaches a large amount of people. From my experience, people who use Cloudflare on top of a Tinyboard site generally use it to have the static content served reliably, not to "speed up" the dynamic content served over PHP.

As for the PHP hate - legacy PHP apps have been historically badly coded, easily susceptible to attacks, and inefficient. I wouldn't blame the language, but the poor code ethics that seemed to surround it for the longest time. Node.js might have better general performance but NPM has become CPAN shit show 2.0, with a lot of inexperienced developers flooding their community with really poor code (gee, wonder what that sounds like). Call me wrong, but PHP 7 has been something long needed - forcing developers to patch vague and broken code that miraculously worked in PHP 4 and 5. Sure, we might not like it, but it's for the betterment of PHP-based software.

 No.207

>>203
No shit, Sherlock. Come back when your perfect project finally has these:
1. Data compatible or at least easy to migrate from/to Tb/vi;
2. Customizabiliy on par with inc/config.php, especially spamfilter and autoban regexes;
3. Platform genericity (RoR, Node, Go, whatever the next meme trend is, still hasn't beaten the popularity of plain old LA/EMP)

Regarding CDN, yes I just need cache for my cheap hosting, "security" be damned. (My nginx is configured to never serve directly outside though.) The extras are just a flip of switch away anyway so it's a loss not to explore and make full use of them.

 No.281

what happened to the patreon? take my money!! and fix it, or tell me why it's not working if it should be. i want ALL THE FEATURES

 No.282

>>203
>Take ANY php web app, and it can be coded to be far more efficient in node js
just, no, https://www.techempower.com/benchmarks/

 No.285

>>281

The Patreon got deactivated due to lack of activity. I would reactivate it, but it would require another audit by Patreon staff and subsequent transaction activity.



File: 1606330757388.jpg (21.46 KB, 600x400, keeping-your-pygmy-goat-in….jpg)

 No.277[Reply]

PHP 7.4 support I am beggin you, 8.0 is almost out and I don't care much about it but 7.4 is nice.
Also is the archiving system complete? or is it missing something or works wonky?

 No.278

PHP 7.4 has been supported since I use it on my local development environment. As for archiving, it's still incomplete but feel free to contribute - there's a lot of design considerations to it that make it difficult to finalize. (It's a different approach than what NPFchan does)

Any code contribution to Tinyboard is highly appreciated, as it's an open source project supported completely by the community.

 No.283

>>278
I see you haven't updated the repo since February, is the thing dead? or what are your plans?

 No.284

>>283

I wouldn't call it dead. I intend to keep the code stable on recent releases of PHP until further notice.

I've just been really busy IRL, let alone lack motivation or manpower to add some of the bigger features.



File: 1574133041651.jpg (8.9 KB, 225x225, download.jpg)

 No.110[Reply]

Did you look at php 7.4 yet? Regular vichan is totally broke on it. Was wondering if your version will adapt to 7.4 or or at least make a patch for it so there is a 7.4 version. This will be a big deal to get it working for php 7.4, as php 8 will be totally different and require major overhaul. But at least ppl can run it on php 7.4 for a long time.
39 posts omitted. Click reply to view.

 No.177

>>175
savetheinternet was always very protective of his work, and I don't ever see him willing to hand over the original repository if he ever makes a reappearance. I'm not concerned with that anyway. Any version of Tinyboard >= v0.10.0 has been from my repository.

>>174
He's not actually future-proofing anything. He's just having vichan ignore errors in future versions of PHP rather than fix them. This will eventually lead to issues that will cause unwanted behavior. Errors are meant to point out broken, bad, or flawed code in programs. While this might make sense for vichan, which labels itself as having "next to no active development", I intend for Tinyboard to be in active development for the foreseeable future, so it makes no sense to "future-proof" it by ignoring errors. Instead, I will aim to fix them as they are spotted.

 No.178

>>177
Cool!

 No.202

>>178
BTW please look at your commit here:
https://github.com/Circlepuller/Tinyboard/commit/31e27a51c20ccceb59ed20c8cac829bfac1ce710

Line 357 and 377

This same thing is done TWICE? Or is it intentional?
Also should the modLog() at line 366 be moved to the last instead?

 No.205

>>202
Those are intentional, they're for different queries.
As for the modLog() call, it's there because the board itself has been deleted at that point, and the actions taken after that are focused on cleaning up the aftermath.

 No.280

Don't know if you still read this but I wanted to comment that the lines to enable automatic removal of EXIF from image files seem to have been left out of your config.php even though the code to do it is present in post.php:

$config['use_exiftool'] =true;
$config['strip_exif'] = true;

When added to instance-config.php the feature works, but of course there is no mention of it on the config page.
Anyway, thanks for your work making this software useable with php 7.4.



File: 1600750651846.jpg (154.76 KB, 1244x850, 1579147566328.jpg)

 No.262[Reply]

Name a reason why I should use this instead of TinyIB, also greetings from 28chan :^)
4 posts and 1 image reply omitted. Click reply to view.

 No.271

>>270
FTFY, the guy just keeps posting cringe lmao

>>262
Also look into Wakaba or Kareha if you want some non-PHP alternatives, I forgot to mention those.

 No.273

So like, is this the only updated version/fork of vichan/infinitychan/tinyboard/openib etc?

Also does this have the feature where you get a tooltip, when you hover over the date, showing how recently it was posted? This feature is in openib and also on 4chan lol

 No.274

>>273
To answer your first question, no - I'm pretty sure there's a few other actively maintained forks of Tinyboard/vichan. What this fork essentially offers over other forks is overhauled dependency management handled by Composer, removal of abandoned features in vichan, and support for WebP. It is compatible with recent versions of PHP (support for 8 is in the works once it is officially released).

As for "x time ago" tooltips, they are provided by js/local-time.js so just have that included in your JavaScript files in the configuration if you want it. (I don't have it on here at the moment, I don't know why)

 No.275

Can there be larger file uploads for posts if one hosts this software on their site? in case i want music video and stuffs posted

 No.276

>>275
Yes. You can set the maximum upload size in the configuration. You will also likely need to make sure your PHP and web server configurations also are the same size or larger.



File: 1552404569734.gif (180.35 KB, 340x192, 1552158984797.gif)

 No.78[Reply]

So I keep thinking about tinyib. It is only 1.5 mb of files, and it can do anything other imageboards can do. It can even deploy in flatfile mode, which makes it so anyone can set up an instant site on just about any php server.
Instead of trying to modify 50mb or so of thousands of files of code, why not just build on tinyib? Tinyib proves that one does not need thousands of files to run an imageboard. So wtf do ppl have thousands of files in like vichan for? Every single file is another potential way to do an sql injection or xss injection. For example, people in the know can run one of the files, for example just point the browser to mychan.org/inc/data/hidden.php AND put the proper syntax afrer the hidden.php, like mychan.org/inc/data/hidden.php?3w the ?3w can do anything, reveal ip's manipulate the db, anything. It seems that chan boards don't give a rats ass about security, and they all just say oah gee let us know if there are any bugs.
21 posts omitted. Click reply to view.

 No.134

>>132
To be honest I thought your reply would take a lot longer as I didn't expect this to be a populated imageboard.
About my code, it is pretty much experimental as I'm discussing with some people what would we be aiming at the end of the project. Some of my thoughts is that it must be "portable" for a lot of reasons:
- you must be able to provide basic maintenance on the code (this is one of the reasons I'm using Go);
- you must be able to port it to another place without much configuration;
- you must be able to provide a front-end as you wish based on the resftful api (there will always be a fallback to noscript users, of course);
Most of the work is still on paper as we are thinking about the tools we'll be using to build it. For example, do we sacrifice the first point of portability with a RMDB such as postgres or do we stick with "embbeded" technology that we have in Go (ex. Badger, bbolt)? With some tests we see that it can handle a considerably number of people on your imageboard.

 No.135

>>132
>>134


> I feel imageboards and *chans in general are becoming a niche thing.

Unfortunately this is true. Meanwhule you can see that there are a lot of communities rising. I mean, look at this: http://textboard.org/prog. It's basically a textboard with LISP enthusiastics. I feel that even though imageboards are dying, specific communities are being born in a fast-paced manner.
But as you said, it's becoming a niche thing.

>I think it's all based on what the developer is trying to achieve.

You're 100% right here I have no comments to make.

>User accounts are a highly controversial topic in imageboard software, see https://wakaba.c3.cx/shii/ for more on that.

This is an awesome reading, thank you for sharing this. As accounts I would not identify them to other users. It would have the same aspect as the "(You)". It's debatable or I could make it optional, I don't know to be fair. I would not require an e-mail I guess as it would be a hell of verified tripfags. hah

>I do feel that imageboard JSON APIs should try to follow a general standard in the sake of compatibility.

Post too long. Click here to view the full text.

 No.256

>>78
Thanks to this post i deployed some TinyIB instances and found out it isn't 1.5mb…
but 600KB!! (after some simple optimizations and deleting unnecesary folders)
so yeah it is light as all fucks and i think with some more optimization (the developer like line breaks and spaces a little too much)
you could get it to 580KB without too much trouble, maybe even less, later im going to try and make an instance as small as possible.

 No.257

>>256
I just read the part about removing the db code which i agree on and will later make a fork to do so, removing that code could easily make it 550KB or even less, god i want to make an instance 500KB so bad

 No.264

Anon, I didn't forget about our conversation, but the pandemic just made me start my life from the bottom again. Sorry about that.



Delete Post [ ]
Previous [1] [2] [3]
| Catalog
[ an / aw / cr / fi ] [ ra ] [ au / ga / he / sp ]