[ 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.]
7 posts and 1 image reply omitted. Click reply to view.

 No.242

>>241
Thanks for the reply.



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
14 posts and 2 image replies omitted. Click reply to view.

 No.229

>>228
I can enable js/ajax.js.
As for replacing the email field with an options field, I have no intent to do so? Why? Because the email field allows for optional email AND for one to sage/noko option their post, which is useful.



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: 1583925412531.png (3.85 KB, 901x35, Untitled.png)

 No.225[Reply]

What's this?
I got this problem when I install it manually.
2 posts omitted. Click reply to view.

 No.230

>>227
First off, what do you mean you installed Composer manually?

Also, which shared hosting provider are you using? Most of them support limited SSH commands, including Composer.

If for some reason you can't use Composer in the production environment, I recommend the following:
- Install PHP (of the same version as the production environment) to a local development machine (your desktop or laptop)
- Install Composer
- Do the steps needed to install Tinyboard on your local machine
- Copy your vendor directory to your production environment
- If you can proceed with installation on your production environment and you don't log any errors, it should be a success and you should be able to delete/remove the local development environment installation

As a side note, it's always good to run a near copy of your site locally so you can work on it safely and deploy it to your production environment without issues. (I do it for this site although I've let a couple bugs slip through on accident)

 No.231

File: 1584455759490.png (9.87 KB, 1364x76, same.png)

>>230
Download it from here https://getcomposer.org/download/ and install it by extracting the files to web directory.
000webhost, any recommendation?
I tried it with xampp and got same problem.

 No.232

>>231
I really don't recommend using Tinyboard on 000webhost or most free hosts. But anyways to help you out I've made a ZIP of the vendor directory you'll need in order to run the current version of Tinyboard (v0.10.2):

https://file.io/M0PWQE

 No.234

>>232
>404'd

 No.239

>>234
File deleted after a few days.
Honestly, just do some reading on setting up a proper dev environment for PHP. XAMPP is a good start, but it's the bare basics and usually only works for, well, basic PHP applications.
I will reiterate that Tinyboard should not be used on a shared hosting provider. I really recommend using a VPS, as most shared hosts (especially the free ones) typically don't allow command-line applications like Composer, md5sum, FFMPEG, or ImageMagick/GraphicsMagick/Gifsicle, which are ALL highly recommended for use in Tinyboard for it's standard feature set.
And by the way, I did use 000webhost at one point when I didn't have a job. They got hacked and they did an awful job at protecting confidential user data.



File: 1585264004520.png (20.37 KB, 994x806, cheaper.png)

 No.235[Reply]

i cant seem to get it working do i put !45erte in the custom_capcode field or some thing

 No.236

>>235
hello

 No.238

>>235
Capcodes go in your name input.

<name and/or tripcode> ## <capcode>



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.
19 posts omitted. Click reply to view.

 No.132

>>131
You bring up several good questions here. Also, I'd love to check out your Go imageboard software. Can't lie that I've been doing a similar project, hah.

>Do we need yet another imageboard software? I mean do we have enough people looking to new imageboard software?

This is a tough question. I'd say the first part is largely philosophical. There are a lot of options, and there is a lot of variety among them. But imageboards are a fun software to work with and there's always something new that one can attempt to apply to the imageboard dynamic. For the second part, I really don't think the audience is there anymore. I feel imageboards and *chans in general are becoming a niche thing.

>How much is too much? Is 50mb of deps too much? Do we need a new stack? For example I plan to do my software run on containers as you'll only need a simple script to update it as Go binaries are 7mb/15mb.

I think it's all based on what the developer is trying to achieve. Are they looking to emulate a full suite of imageboards like 4chan? Maybe they just want one imageboard? Maybe they want it to be real-time with multi-file video and audio uploads?
Dependencies and programming language stacks I feel are really up to the choice of the developer as well. You don't NEED dependencies in most cases, but they can provide you with tooling and features that would otherwise take a lot of time to create yourself, as well as maintain.

>Do we need new features? User accounts so you can keep track of replies and watch threads or even a new "UI/UX"?

This is a matter of what audience you're trying to cater to. If you make a 4chan clone, you can expect a majority of your audience are the same people who would use 4chan. User accounts are a highly controversial topic in imageboard software, see https://wakaba.c3.cx/shii/ for more on that. A new UI/UX for imageboards is always something I've been interested in, since imageboards generally use a layout that dates to the late 1990s.

