(Old) (No longer true) The end of Vichan maintenance. (Vichan has reached END OF LIFE)

ctrlcctrlv commented 1 year ago

Well, I have tried and tried to find a new maintainer.

Unsuccessfully.

@perdedora was the latest. Just poofed as usual, no communication.

@czaks will either return or he won't. I am archiving this repository. Email copypaste@kittens.ph to discuss this matter.

perdedora commented 1 year ago

Just had some personal troubles for the past week or so. Going to push updates before the end of month

ctrlcctrlv commented 1 year ago

You're free to fork the repo @perdedora. I'm really done with this whole thing. If you do do that work you may link it to me and I'll put in README.

Removed from organization:

@27chan
@perdedora
@h00j

Retained:

myself;
@czaks.

Thanks.

ctrlcctrlv commented 1 year ago

And furthermore that offer is open to everyone.

@lainchan, @314chan, @fallenpineapple, @27chan, @discomrade: there is no way I can "bless" one of you as none of you decided to take over vichan maintenance when that was possible, but I can still list any of you as possible continuations of maintenance.

ctrlcctrlv commented 1 year ago

All issues are closed.

All PR's are closed.

All files moved under vichan so that the message will appear early on in the page.

I did not overwrite repo history. All history is in tag final-pre-eol.

To clarify:

Three commits are made:

commit 2d092461fc5d6d5d6b61dcb06026923e0e7603c4 (HEAD -> master, origin/master, origin/HEAD)
Author: Fredrick Brennan <copypaste@kittens.ph>
Date:   Thu Mar 23 06:03:27 2023 -0400

    Vichan has reached EOL (oops i eated it)

    Close #543.
    Close #544.
    Close #543.
    Close #417.
    Close #384.
    Close #351.
    Close #350.
    Close #345.
    Close #327.
    Close #188.

commit d4e25308ad784c0bdc7acfba879b094f46de9807 (tag: final-pre-eol)
Author: Fredrick Brennan <copypaste@kittens.ph>
Date:   Tue Mar 21 03:30:15 2023 -0400

    Vichan has reached EOL.

commit f631b83fb144b4b9a003ca7562366764b3e1bdce
Author: RealAngeleno <angeleno@screamer.wiki>
Date:   Mon Feb 27 14:32:28 2023 -0800

    fix issues with the banner script not working

    PHP 7.4
    Notice: Trying to access array offset on value of type resource in on line 13

    Notice: Trying to access array offset on value of type resource in on line 14

    Notice: fpassthru(): read of 8192 bytes failed with errno=21 Is a directory in  on line 17

f631b83fb144b4b9a003ca7562366764b3e1bdce by @realangeleno was the last real commit. d4e25308ad784c0bdc7acfba879b094f46de9807 added the EOL message and serves as the last real commit and tag final-pre-eol. 2d092461fc5d6d5d6b61dcb06026923e0e7603c4 closed the repo.

perdedora commented 1 year ago

wow, this is some next level ego display and breakdown (same as your video about php foundation killing old projects)

theres no need for you to move this shit into a subfolder other than your narcissist persona. people don't come here expecting a great software and commits every day. everyone knows the development has stalled. if you really needed to do some shit, just archive the repo, fucking child.

basedgentoo commented 1 year ago

@perdedora I agree with you and I'm very sorry that this is the route the previous maintainer wants to take. If you want, I welcome any work on my fork. I hope that it becomes the de-facto fork that others spin off of. Currently the only thing I've done is revert the commits announcing the discontinuation and the 2nd commit defacing the README.

This goes to @discomrade as well. For what it's worth, I appreciate the small commits you guys have been making to the repo. Even if they're small, insignificant changes, I appreciate the fact that you're willing to contribute to the project. People that work on this don't get recognition enough and I understand why Fred got angry at the community. But acting like this isn't the right way.

Discussion here: https://boards.4channel.org/g/thread/92297158

My fork of the repo with NO CHANGES currently besides undoing these commits and force pushing: https://github.com/basedgentoo/VichanEX

ctrlcctrlv commented 1 year ago

Perhaps consider I do what I do to spur discussion that has stalled.

I did not simply archive the repository to allow this discussion to continue. I also want to see if @czaks is still alive, he was my friend.

Don't judge me so harshly.

ctrlcctrlv commented 1 year ago

(Archived repos no longer allow replies to threads.)

basedgentoo commented 1 year ago

Is it true that someone e-mailed you in regards to a critical vulnerability in the software seeking a bounty for it? Was this the issue that they e-mailed you in re to if this is so? https://github.com/vichan-devel/vichan/commit/191dbd3be02d1fd59b2845f913acdd223003c3fd

This doesn't seem like it would be a critical issue described (and this one is fixed). But if there are unpatched security vulns we should at least make that known.

ctrlcctrlv commented 1 year ago

