I suspect you mods and suckermoot want this shit to stop now, but are too prideful to approach me. No problem. You have three choices.
1. Assist me in making my own fork of nanochan.
- Provide me with a full copy of the database, minus account, session and captcha tables.
- Put up a link to my fork in the global announcements for 36 hours.
- I will give you the script used to convert the database.
- I will stop posting here outside of /b/.
2. Give me the keys.
- Provide me with a full copy of the database, minus account, session and captcha tables.
- Provide me with the v2, v3 and new v3 hidden service private keys.
- Provide me with the SSL keys.
- I will release the script used to convert the database in the next picochan release.
- I will not post hapa-related propaganda on neo-nanochan outside of /b/.
- Opinions which I disagree with will not be discriminated against.
- Current nanochan moderators may be reinstated as neo-nanochan moderators.
3. Do nothing, or delete this thread, or continue deleting my posts for reasons that do not align with global or per-board rules
- I will train my captcha cracker to work on your new captcha and spam your site some more. This will not stop.
You have up to 1 week to decide. You may negotiate. Remember that ultimately, since Nanochan was started by a hapa, I have the best interests of Nanochan at heart. Also remember that Hapase has acknowledged me as the legitimate owner of Nanochan. Furthermore, suckermoot was going to execute option 2 until he changed his mind for whatever reason.
So go ahead and make a choice.
<Give me your data in exchange for a simple conversion script we could make ourselves
<Kill your site and give it to me
<I'll kill your site
All are bad options.
>You may negotiate
We do not negotiate with hapas
>Also remember that Hapase has acknowledged me as the legitimate owner of Nanochan
Keep telling yourself that and how superior your imageboard engine is.
>>6416 >All are bad options.
Choose the best one, then.
Or propose another one which still lets me get what I want.
Personally if I were you, I'd choose option 1.
>simple conversion script we could make ourselves
No, your administrator is not competent enough to do it. He doesn't understand the picochan database structure at ALL. He doesn't understand any of how it works, or how databases work in general. He just wants to be a pajeet.
>We do not negotiate with hapas
Alright then.
Suckermooto will choose an option and fulfill all its requirements, or he will not choose one and option 3 will be the default.
>Keep telling yourself that and how superior your imageboard engine is.
I don't need to keep telling myself, because it's an objective truth. Suckermoot added another few hundred lines of code to nanochan today with no functionality to show for it. Does it really need to take 10 seconds to delete a post? Picochan can delete a post near-instantly.
>>6415 >but are too prideful to approach me
Honestly, I just think it's entertaining. It's less about pride, but more about not making deals with terrorists.
That aside, option 1 does sound appealing to me, if not for the fact that you're willing to share your conversion script.
The reason I'm even putting up this much resistance against you (aka not going with option two) is because that's not what the community at large wants. So yeah, there's your reason (along with the fact that you still haven't obtained "hakase"'s approval of your code, that you decided to drop the agreement in the first place, amongst other petty reasons)
If you're willing to make the promise that you'll release your conversion script when it's done, I'll publish the current version of the database. Once you release your script and your fork is up and running, I'll make an announcement with a link to your site.
While I don't see any reason for others to be outraged at this myself (outside of potentially splitting an already tiny community), I still reserve the right to reconsider until the database is actually released, in case this decision turns out to be majorly unfavorable to most.
>Hapase has acknowledged me as the legitimate owner of Nanochan
That means nothing when you're hakase yourself, you know
>>6417 >He doesn't understand the picochan database structure at ALL.
Well no shit, I haven't even seen your database structure outside of the screenshots you posted back then.
>>6418 >If you're willing to make the promise that you'll release your conversion script when it's done
Yes, I do.
And also I forgot to include one of the requirements for option 1: give me the old v2 and old v3 address along with the old ssl key. Reason being that those were made by hapase, and my site will be a successor to hers. Thus there needs to be a redirect to maintain continuity.
Alternatively you could not give me those keys and just redirect to my site yourself as a sort of insurance policy against me spamming your site/breaking my end of the agreement, if you would like.
>>6423 Well yeah, I just haven't got around to it.
>>6422 >Alternatively you could not give me those keys and just redirect to my site yourself as a sort of insurance policy against me spamming your site/breaking my end of the agreement
Sounds good to me, this would provide actual accountability to the last condition in your first option. I'll give it half a day or so to test the waters before going through with it.
>>6424 Make the database copy in 3 or 4 days, because I am writing the conversion script now (using an old copy of the database) and I want to get that finished before you give me the new db such that I bring my website online with data as up-to-date as possible.
Why do you need Nanochan's database? I mean, unless Nanochan actually closes, there is no need for another Nanochan.
I would like to see how your board develops from scratch though.
>>6429 >tkmizposting
Now that's something I can get behind
>>6431 He could just scrape the site or wait for a new dump to make his fork anyway, and I don't think nanochan's userbase is much like 4chan's, where they have to censor 8ch in order to keep the majority of the sheep they're herding in the dark, some dumb announcement wouldn't hurt. And outside of a couple of onion search engines hammering the v2 address with failed requests to random mod links almost nobody actually uses the old links anymore, and aside from giving asukafag an incentive to not talk about hapas, I'm still not entirely convinced he's able to resist the urge to stop posting outside of /b/. Maybe the v2/v3 redirection could just be temporary, just for a month or so.
>If you want to migrate that bad
I might not even be migrating to picochan myself. Even if I consider nanochan to be superior in terms of UI, stability and in some ways features, picochan is more performant and thus makes for a better experience for the end user. It might be for the best to get endofunctor's opinion on this, considering he's the most likely candidate for the next site admin, if he'd rather maintain nanochan's or picochan's codebase.
>>6418 >Took over nanochan without having an multiple different means of contact with Hakase
SHIGGY. Pro-tip: Never ragequit imageboards, that's what these cocksucking kikes want.
>>6434 >picochan is more performant and thus makes for a better experience for the end user
This would be most notable for users making a new post or thread as for browsing the site most of the pages are cached and can just be read off of the disk without having to call the lua script. The current slowness of nanochan is not that bad and mainly only comes up when needed to delete multiple posts at the same time. You could probably make nanochan repeat these operation which fail due to a locked database and made range deletions not fail if one of the posts has already been deleted and it would resolve my current issues with the current engine.
>It might be for the best to get endofunctor's opinion on this, considering he's the most likely candidate for the next site admin
With the current options I think it would be a good idea to in the future fork picochan and migrate to it. Writing a script to migrate the database will not be that hard. I've already figured out what is needed and have done a test migration between my test instances of nanochan and picochan to see what complications there are in doing a migration. A problem with doing this is if there are unexpected problems and we have to migrate back.
I also have my own high performance imageboard engine I've been working on in my spare time, but it still has while before it will have feature parity with nanochan. My free time is also consumed by working on a project for a Fortune 100 company, so it is still a ways off before it will be ready.
>redirect old hakase era V2 and V3 onion domains
I just want to say that i am against this, this is called domain spoofing and is a really malicious practice, if we redirect them someone that still uses those old domains or old links using those domains is gonna find himself on a destination that was not where he wanted to go.
Cause asukafag's fork of nanochan regardless of what he says is NOT the original nanochan, it's a fork, a derivation, an aberration, of nanochan and this should be at least communicated and made clear to somebody using the old domains.
I suggest to sakamoto to reconsider the decision of redirecting the old domains to asukafag fake nanochan. And instead to consider this alternative:
Instead of redirecting directly to asukafag fake nanochan, i propose to redirect the old domains to a text file hosted on our nanochan at /links.txt inside this text file we can put a brief description of how asukafag's fork came to be(including all the malicious stuff he did), we can specify that we have nothing to do with its administration and only then we can put the link to his fork, if he breaks the deal we remove his link from the text file or the redirection at all.
We should also put a link to out homepage in the same file, this way whoever uses the old domains can choose between the two, is informed of what's going on and can bookmark the new address.
>>6444 >make range deletions not fail
>slowness from deleting multiple posts
Both these issues should now be fixed, and range actions will no longer regenerate the same page multiple times for each action.
>Writing a script to migrate the database will not be that hard.
It's definitely not as hard as I make it out to be, but if someone else wants to do it I don't want to waste the effort in making something redundant.
>>6448 Yeah, after some consideration, if I'm not going to back off from the deal, the best compromise would be to create a separate page that links to the original and fork of nanochan, along with any future nanochan-like imageboards. I'm doing this as a means for other nanochan clones to advertise themselves, so another condition I'd like to add is that this page would only be up for as long as I remain as the admin of nanochan, and if any new admins decide not to link to your fork anymore, it's their choice. Either way, the new database archive is now up at /nanochan.db.bak.
>>6448 I'd rather just do nothing regarding the old onions and keep it the way it is now. Nanochan's and picochan's databases are very similar. The only major difference is from supporting multiple images in a post. Paying with the old onion addresses is not worth a script for such a simple migration. I'd suggest making one my / ourselves if we want it.
1. Assist me in making my own fork of nanochan.
- Provide me with a full copy of the database, minus account, session and captcha tables.
- Put up a link to my fork in the global announcements for 36 hours.
- I will give you the script used to convert the database.
- I will stop posting here outside of /b/.
2. Give me the keys.
- Provide me with a full copy of the database, minus account, session and captcha tables.
- Provide me with the v2, v3 and new v3 hidden service private keys.
- Provide me with the SSL keys.
- I will release the script used to convert the database in the next picochan release.
- I will not post hapa-related propaganda on neo-nanochan outside of /b/.
- Opinions which I disagree with will not be discriminated against.
- Current nanochan moderators may be reinstated as neo-nanochan moderators.
3. Do nothing, or delete this thread, or continue deleting my posts for reasons that do not align with global or per-board rules
- I will train my captcha cracker to work on your new captcha and spam your site some more. This will not stop.
You have up to 1 week to decide. You may negotiate. Remember that ultimately, since Nanochan was started by a hapa, I have the best interests of Nanochan at heart. Also remember that Hapase has acknowledged me as the legitimate owner of Nanochan. Furthermore, suckermoot was going to execute option 2 until he changed his mind for whatever reason.
So go ahead and make a choice.