arisuchan    [ tech / cult / art ]   [ λ / Δ ]   [ psy ]   [ ru ]   [ random ]   [ meta ]   [ all ]    info / stickers     temporarily disabledtemporarily disabled

/q/ - arisuchan meta

discuss arisuchan itself. comments and questions welcome.
Name
Email
Subject
Comment

formatting options

File
Password (For file deletion.)

Help me fix this shit. https://archive.arisuchan.jp/q/res/2703.html#2703

Kalyx ######


File: 1493005444547.pdf (844.03 KB, Anonguide.pdf)

 No.245[Reply]

Okay guys, I am currently browsing .org because /zzz/ is much more active there and mostly because it is supported by everychan.
How can I browse this site from my phone on a *chan app?

 No.246

>>245
>Okay guys, I am currently browsing .org because /zzz/ is much more active there and mostly because it is supported by everychan.
They've been around like 3 years. We've been around like 3 days. Give us a chance. =P

>How can I browse this site from my phone on a *chan app?

We would like you to not have to in the first place. Making the site fully responsive (and functional without JavaScript) is one of our priorities.



File: 1492497261844.jpg (52.32 KB, 375x720, non agression principle.jpg)

 No.129[Reply]

What's the future of laintracker?

 No.152

>>129
Not Seph, but it seems like the tracker will stay as-is.

 No.153


 No.164

>>>152
Which means? Who's the current owner? Applebutt or Seph?
>>>153
that thread does not answer my question

 No.167

>>164
>Which means? Who's the current owner? Applebutt or Seph?
The Laintracker was initially built by Niles and Monster. Niles and Kohaku oversee most technical matters while I am responsible for the design and management of the tracker. There was no change of ownership with the move to
lainchan.jp
as the tracker was never explicitly affiliated with the previous site to begin with. It is a community project and always will be.

 No.244

The future of laintracker is on I2P



File: 1492893740226.webm (11.73 MB, 640x360, kcxtfw.webm)

 No.217[Reply]

Please consider the attached video introduction before reading this post, or replying to this thread.

Proposal
An OStatus compliant microblogging instance available on social.lainchan.jp or through an affiliate provider. Examples of such services include https://unsafe.space/ and https://gs.smuglo.li, which are built on postActiv.

Why?
There's a marked absence of decent cyberpunk communities in the GNUsocial federation, largely due to soykaf.com meeting an untimely demise at the hands of Canadian law enforcement. The domain and site are under new ownership, but unfortunately pleroma.soykaf.com will not be functioning for a while. social.lainchan.jp would provide a persistent social space outside of the IRC where the lainchan community could interact not only internally, but also with other federated OStatus services.

While people interested in the GNUsocial federation could just join an already extant instance, social.lainchan.jp would provide a central instance for people who would like to affiliate with lainchan and a community that is definitively by lainons, for lainons. The presence of lainchan on the "fediverse" could also act as exposure for lainchan.jp to a new demographic already receptive to cyberpunk culture.

social.lainchan.jp would provide microblogging and status updates from the lainchan staff, and could act as a home to statusbots and announcements that would otherwise be done through a centralized, proprietary service like Twitter.

How?
postActiv works pretty well. A fork of GNUsocial, it's got a good amount of documentation and several improvements over the original software. With Qvitter or PleromaFE on top it largely functions identical to how Twitter would, with the bonus of federation.

https://postactiv.com/

There's also Mastodon, which has become extremely popular as of late. It's become extremely popular as of late, but is built on Ruby and is a bit more complex to deploy than postActiv is. It also tends to make design decisions that put it at odds with other OStatus compliant providers.

httpPost too long. Click here to view the full text.
8 posts and 1 image reply omitted. Click reply to view.

 No.230

>>229
>applechan*

 No.231

>>230
LOL that word filter

 No.232


 No.233

I am going to register lain.haus later today. Let me know on irc if anyone wants to use it for this.

 No.234

>>233
accidentally torposted. this is thufir



File: 1492437544402.jpg (161.76 KB, 278x646, crash_override.jpg)

 No.89[Reply]

>no repo link anywhere

FOSS or no deal
7 posts and 1 image reply omitted. Click reply to view.

 No.149

I've noticed the [.code] tags don't cancel out the other formatting symbols. This completly destroys anything you write in C. With a repo link I'll fix it myself, otherwise please be aware that this is a fairly annoying issue.

 No.150

It's linked at the top and the bottom:
https://github.com/lainchan-jp/lainchan-jp

 No.151

>>149
They're using
highlight.js
on live. The vichan software uses
$config['markup'][] = array( );
to replace markup strings with appropriate formatting. They'd have to implement a different solution for adding formatting that is sensitive to the code blocks.

 No.169

>>149
>>151
Some improvements have been made to syntax highlighting; code blocks should prevent other tags from taking effect now. Inline monospace (with the
[m]
tag) does not use highlighting

Also, note that highlight.js has pretty bad heuristics for detecting which language is being used. I recommend specifying your language - using
[code python]...[/code]
, for example - if you give a damn.

 No.1891

>>150
for anybody stumbling into this thread and noticing that link's dead:
>>1733



File: 1492414379829.png (83.56 KB, 694x422, tor.png)

 No.34[Reply]

I appreciate the community effort you're trying to do but why would you block tor exit nodes from posting? Hostileness towards proxys is a reason why I stay away from halfchan for example. Come on, alt-lains.

Pic related ofcourse.
6 posts and 1 image reply omitted. Click reply to view.

 No.78

>>70
>angry .org nerds
Wow, what a great way to refer to the community you are trying to usurp.

 No.96

Please allow tor posting.

 No.107

>>70
>>78
Don't fall for false flagging!

 No.1581

spoiler
[italics]italics[/italics]
italics
!!exclaim!!
fuzzy
equals

 No.1851

Trying to make a post…



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] Next [ Catalog ]