The initial commit—applying the few modifications that were not specific to our particular installation—has been pushed to
. We will continue to use
as the issue tracker for the time being. I'm sorry for making things complicated.
I have organized a few of the issues into categories below to help you select where you may want to focus your attention depending on your skill and availability.
Thank you so much for your help, Alice!https://github.com/arisu-dev/arisuchanhttps://gitlab.com/arisu-dev/arisuchanhttps://gitlab.com/arisu-dev/arisuchan/issues/1https://gitlab.com/arisu-dev/arisuchan/issues/3https://gitlab.com/arisu-dev/arisuchan/issues/6https://gitlab.com/arisu-dev/arisuchan/issues/50https://gitlab.com/arisu-dev/arisuchan/issues/18https://gitlab.com/arisu-dev/arisuchan/issues/47https://gitlab.com/arisu-dev/arisuchan/issues/57
…settings? please expound
Like blue CSS? Copland CSS could be pretty cool.
settings as in enable\disable enlarge image on hover. change what boards you want to hide from /all/ and dropdown menu of different themes. I personally want a theme that is like arisu theme but purple
also does /dev/ and /q/ and /r/ not appear on /all/?
>>1738>also does /dev/ and /q/ and /r/ not appear on /all/?
/dev/ and /q/ do not appear on /all/ because they are not content boards. /r/ does, however.
a few issues started, alice
some require response / followup>>138
Can't get in without an account,
Registration is closed since the server is shutting down in a monthhttps://gitla.in/gitlain/misc/blob/master/shutdown.md
Pour one out for darkengine
The issue tracker has now been migrated to GitLab.https://gitlab.com/arisu-dev/arisuchan
>>1737>I personally want a theme that is like arisu theme but purple
We added a blue "Copland OS" theme you can select by clicking on the copyright in the footer.
It's nice, still want a purple one tho lol.
So will it be migrated to gittorrent or what?>>1743
Still can't be viewed without signing up which prevents people from looking at what issue has already been brought up
Sign in with GitHub?
sorry, definitely should've linked a hex code #8A2BE2 is the kind of purple I'm looking for. The Chisa purple is close but not as bright.
Also, is it just me or does infinite scrolling not work on /all/?
>>1749>sorry, definitely should've linked a hex code #8A2BE2 is the kind of purple I'm looking for. The Chisa purple is close but not as bright.
Hard refresh. Is this better?
>Also, is it just me or does infinite scrolling not work on /all/?
We had to disable infinite scrolling because there was a bug that it would begin to load more content independent of scroll position. In other words it would literally attempt to load every single thread of the entire website at once.
If you can help us fix this bug, please join us in
on Freenode. Thanks.
doesn't seem like #8A2BE2 is being used. Bigger problem is the huge spaces between each post. It's not the same as the lain and arisu themes
why not fork the lainchan code and then apply these sweet themes? also doesn't seem like #8A2BE2 is being used and the spaces in between the posts are huge unlike the arisu and lain theme. I could've sworn i already posted but it seemed to have disappear
i guess i did post woops. also delete button doesnt seem to load. maybe its because im using the firefox nightly
>>1751>doesn't seem like #8A2BE2 is being used.
I didn't use your exact hexcode.
>Bigger problem is the huge spaces between each post. It's not the same as the lain and arisu themes
That is not true. The themes are literally identical aside from two color declarations. Look at the source.
>why not fork the lainchan code and then apply these sweet themes?
Because lainchan is even more of a disaster than vichan.
>also delete button doesnt seem to load. maybe its because im using the firefox nightly
I use Firefox Nightly on both mobile and desktop and don't experience this issue. It sounds like you are having some bugs on your end.
>link referring to OP post inside thread goes to 404 instead of jumping to OP
here, try it yourself >>1733>default nginx 404>nginx>jpegs are not sanitized, metadata is present, preview rotation is fucked up
is it a bug or a feature?>no selfhosted bug tracker>please sign-in>another soykafty vichan fork without visible replies>eyebleed CSS>posts with one picture occupy too much vertical space>no thread indention
at least, board title has a link pointing back, lemme guess those russkies suggested it to you>bright pictures on black background are not dimmed>high contrast text>let's encrap>no onion mirror>no irc server
Quality web dev here, Sophie. Really adds up to your CV Present Day, Present Time! HAHAHAHAHAHAHA!
>>1755>here, try it yourself
works on this board, not on /diy/ in 'old' threads
Because board directory changed from Mu to Delta
>offers no solutions, only complains, doesn't contribute
Quality comment here. Really adds up to your MO Present Day, PresentTime! D:
Why are we using gitlab for issues?
There are particular issues that are only relevant to this website. I don't think it's appropriate to post them on GitHub.
Why is banners.php not in the repo?
it could make sense to have as a separate issue-only repo under the same github account (similar to https://github.com/ValveSoftware/Source-1-Games
I'd argue it makes sense to have them more easily reachable from each other at least, and GitLab has a slight barrier to entry in that they require an account to even the current issue tracker (although that might be a config issue, since GraphViz's issue tracker is anonymously readable).
On the other hand, it's then arisuchan fork of the general vichan project - so I'd argue site issues are issues of the arisuchan fork even if they aren't vichan issues (though it may make sense to duplicate some upstream, or contribute back fixes & improvements).
can we get this pinned, by the way?
>>1896>can we get this pinned, by the way?
That's probably a good idea now that a) we closed the /dev/ board and b) I am actually working on it some. I should have another commit in the next few days. If anyone else is interested in contributing, please get in touch with me via IRC at
on Freenode or email at
I also set /dev/ to redirect to this thread in case anyone was still checking it.
I think this fixes issue #6 but I'm too lazy to set up a development environment to test it:
diff --git a/templates/themes/ukko/theme.php b/templates/themes/ukko/theme.php
index ada4082d..89f16037 100755
@@ -30,7 +30,7 @@
$body = '';
$overflow = array();
$board = array(
- 'url' => $this->settings['uri'],
+ 'url' => '/' . $this->settings['uri'] . '/',
'name' => $this->settings['title'],
'title' => sprintf($this->settings['subtitle'], $this->settings['thread_limit'])
My main question, is why is this still based on the absolute clusterfuck of tinyboard+vichan, and #2 why do crucial features like quoting require JS?
>Your request looks automated; Post discarded.
Every time when i try to post something.
I don't know how to fix it.
Anyone can help me?