No.41
Add a points system where you can grow a pokemon-style creature by making posts that are cool. I'm not joking, this is a serious suggestion.
No.42
>if this is just a re-implementation of the original Arisuchanwe are NEW AND IMPROVED arisuchan so im open to making more changes
>what do you plan on implementing next?idk, nothing? lol i havent felt the need to add anything else lately
>Please add the option for users to choose to hide posts before this place grows to a point it's overrun with low-effort posters.ive kinda decided to just delete low-effort or shitposts for the most part, but ill consider adding a post hiding thing, ill look into it sometime soon when i have a minute
if theres stuff that would help the site be more useable etc im open to suggestions, termer recently suggested borders around posts for better layout visibility and a floating reply window in thread-view to up site usability - i recently implemented both
additionally, another user had emailed me having trouble with the post form and i changed that too to make it easier to use / more obvious
so to reiterate - yes im open to ideas
things that fix an issue are more top-priority so let me know if theres any issues youve found obviously
overall, stuff that is niche and doesn't really exist on other imageboards like
>>41 suggestion is *perhaps?* interesting but much less likely to happen unless its an extremely good idea
No.43
>>42Fair. Maybe use the thread to post updates and fixes? A place for transparency is good if only to let people know the site is still cared for and not just still running on a laptop in some guy's closet. That's the only other suggestion I'd have for now.
No.44
>>43not a bad idea
i have posted about some site changes ive made in the past, but those posts are scattered across multiple threads
i can understand how seeing regular updates about site maintenance and changes could give users and passers-by a sense that the site is well taken care of
ill think think about how best to approach this - its a bit weird because even if there are no active changes going on the site is still constantly maintained, im not sure things like PHP and OS updates are even worthy of notifying people about?
i will give you an idea of the state of things here for more context -
>this imageboard is running a newer version of vichan than probably *99.99%* of others that run vichan or a fork of it (we are pretty much our own fork now due to all the changes ive made, but our fork is from a much newer version of upstream vichan than others)
>the main web/storage server for the site is automatically backed up once a day and OS/PHP/etc updates are done once a month *at the very least* - i also test all the sites main functions myself after each update/change
>the sites database backend is a highly-available clustered DB that is backed up every minute of every hour of each day (total overkill)
>the site also has ALMOST enterprise-tier caching, SDN, and web application firewall (actual enterprise-tier is way too pricey lol)
>also, every time there is a new post on this site A TEAM OF MODERATORS LOL is automatically sent a notification with a link to the new content in case its something that needs to be deletedeverything here runs on money (and not in a closet)
this sites infrastructure is most likely better than the vast majority of other imageboards (besides huge ones like 4chan etc)
im a professional sysadmin of 10+ years and because of my job im used to doing maintenance in a way that is nearly invisible to end users
any additional infrastructure changes would pretty much be total overkill at this point lol (i am considering maybe another web/storage server for active-passive high availability though)
lastly - the site is probably very close to being "feature complete" so if i did make a dedicated place for change notifications - it probably wouldn't continue being updated beyond a certain point - in the future that could give the impression that maintenance has stopped lmao
an example of this is lainchans "latest news" section - the last post there about maintenence is from 2022 - is the site still maintained or did the admin just stop wanting to notify everyone about normal updates? my assumption is its not maintained - but only because that dedicated place for change notification has not been updated - not sure i want to normalize something that eventually turns into that sort of situation here
something to think on -
>what other metric is an accurate predictor of site maintenance if the site has been feature complete for years?like i said, i am always open to suggestions
No.55
the thread hiding JS has been modified to also allow hiding replies
i also added support for hiding posts in thread view and unified the storage for hidden posts across views
you can hide any post anywhere on the site now, and it will remain hidden anywhere else on the site it shows up unless you manually unhide it
No.68
i made a bunch of CSS changes recently as well as changes to some JS that has browser TTL set for 30 days (oopsies)
clear your browser cache for the site to see all the changes, otherwise wait 30 days for your browser to fetch the updated resources
No.70
added mp4/webm support with inline expanding
also added embedding youtube videos
fixed backlink generation on /all/ overboard
and also fixed an issue with the captcha and quick-reply window where the page would reload if the captcha was activated in fixed post form before floating post form was triggered
No.72
uploaded files can now be a maximum of 30MB
No.82
it appears that previously if a post was submitted with both a file(s) and embed link that the files were stripped
posts can now contain files + embeds and both will be stored and rendered
additionally, the embed regex has been modified to fix escaped characters from playlist URL's and embeds have been moved to the files div
lastly, i integrated tegaki.js for Oekaki on /art/:
>>>/art/28 No.83
disabled multi-image for threads (OP's) but keeping it enabled for replies
because we do images on the left of a thread post, when theres a million images in an OP it makes the thread look kinda fucked up in board/index view
keeping embed+image for thread OP's though
No.86
got our site added to an imageboard webring - you can see the boards from those sites on our webring page as well as with the webring JS button at the bottom of board indexes (next to the boards catalog button)
major JS changes - post hover has been overhauled, thread expanding got updates, thread and post hiding JS got some tweaks too
moved reply button, changed CSS so thread OP's maintain horizontal stacking until mobile layout shift
revamped next/prev/catalog/report/delete buttons
a bunch of minor CSS changes
some quality of life improvements to vichan under the hood
also enhanced our WAF rules and added some mitigations to vichan to block new bots we have seen recently
as you can tell ive had a lot of free time on my hands lately
No.89
adjusted our backlinks to mimic the way they look on jschan instances
they shows up as "Replies" at the bottom of posts now, instead of the default vichan place at the top of posts after the intro span
never realized how shitty that looked on vichan until i started browsing more jschan boards recently
No.91
totally refactored the catalog theme
added a catalog to /all/ as well as threads.json and catalog.json
>this was a huge pain in the ass
No.93
>>92damn you're being busy i see
small nitpicks about the catalog: would be cool and i guess look nicer if the catalog posts would have full width on mobile viewport or something like 90vw (the catalog on mobile is waaay smaller than on index) and something about that catalog button looks off to me, like color and positioning
just some personal nitpicks tho otherwise great work imo
No.95
>>93>would be cool and i guess look nicer if the catalog posts would have full width on mobilei actually made it a point for it to be 2 columns on mobile
a lot of frontend/style changes ive made the past few months have been focused around keeping as much text/content on the screen as possible (borders and padding on lots of stuff has gotten much smaller) - im not positive on this theory but i think things "feel" more like an imageboard with more text on screen at once (less fluff, margins, padding, more items in horizontal space)
>something about that catalog button looks off to me, like color and positioning im not really sure about it either - i kinda just thought that for /all/ there should be a catalog button at the top of the page too - since it would take longer to scroll all the way down to the default one - and you'd only do that if you knew it was there to begin with *since most overbaords dont have a catalog new users wouldnt know it exists for /all/ otherwise*
i could do the fixed floating catalog button like arisuchan.jp did but i honestly am not a fan of of it stealing screen space on mobile
i basically just put it in the same spot as the one at the bottom of every board index vertically, but above the postcontrol form (threads list)
i like the color for the catalog button at the bottom of the page, but that might be because i put colors on the report/delete buttons too - trying to figure out how to incorporate a little bit more diversity of colors on the site
i do agree that towards the top of the page it does stand out in a sea of red and black
if you have any ideas feel free to let me know - if you can edit the way that part of the page looks in GIMP or something and send an image to depict your suggestion that would be the most helpful way TBH
No.96
>>95huh, so i looked and tested around a little and figured out that "grid-template-columns: 50% 50%;" in the catalog.html file, in the #Grid block should do the trick but then noticed it cuts of images a bit
also noticed that it really should be 2 columns instead of just one which breaks if the screen is <422px like picrel
No.97
>>96damn, i didnt realize some phone screens were that narrow!
i modified both our navbar's CSS and the catalog CSS for you
the navbar wont overflow anymore for you and the catalog page tiles will go into full-width mode when a screen is small enough to only have 1 tile per row
i appreciate you helping me get that fixed!
No.98
>>97thank you a lot, as a webdev myself i know how annoying it is to make a site responsive, especially when the client is retarded and keeps the browser windowed and or at 150% zoom
>damn, i didnt realize some phone screens were that narrowyeah mobile viewports are pretty narrow, i think the smallest vw i've seen was 330px
glad i could help a bit
No.99
Hello. I run another webring imageboard, homurachan. Would you be interested in following us back?
The main board's on /homu/ and the endpoint is here.
https://homurachan.org/webring.jsonIf you're not interested and want us to unfollow you, I don't mind.
No.101
>>100lol. The title is a silly meguca feature, I didn't realize anon had it enabled on /psi/. I'm just illya. The admin shows up as ## admin on meguca, ## head meido is custom loc for board owners on my fork.
No.102
>>101lol thats funny, nice to meet you dude, im Alban
i added you to our webring config
Ты русский?
No.103
>>102>lol thats funnyYeah, got a big list thanks to an old admin. Titles rotate hourly, it's a fun pseudo ID system. Not sure how they work on lain and here, do they rotate every post or are they derived from the IP? I'm posting via tor.
>i added you to our webring configThanks.
>Ты русский?Not russian, just an old nickname that stuck. There's a russian dude on /asylum/ though. Got an ex-arisuchan user too, I'll point them your way when I see them again if you're interested.
No.104
>>103>russian duderussian speaking, sorry. he's eastern euro.
No.105
>>103>do they rotate every post or are they derived from the IP?theyre just random by post, i could enable poster_ids and modify vichan a little to get them to stick per-IP but eh
>Got an ex-arisuchan user too, I'll point them your way when I see them again if you're interestedsure why not
>>104>russian speaking, sorry. he's eastern euro.same, my russian is pretty shitty though
i see you run a movie night on Saturdays at 10pm - i used to do that on a previous IB i had years ago too, that was always super comfy. curious, what do you use for your movie stream setup? im not seeing a link anywhere
No.106
>>105>what do you use for your movie stream setup? im not seeing a link anywhereDIY lol. We try to get the magnet link up early and anons fetch it themselves. Meguca has a synchronized timer hash command that keeps people roughly in sync, it's syncwatch in the banner info modal if you've got js enabled.
No.107
>>106lol i never even imagined people would do something like that
if you could use some inspiration feel free to hop in our IRC, mostly anyone active on our IRC would probably have some good suggestions
personally, i wouldnt mind sitting down and helping you set up / build out something more streamlined if you could use the help
on my old imageboard i used this streaming server written in golang:
https://github.com/gwuhaolin/livegoi probably wouldnt use that one if i did that now, it looks unmaintained and it didnt have any documentation to begin with, but generally speaking, using a streaming server and writing up a frontend would be the most agnostic approach (you could even write a plugin to incorporate this type of stream into your site as a floating window or something people can pop open)
doing something like that would basically require a VPS/server somewhere with good bandwidth to supply the stream data
theres also lots of random little things you can just spin up to get a webpage and everything:
https://github.com/calzoneman/sync (popular with ib communities)
https://github.com/RblSb/SyncTube (never used this one but it looks cool)
https://owncast.online/ (twitch-like experience)
even that much additional infra isnt necessary though, the "live tv" page i run now at 0xfdb.tv is on a box in my house, behind a CGNAT, with no ports open, and uses the same GPU to encode the channel streams as the one that runs the screens im looking at to type this message
i abuse cloudflare cache for the streams so that im only ever serving up enough data for 1 viewer per channel (so nobody can saturate my home internet), and the stream only starts up and consumes GPU cycles/power when someone starts viewing a channel
there are many many options you can consider here
No.110
also rewrote the site links in our archive (previously some were outlinks to .jp's archive) and added a few boards that were missing
>(unless theres something else im forgetting about then ours is probably the best way to browse the arisuchan archive at this point)some of the missing stuff i couldnt find i just used placeholders or my closest guess for (i also made 1 small CSS change to fix image expanding on the archive for mobile browsers)
<if youve browsed https://legacy.arisuchan.xyz/ before then you need to clear browser cache for it to get the new content (its HTTP cache which mobile browsers might not clear when you "clear site data" unfortunately)<added redtextoptimized post hover JS more
totally redid thread auto reloading JS
No.111
>>110Cool. Is the arisuchan archive here more thorough than the one on .jp?
No.112
>>111as long as im not missing any other hidden boards then yes ours is more complete
No.113
single-image replies now have horizontal layout under 650px browser width
hide post button moved
expand video got hide button removed and replaced with clicking on expanded video to close
No.114
added search (slightly janky at the moment)
added catalog button to top of all board indexes
new thread form is now hidden behind a button
No.116
>>115that's actually really cool. reading raw text uploads usually sucks.
No.117
>>116thanks i had a feeling it would be a good idea
i just went a step further and added PDF support too
clear your browser cache for the site if you already opened a TXT file before seeing this reply (otherwise it might not work right)
No.118
>>117Yeah works well for me.
No.120
made us a new "recent posts" style homepage
feedback on the site layout etc is welcome
if you have thoughts, then let me know!
No.121
>>120This?
https://arisuchan.xyz/Hard for me to really judge since meguca's approach is "dump him in /all/" (and I like that), but it looks good and advertises the extra services well. My main feedback is that the site rules link isn't obvious, I'd make it always red and not only on hover. Maybe you could use the board name instead of the title to save horizontal space in latest posts?
Two things about mod logs though. First, I couldn't access them on tor, I got endless cloudflare captchas. Not sure why they're even captcha gated. Second, they don't feel prominent enough. Are they only accessible through the homepage? A board's mod logs should be directly linked on the index page (see jschan sites in the webring) or maybe accessible through the top bar. What I did on homurachan was add generic links for the logs to the top bar's info panel and set the href to the current board with js. In any case, they should be more prominent on the home page itself, most people won't notice the gray link on a dark background in the bottom left corner.
Also does the captcha session timeout while the quick reply box is open? I needed to refresh to post. The captcha should autorefresh if it does timeout.
No.122
>>121>site rules link isn't obvious, I'd make it always red and not only on hoverthis is a no-brainer, thanks for bringing it up, was half asleep while making the new index page lol
> Maybe you could use the board name instead of the title to save horizontal space in latest posts?this is another good idea, i thought about this myself but forgot before the time i stopped working on it this morning, i will implement this
>about mod logs though. First, I couldn't access them on tor, I got endless cloudflare captchas. Not sure why they're even captcha gatedon vichan instances, log.php is a direct method to DDOS (and to SQL inject) your sites database - not sure how mod logs work on meguca but this is an issue with vichan
<our log.php is completely custom and has been hardened against SQL injection attacks, but it still leaves our DB vulnerable to DDOS - hence the super aggressive CF captcha i put on it (effectively acting as a rate-limit)this is something i plan on changing but havent found the time to get around to yet - im going to rebuild the public mod log as HTML that gets built on mod actions, ive already laid the groundwork for this just need to finish it
>Are they only accessible through the homepage? A board's mod logs should be directly linked on the index page thats a good idea, personally i never look at any boards mod log but i could see that people who do would find that more useful
<i estimate itll probably be sometime within the next week or two when i have a chance to finish the mod log stuff
>does the captcha session timeout while the quick reply box is open? I needed to refresh to post. The captcha should autorefresh if it does timeout.yeah the sessions it creates have a timeout, its easier for me to just extend that from this:
define("SESSION_EXPIRE_MINUTES", 30);
to this:
define("SESSION_EXPIRE_MINUTES", 120);
timeout shoulnt be much of an issue anymore
ill post updates when some more of these things get done, i appreciate the feedback
No.125
>>122>not sure how mod logs work on megucaEvery mod action is written to a mod_log db table after it's committed, bans also go to their own bans table. The mod action/ban/report logs for a board are fetched from the DB, formatted with an HTML templating engine (quicktemplate) and served as an HTML table at an endpoint like /html/bans/homu. The bans page also has some simple authentication done on the backend so mods can unban there and all three pages have SSE support for live updates on my fork.
If you want to see the code yourself, the files you should look at are server/admin.go, db/admin.go, templates/auth.html and templates/report.html. Go is pretty straightforward to read if you have any C experience and quicktemplate mostly uses normal HTML with Go variables. Not my fork but it's what I've based my work on.
https://github.com/zkm2/shamichan No.126
>>125that is similar to how it will work on our vichan fork once im done with it
unrelated but i modified our post-hovering JS to also support the "recent posts" links on the homepage
No.128
public modlog has been re-done as statically built HTML
<board indexes now have a link to their public modlog
>i also fixed some other template errors and cleaned up the "catalog-search-row" bars style a bit
No.132
board indexes now get auto updated
if there is a new thread posted - you are given the option to add it to the page without refreshing
if theres a new reply to a thread thats already on the page - the reply will automatically be added to the page just like the thread auto-updater does
