Site Discussion@Heyuri

I don't see anything wrong with them. It's not like the catalog is full of porn

It's not like we're on 4chan's /b/ where its all 3dpd garbage, jacking off is good for you, I'd only complain if they started becoming the most popular kind of threads

Pr0n dumps are awesoem and Heyuri has always had them - especially Japanese 2D, gravure, and AV. Pls post moar of teh hawtness, my b0ner demands it
(but don't overdo it to the point of flooding the board, obviously)

We even used to have a few dedicated pr0n-dumping boards (in addition to what was already on /b/), but they were merged with /b/ along with everything else when /all/ (the Overboard) disappeared, overall site activity was significantly down, and it was agreed that those boards were kinda redundant anyway (especially since every Heyuri imageboard that was not /b/ typically ended up as /b/ + a very loose sense of a theme)

PS: loli3.net and guro.cx were made by kuz shortly after kuz removed Heyuri's own /l/ and /g/ without asking us. I believe kaguya owns them now, but still - nigger stole our boards!!!

>>62614
anon.. gurochan existed for decades before heyuri. gurochan was its own thing, not a breakaway heyuri board...

>>62667
I'm well aware - /l/ and not4chan predate Heyuri by many years also. But the timing of kuz buying gurochan and launching https://g3.kolyma.org/ (now defunct) came very shortly after he removed Heyuri's own /g/ and /l/, and he teased the reveal here like it was going to be a Heyuri thing... and then it wasn't. We r teh betrayed, nevar forgone

(I don't actually care and I was pro-consolidating excess boards to /b/ anyway )

There was a little more info in the original "Kokonotsuba is now open source" thread, where some users wrote about some of the issues they ran into and how they solved them: >>62231

There's also the prerequisites of configuring a server, creating a database, etc., but that might be a little beyond the scope of a kokonotsuba-specific tutorial (and it varies depending on your setup)

Where are you currently stuck? I can try to help you. My biggest issue was having the wrong version of PHP

>>62607
the PIO conn string, idk what 'imglog' stands for
also im a bit confused about what the archive db is for, like is it whats it used for?

>>62616
so for the PIO string you want
mysqli://<NAME_OF_DB_USER(with admin permissions>:<DB_USER_PASS>@localhost/<DB_NAME>/<DB_TABLE_NAME>

I attached an example of my string for reference
dolphinb_root is the name of my privileged user with all perms
password is obviously the password with sensitive information edited out
localhost is my server address (99.9% chance it'll be localhost for you too)
dolphinb_boarddb is my database name
dolphinimglog is the table inside my database that is being used

ignore the archive db info. Mine is the default data

>>62512
Too green

complaining about people quoting OP is bad but misusing the quote feature is worse

>>62492
Can you explain the exact issue with it, besides falling back on "culture"?

>>62567
It's a redundant practice since replies are replying to OP by default

But... Heyuri's culture was originally one of not sweating the small stuff, which I think is more impr0tant than some crap about OP quotelinking. As long as we're keeping within teh rules, let's have fun on the internet

>>62561
> Too green
Eat your Broccoli

I remember when I was the only one who would argue in favour of quotelinking the OP. How time flies...

>>62558
but how does heyuri display these files? is it through something outside of kokonotsuba or something?

I am not a programmer but it's not something via outside of kokonotsuba, I think it should just werk. There were some users who could set up their instances without any issues with tpl files

variables seem to be loaded through the ParseBlock method in the PTELibrary class. you should be able to just modify the arrays that get passed to the method in koko.php if you want to add variables

>>62562
Thanks! Although it seems like there are some variables that aren't defined in either koko nor PTELibrary, which is a bit weird but I should just search further

>>62565
the others are probably from lib_common.php and the optional modules, just do a regex search for

'\{\$.+\}'

and it should come up with all of the template variable definitions

>>62538
thank you kagy ^_^!

>>62538
thank you kagy ^_^!

The most thankful and apologetic man in the universe, right here on Heyuri.

does anyone know directly what causes doubleposting to happen? isnt the post button just a POST request to koko.php, and if you spam it you just refresh the request before it reaches
maybe there should be a timeout like if someone posted theyre locked from posting for 5 seconds

fufu

>>62403
>I want you to know that no one likes you, the reason Heyuri stagnated was because no one wanted to be associated with you, and the boom in new users that happened in december happened because the main point of the advertisements was that YOU were gone
The boom of new users is refugees from other imageboards who long knew about heyuri whose main haunt gave up the ghost of being usable. Eceleb obsessed faggots like yourself notwithstanding, of course. The boom of new users making any sort of attempt to post in the style of the site, I guess.
Even though I've never had any interest in or partaken in soyjakery, it's pretty clear that those guys are having fun and keeping the spirit of doing shit that's funny to them at least in part because of how booty blasted prissy prats who are concerned by people liking what they don't like rather than actually carving out a space for themselves well alive. Your incredible asshurt over something which literally doesn't appear on this website at all, which you, you specifically and other people like you complaining about something offsite, are bringing into my consciousness when here, is the only actual source of soyjaks being posted or discussed actively on heyuri. Congrats. You have made a post about soyjaks. You are the soyjak poster.

>>62477
how can you be so pathetic?

>>62480
How so? That anon merely pointed out that what >>62468 said was incorrect

>>62479
>Eceleb obsessed faggots like yourself
>You are the soyjak poster
>ID:Heaven
Seriously, it's not even believable at this point. Just drop the act

The Q&A is over, so locking the thread now. The drama should get over as well.
>>62482
Also I just want to point out that post was made during the night time for kuz

Posted this on /b/, but guess I should post here too

>I was working on an update but something urgent popped up in the middle of my work, and I didn't realize images were broken for some reason

Believe me I was in a great haste to get back on PC to fix whatever broke it once I noticed the situation on phone
I think it has something to do with one of the recent koko.php updates, I'll do the debugging at a later date

I thought it was a lot of fun, Heyuri should b0rk more often

>>62410
agree ﾀｷ━━━(・∀・)━━━!!

>>62410
agree ﾀｷ━━━(・∀・)━━━!!

i dont like fighting, which makes me indifferent to all sides. there are no lulz Σ(;ﾟДﾟ)

>>62458
I don't like fighting either, I want Heyuri to be the easiest place on the interwebs

>so, I propose something: filter Kuz's name and any discussion about him, and then pretend he isn't associated with the website anymore
That is effectively exactly what kaguya had been doing for months until that big longpost thread between him and I recently

That all started because I was growing increasingly concerned about how far the convenient narrative/white lie of "kuz is no longer involved with Heyuri, he's not here anymore" had deviated from the truth of the situation. I could see it having a terrible impact on Heyuri later down the road when those who were here specifically because they were under the impression that kuz was gone were to inevitably find out that he was still around to some extent - so in a rash decision and the heat of the moment, I tore the bandaid off hoping to resolve things early before the new/returning users could get too comfortable, hoping to minimize the potential outrage/devastation

Obviously this has upset the peace and caused some pandemonium (for which I do take a fair amount of responsibility for and apologize), but I do believe it was inevitable given the circumstances - and I think all of this will inevitably happen again should we go back to pretending kuz is gone when he's not

I know it's not fun for anyone, but I honestly believe it's for the best that we keep transparent and don't try to "swindle" potential/returning users - if they have a deep-seated hatred of kuz (or anyone else here for that matter), it's better if they're aware of the involvement so they don't come in with false hopes and expectations, which will only lead to further disappointment, distrust, and bitterness

(also quick sidenote: I'm not the only one that uses the mod capcode and ID, and I typically only use it when I think it's necessary or if I think it would be funny, so don't assume it's always me. For transparency, my only post ITT before now was >>62424 )

>>62460
what do you suggest to fix this then mod-sama? I feel like most people would be ok with the escapism of pretending Kuz doesn't exist

>>62461
This may be a little too "insider baseball", but if you look at the wider trajectory, it's pretty clear that kuz's involvements with Heyuri (not including the random Rule 8 stuff he posts and his recent "less than effective" efforts to defend his name in the current climate) have been steadily decreasing - both through kuz's own waning interest in Heyuri, and through kaguya's many (but often unseen) behind-the-scenes efforts to de-kolyma-ize Heyuri and to complete the remainder of the transition of full ownership from kuz to him

Now, putting any friendship they might have for each other aside, it's clear that in order for kaguya (or anyone) to one day own Heyuri in its entirety (and thus kuz having no involvement whatsoever), he must remain in kuz's good books and maintain a certain level of mutual trust and respect before kuz even considers. Just think - if I or some random person were to contact kuz, point bananagun at head, and say "ALL YOUR HEYURI ARE BELONG TO US", he'd just LOL and ignore it, right?

The point here is that kuz is never going to give Heyuri to anyone who just asks/demands for it, so diplomacy, politics, and tact are required (or just being friends - that helps too!). Aggression, wild accusations, and calls for revolts/coups are totally useless and ineffective - not to mention they turn Heyuri into a warzone

While I'd be the first to admit that it's very easy to get worked up about kuz and view some of his various actions (whether real or rumored) as "ruining Heyuri", we all have to keep in mind (me especially) that our responses to/about him can equally ruin Heyuri, and can stop the site from being fun for everyone else

Now, this isn't to say we should all just let kuz and kaguya be totally unaccountable and rule over Heyuri with an iron b&hammer - I think they've individually overstepped the mark and exacerbated the situation just as much as certain users and I have, with the careless overuse of b&hammer and the needless antagonizing/ostracizing of certain users in ways that were completely avoidable. I think changes to the current moderation policy (...there isn't one LOL) should be made so that Heyuri doesn't end up making any more enemies out of allies, and so situations like this don't end up going this far, for this long

I'd also like to extend an olive branch to you (assuming you're the anonymous who's been the most vocal about your thoughts on Heyuri meta lately), and ask if you'd be open to a private discussion with me on XMPP (or wherever is convenient for both of us... I'm not very convenient ) where we can discuss Heyuri, your issues, hopefully learn some things/reach some middle ground, discuss PENIS, etc. - if you're interested that is. I'll warn you now though that I'm a shitty and awkward conversationalist

Here's sum historic data, for teh n00bs

ｷﾀ━━━(・∀・)━━━!!

it will be fixed soon

Kaguya is the best mod for being able to keep the retard on a leash

>>62404
kaguya's decent but he's not ideal. He's still associated with you-know-who. Hopefully our next admin will give us a fresh start

(USER WAS BANNED FOR THIS POST)

>>62405
>Hopefully our next admin
I want to believe

Stop spamming /q/ with some words you learn from /pol/

I don't want users thinking I am deleting posts that's not hugging me, but I also have a good idea what kind of poster you are by your previous bans. If users have a valid criticism (you don't need to be polite either, but raging without providing reasons isn't any constructive) against me, I'll take that as an opportunity to improve myself - but clearly you are trying to create some artificial drama, so git B& (again)

Can't. And the mods r sleep it seems. Cp bait post staying up for over 1 hour now

Well fuck, that sucks.

Yeah there should be a way to report iilegal shit

See >>62103

>other than running scripts on webpages and shit like that
...that's it

In my travels through the Japanese web, I fell in love with all the awesome and obscure (to us) scripts that made up the Japanese web in the 90s and 2000s - I've long thought it would be kewl to bring some of them over to Heyuri like we did KuzuhaScriptPHP+, HeyuriRemix, etc., but... it turns out that 90% of Japanese scripts from that era use CGI/Perl, and Perl is b0rked on Heyuri's current servers

Pic related is what my spruced-up version of the Jidou Enquete Sakusei script currently looks like. It's kinda liek /vote/, but users add the options they're voting for themselves along with a comment. Each poll is like its own little board, with each vote option being like its own little thread that you can open up and comment in. All the functionality of poal.me with all the style (and code quality) of 1997!

No posts were made in reply to 62340

>>62348

There was a reply but it got deleted.

It would be nice if i could get an answer cause i am not the spammer.

>>62364
Kaguya still hasn't unbanned you?
the answer was given in that one reply

>>62365
>Kaguya still hasn't unbanned you?

No.

>the answer was given in that one reply

Someone had a meltdown?

Very sorry for that
Please mail me your (ipv4) IP at kaguya@kolyma.net
Alternatively you can use the tripcode mail thingy on /b/