I don't remember if I was emailed in regards to #516.

RealAngeleno commented 1 year ago

This might be what basedgentoo was referring to. From a KolymaNET dev:

Vichan HAS been effectively abandoned, there are currently 4 known security issues which KolymaNET developers have located in Vichan. 2 critical, 2 non critical. The first one (Critical) was reported privately, but after failing to deliver upon the promised vulnerability reporting reward, we did not report the other 3. They have been patched on our version, though.

https://sp.logwarehouse.net/read.cgi/soy/2652435#2652571

ctrlcctrlv commented 1 year ago

What is "KolymaNET"?

RealAngeleno commented 1 year ago

Internet company, which owns soyjak.party, kereste.moe, and many other websites.

https://www.kolyma.net/about

ctrlcctrlv commented 1 year ago

@basedgentoo We agree more than you think. The reason I have taken these drastic moves is so that the community will figure out who is going to be the recipient of critical vulnerabilities in the future, as I'm telling you all it can't be me. I have neither the interest nor the time to deal with the time-sensitive nature of them. I want the community to figure out who is going to be the new recipient. You don't need to agree with my methods, but I've been around over a decade, and I sure know how to get you all here, don't I? ;-)

ctrlcctrlv commented 1 year ago

I will fire up Tor to click that.

basedgentoo commented 1 year ago

You probably should indeed fire up Tor to click that. Bunch of trolls lurking in that community/space. Be cautious in dealing with them.

If this was really a ruse to bring attention to the project and get someone else to finally take it off your hands, I commend you for your excellent trolling and strategy. It seems to be working well lol.

ctrlcctrlv commented 1 year ago

It sure is.

ctrlcctrlv commented 1 year ago

OK, I looked at the KolymaNET website.

In general it's semi-professional (only semi, lol): Screenshot_20230324_002128

However certainly professional enough to assume maintainership of this repository. I am OK with KolymaNET taking over, if that's what they want. Is it?

ctrlcctrlv commented 1 year ago

Chud #Developer 2023/03/24 04:54:24 №/soy/2652504 [Report] Brennan does not "own" vichan. He did not create it, he does not possess a copyright over it. Its not known for sure who does, but as just a maintainer, he is not even the end all source on who can use vichan, how, and who gets to use it. It is a fork of a fork and based on tons of stolen/uncredited software. In addition to this, the software has been effectively abandoned for years, and has recieved almost no updates. This announcement only makes this situation de jure, and is likely just an attention grab.

All this to say, it is likely that KolymaNET will be developing its own software to replace Vichan, though the specifications of this project are classified.

What an inane comment. I have never claimed to have owned vichan, never claimed copyright over it, never claimed anything but being Marcin's chosen successor until he returns. This "Chud #Developer" doesn't know what they're talking about, and is casting aspersions unfairly.

basedgentoo commented 1 year ago

Please don't do that. You'd be giving the repo to people who don't care about open source software, would keep the security updates to themselves, fix them in private but never release them, and leave the community with just as little support as having no maintainer. I'm willing to take the security vulnerability reports and pay someone (even you!) to fix them. I don't want to see this software die and I do legitimately care about it.

If you want to give it to someone with more credentials, why not perdedora (assuming he wants it?).

Their whole thing is about making money. The owner is a rich dude who wants to monopolize imageboards.

ctrlcctrlv commented 1 year ago

Oh, okay. A Russian Jim Watkins, then. Thanks for taking the bait everyone and discussing this with me.

If that Russian Watkins is the same man who wrote that comment as "Chud #Developer" I'd never give posters of such inane comments the repo anyway :^)

ctrlcctrlv commented 1 year ago

It's also incorrect to say that vichan is stolen. It has a clean title from @savetheinternet, to @czaks, to myself, with third-party contributors all documented in Git. I knew almost all its developers over the last thirteen years personally. What a tryhard, trying to use money to replace experience.

basedgentoo commented 1 year ago

The guy who wrote that comment isn't the Russian Jim. The owner's name is Yuri Kuznetsov (kuz). He has a team of hired moderators and developers that work and run his boards for him. So that's just his developer speaking.

ctrlcctrlv commented 1 year ago

I see. So the Russian Jim is even more out of touch. Perhaps ~~kuz~~ Chud #Developer is the Russian Ron.

ctrlcctrlv commented 1 year ago

That site isn't so badly designed though even if the users are misinformed. They like №! Anyone who likes № is cool.

ctrlcctrlv commented 1 year ago

Regarding @perdedora, they just got mad at me but I don't really hold grudges, the reason I did not take their offer of maintenance is because I'd been waiting on it for like two months. And they keep switching accounts. All I want is someone with a stable identity to take over and receive security patches. It can even be @perdedora. It can even be you, @basedgentoo. Yes I did put furry art on the README to make people mad enough to comment, you caught me. Now let's see if we can solve this issue. :-)