>Do we follow bigger software standards as response layout (vichan's .json endpoint)?

Creating a standard for imageboards is always something I've been interested in. I do feel that imaPost too long. Click here to view the full text.

 No.133

>>79
Better yet, move it to the Gopher protocol or the new spin-off "Gemini".

 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.233

dwadadwadadawdadawdawdadadawdadawdaw



File: 1580891817133.png (6.03 KB, 186x66, WebP.png)

 No.211[Reply]

So far iOS is our last major obstacle (screw IE lol).

Is there any polyfill usable on Tinyboard (i.e. something to easily add to $config['additional_javascript'] or $config['url_additional_javascript']), to make pics viewable on iOS browsers?

Yes I know about pagespeed and the likes. I don't like keeping extra sets of converted images. It defeats the purpose of saving space.

 No.212

Regardless of above,
when I use ImageMagick to convert a WebP file to a JPG thumbnail,
the result is fine,
but IM feels obliged to also write these to stderr:

>Decoded /tmp/magick-**. Dimensions: * x *** . Format: lossy. Now saving…

>Saved file /tmp/magick-****

Somehow IM needs to make temp files only when dealing with WebP format.
That's fine.
But Tinyboard's image.php (line 376) treats the stderr message as a blocking error.
Can you fix this?

 No.213

>>212
I'll look into it. I had WebP on the agenda and it was implemented for a while, but I was noticing a lot of distros were behind on the support for it. But that should not be a concern now.

 No.214

>>212
>>213
Plain GD (unless very ancient PHP) already works well with WebP and thumbnailing though. It's just config.php suggests IM and GM are still better at this job for some reason.

GD thumbnail functions are more hardcoded in image.php thus less configurable. I could modify it myself but I think it's better to suggest upstream changes rather than fiddling alone.

For example, what do you think about adding imageinterlace() for making progressive (smaller) JPG thumbnails, and imagejpeg() defaulting to about 75 quality?

 No.216

>>214
PHP 7.2 didn't have support for WebP most of it's release schedule. But since most distributions now have forced an upgrade to 7.3 due to a vulnerability, it would make sense to implement WebP as an option finally.
As for JPEG thumbnailing options, that seems like it'd be a good idea, I'll do some tests to see the difference.

Excuse me for the seeming lack of presence, I've been really busy with ongoing events and have yet more planned through March.

 No.221

>>214
>>216
So a followup on this - turns out I never removed the code that implements WebP. All that should be necessary in order to use it is to add this to your inc/instance-config.php
$config['allowed_ext'][] = 'webp';



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.
38 posts omitted. Click reply to view.

 No.176

>>175
tinyboard I meant instead of tinyib

 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.



File: 1580449258246.png (4.76 KB, 240x80, redis.png)

 No.208[Reply]

1.
I'm trying Redis. When I try to rebuild there's this error:
>Function Redis::delete() is deprecated
Seems renamed to del() or something. Please update the code?

2.
NPFchan added memcached support sometime ago. Is it easy to port that?

3.
Between these two which do you prefer for Tinyboard?

 No.209

Believe it or not, I had removed Tinyboard's support of Memcached a while ago (NPFchan never added it themselves) since it was being abused for an open exploit. This has been largely patched in most installations of Memcached so I decided to add it back since you mentioned it.
I've also changed the call from Redis::delete to Redis::del to fix that deprecation issue.
As for an opinion, I'd recommend Redis more. It has a much bigger following and seems to be more reliable since I haven't heard of any deeply concerning exploits like I have with Memcached.

Also, I'd like to note ahead of time that APC will be deprecated (and eventually removed) in a future version of Tinyboard, and I highly suggest using APCu instead.



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.
6 posts omitted. Click reply to view.

 No.129

>>126
Using Cloudflare on here, I haven't noticed any issues. I can't speak for Rocketloader or any of CF's paid offerings. Worth trying on a site mirror though.

Tinyboard unfortunately does use a fair bit of inline scripts and style tags. Luckily CSP does allow you to whitelist them - see our CSP for an example.

>>127
I think you're a bit paranoid. If you're a firm believer that imageboards should have an incredibly small codebase, just go use TinyIB. Although I can acknowledge that a fair bit of *chans on the dark web are harbors of illegal content. Sad.
Also, please don't try to impersonate staff, lmao

 No.201

>>129
Rocket Loader is free though. Did you try it on?

Anyway another question:
I want to change a board's directory name (URL), and/or migrate it to another Tinyboard setup.
There's no auto procedure for URL renaming AFAIK, so I need to do it manually.
Where else should I look besides the board's dir and database entries?

 No.203

>>201
Rocketloader and cloudflare in general are stupid. If you are that paranoid about being hacked, just lower the attack surface by not having shit ppl would want to hack. Also, cloudflare is not some magic protection, for example if someone knows the server ip address, cloudflare can be bypassed entirely- just like you do when you ssh or sftp into your own website. Lastly, if you are running code so slow where you think a cdn is ultra necessary, how about growing a brain and using a more modern technology than php. Lynxchan is a good example. Node js is far superior to php.
Sure, a few sites like Wikipedia use php still, but they have to have lots of servers at an absurd cost. Take ANY php web app, and it can be coded to be far more efficient in node js or go or something. So instead of relying on a stupid cdn, code the fucking thing in a modern language in the first place, then no cdn is needed. Basically, tards like you who shit your pants over stupid shit like rocket loader create your own problems by existing in php which is shit, outdated, and just stupid.(don't try to impersonate mods)

 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.



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