basedgentoo commented 1 year ago

Would you like to talk to me in private / call or something?

ctrlcctrlv commented 1 year ago

Sure. On Discord I'm copypaste#6969. I can also install GNU Jami again, or we can use Jitsi.

basedgentoo commented 1 year ago

You'll get a friend request in a second.

basedgentoo commented 1 year ago

I will also confirm my identity externally.

ctrlcctrlv commented 1 year ago

Just drop a GPG key here. Mine is same as always:

fred@デブ狸~/Downloads/DCE% gpg2 --list-secret-keys
/home/fred/.gpg-mfek/pubring.kbx
--------------------------------
sec   dsa3072 2022-04-21 [SC]
      98F28F767470129FBE3B054CE2154DD1A1C77B8B
uid           [ultimate] Fredrick R. Brennan <copypaste@kittens.ph>
uid           [ultimate] Modular Font Editor K Foundation, Inc. (Grants department) <grants@mfek.org>
uid           [ultimate] Fredrick Brennan <copypaste@kittens.ph>
ssb   elg3072 2022-04-21 [E]
ssb   ed25519 2022-09-16 [SA]
ssb   cv25519 2022-09-16 [E]

ctrlcctrlv commented 1 year ago

basedgentoo commented 1 year ago

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQENBGQdKmQBCADEajp2oKISOdqrYv7ld/2N6olYcf0w1FtikPBKH2o9DJlOlYU6 HV63KFMfxYDXazWajvjltFdZmr5vA99Vg9mU0SyyQcVnujyczzQ1dcmKu2e6wyds Rv3zNc+SqQGtojVZpZEwvNCjlYz79zYhcdXJ5I53TGprjPAOxZVYw18soCbInya8 srDQA3qWx3dz9HewVr494jK+sMOelMuQwncu9ayy237kfYzthEmI2QuIT3LSodRJ IV19x6tM13e4FJcsn78Z2L63ncY0Vc4KNVgJUwyzZCZMau6TsWhDJGXzWj51Erlu LFbDYLWX9xhE05ycQxDrlZ7jZh3LmF+IJmYbABEBAAG0C2Jhc2VkZ2VudG9viQFO BBMBCgA4FiEEXcTXaKEXe2Sojwg3anTKasAZrcEFAmQdKmQCGwMFCwkIBwIGFQoJ CAsCBBYCAwECHgECF4AACgkQanTKasAZrcH0IAgAk7O+wyKRijViMak2YNJHZ40j 1lFb+OupqcBPdf1BaChy0JHN96P501cjWkMSI+nsdaewtMP4BP+BCJP5WBzyFrci pium8KbzgRt6N9xudJPfaWRlzLswgmgMTKFr/Wtc3rnX815uJeVBQLPWTjAUtJSP QxHzxpKfPrGjYXQ+z7+zNOZsutWOpdCsc5gPzLWJhv68ydwjngNpXNqHz2RLqALH EZse9lL9fx/9BRtzjaTld1rHbtsBuja/Tm8AVevgxzX8DeHVDmJpOHmpzMXsnmaq xOueIowbj5SQDERh0n1hWRip4VHD22f10zBZY2tZ+w/0ShIwMQnFjUJziR52YbkB DQRkHSpkAQgAmBtgDUDJZJU3TwnbQSw+ZsSprHazbDFi1URW0p0IR6in/Y3Q4hFi TQJqxFWet2JTrTf6Cmb80zMeaVxvTp0JOs4QAoR3/JkfqQwfJkaBzR/hxK2p6qPr aD98FKojPi18Y2QPt9v1naNrC5/QhOthYpgzQCL7kMIzrBlLIKDbO9cbIGw2RcIq 8XU/XnMRfrxeR7/AzmHecCpwglScwpQzzmw7GfFlTfcm3IegJOJtgr/BKkfNVaEJ k7ifVx+4f5746HagX9pwRGd87dVi7d6knK13HTJlWp6KSe6oiCPYbTpqElaxMGgw RRMo5gCel73qE/mUCXnG/XrgGWwoMcOrVQARAQABiQE2BBgBCgAgFiEEXcTXaKEX e2Sojwg3anTKasAZrcEFAmQdKmQCGwwACgkQanTKasAZrcEfCwf9GlieQHyxc3dc EeNMtBvC/0bKyUY2uQ6UoXI+l/M3tR2+PCPnCjTmFzPrCccxBgw1zJSPRK8gGt4I 4zgTe+7+ekATjV7nqGf6craEZYt8VqlU0YFb17rAwUV6GFPGYC9wB8ZdvGACm8q+ XQfbvw0as6US/+vKVqhMnpynAAv1jJBP4674s3K+jneRzfucELPtCXoV+LRG7oIv szcYGX4jZ/fEYLppJeSKurvqRGLVY2kReR/3AfxwHErkg7QdMZ7vW3qKxnAt/A8N tqIrEbRinlxH9IvTu+StHy0vkoy8xLmbStyXpfk9guD6h+PucF5pf8KYuOBCFT2Z d1qHPsprOg== =5go1 -----END PGP PUBLIC KEY BLOCK-----

ctrlcctrlv commented 1 year ago

Added. Still waiting for friend request. I'll encrypt a password to that key, if the account that adds me can decrypt it I'll call it. Also I'm wiling to accept this key for now but you should generate a quantum-safe key for long term use like mine.

basedgentoo commented 1 year ago

I'm having issues with discord 2fa. Will be about 5 minutes before I can get in.

basedgentoo commented 1 year ago

Ok, we're good. sending now.

ctrlcctrlv commented 1 year ago

No problem, it's a shit system. Are you on Rizon? I can send you a private Jitsi Web room.

ctrlcctrlv commented 1 year ago

I'm copypaste on Rizon, again, as always.

ctrlcctrlv commented 1 year ago

Oh OK.

KUZLOVER1237 commented 1 year ago

2005 : Kuzzy 2023 : Kuzzy 3023 : Kuzzy 5000 : Kuzzy 10000 : Kuzzy Forever : Kuzzy No matter what year it is Yuri Kuznetsov will always be a legend ❤️ ❤️

Repost this in 15 threads to show your support for Kuzzy ezgif-4-cf0caf6fc2

RealAngeleno commented 1 year ago

A Kolyma-maintained Vichan would not be a bad thing. You can trust Kolyma with it.

(To prevent any conflicts of interests in this statement, I do own the soyjak wiki. I don't work for Kolyma or anything, but they truly are great people)

Syerek commented 1 year ago

Do not allow the words of one person make you decide your opinion on another. Kolyma has done a lot of positive work for various imageboards and has handled many issues (illegal content, issues in coding, prohibitively expensive server hosting) that has plagued these communities for ages. Kolyma has dived headfirst into places others refuse to go, and saved many of these communities from extinction by the hands of outside forces. You don't need to immediately take my word or someone elses for fact however, but I feel a conversation with kuz or the vidlii owner would do everyone some good to clear up any misunderstandings.

Jvrtychud commented 1 year ago

Kolyma sucks. Kuz has leaked peoples IPs for criticizing him in the past. He basically never keeps his promises and his jannies always ban people for no reason Also Angeleno is lying. He takes orders from kolyma and is an employee for them more or less https://soyjak.wiki/User_talk:Angeleno#Deletion_log

gemeraldenjoyer commented 1 year ago

Kuz has leaked peoples IPs for criticizing him in the past.

gem

ctrlcctrlv commented 1 year ago

@basedgentoo is maintainer. They'll push their email to the README momentarily. I'll let them close this issue as they see fit, and am taking vichan repo off of my notifications. Thanks for answering my call to action friends.

basedgentoo commented 1 year ago

So as of today I will be taking over as maintainer for this project.

I just want to state that Kolyma, according to Fred, is completely lying about any vulnerability in vichan. If you have a reproducible critical bug, please demonstrate it to me in private and we can discuss how to handle it. So far it seems like the people from soyjak.party were just lying to try to make it seem like their closed source software was superior. But at least according to Fred, there was zero communication about this stuff with him. I don't know the concrete truth in this, however. For what it's worth, Fred didn't even know Kolyma existed until today.

I will be updating the README to reflect this change. And if the people at soyjak.party would like to demonstrate their vichan exploits (which I personally doubt exist), please feel free to explain them.

Thank you.

ECHibiki commented 1 year ago

The exploits thing doesn't seem likely in my opinion.

KUZLOVER1237 commented 1 year ago

KUZ VICTORY gem

ctrlcctrlv commented 1 year ago

Just confirming I had not heard of KolymaNET until this thread. I see their owner wrote this on their website:

I had never heard of them before but cannot deny they have a large, popular, vichan-based website. So, what we will do is, to prevent this situation from recurring on the offchance @basedgentoo poofs for more than three months without contact the same way @h00j and others did, I will email kuz (but can't find his email on their website so he should email me today so I have it) and offer it before making similar moves as made today.

KUZLOVER1237 commented 1 year ago

Just confirming I had not heard of KolymaNET until this thread. I see their owner wrote this on their website: I had never heard of them before but cannot deny they have a large, popular, vichan-based website. So, what we will do is, to prevent this situation from recurring on the offchance @basedgentoo poofs for more than three months without contact the same way @h00j and others did, I will email kuz (but can't find his email on their website so he should email me today so I have it) and offer it before making similar moves as made today.

vichan-devel / vichan

(Old) (No longer true) The end of Vichan maintenance. (Vichan has reached END OF LIFE) #543