/operate/ - Endchan Operations

Let us know what's up

Posting mode: Reply

Check to confirm you're not a robot
Name
Email
Subject
Comment
Password
Drawing x size canvas
File(s)

Remember to follow the rules

Max file size: 350.00 MB

Max files: 5

Max message length: 4096

Manage Board | Moderate Thread

Return | Catalog | Bottom

Expand All Images


(223.12 KB 1536x1024 EURASIAN-LYNX-CUB.jpg)
Lynx Upgrade Anonymous Global volunteer 04/29/2020 (Wed) 19:12:46 [Preview] No. 11091
We are asking Anon's opinon again. This time about Lynxchan engine.
As you guys probably know, Endchan is running on a modified copy of an older version. We read several posts asking us for an update, so we are curious what advantages Anon sees in the newer ones, what features are better, what are missing now?

Thanks.


Anonymous 04/30/2020 (Thu) 03:25:31 [Preview] No.11092 del
>>11091
So what would happen if we migrated? Would the site be up? Would it only be for the [.]org domain of the site or would it be for all 3 at the same time? If it's only for the org domain then yeah so no more cloudflare here.

What exactly would there be to add? Everything works well as it is for now

Although we do get some "connection failure" messages sometimes. And sometimes the site goes really slow for some reason. But it's nothing major


Stephen Lynx 05/01/2020 (Fri) 00:53:26 [Preview] No.11095 del
I would argue that laymen are not the best people to judge technical aspects of software. Most users never come in touch with most of the features of a software of this type.
If you would ask me, the biggest changes since 1.7 were:
Offense records.
Bans per block bypass id.
Posting and file history.
Latest posts page.
More granular range bans.
Vastly improved caching. More performance, more reliability, more efficiency.
Better capcha options that are much harder to break.
A page with the latest replies in a thread instead of all replies.
Separate pages for reports and appeals.
More efficient RAM usage due to native functions.
Automatic full captcha for boards.
Thread merging.
Option to mass file deletion based on text matches.
More granular configuration as to who can bypass bans and blocks.
Archives.
Option to store files directly on disk instead of the db.
Added limits as to how many captchas users can request.
Specific board languages.
Warnings as a type of ban that is removed when the use sees it.
DNSBL integration.
Improved moderation form.
Added a redirect when threads are moved.
Added a redirect to the page the user tried to access but had to log in first.
Support for ipv6 for locations.
Individual file spoiling.
Templates can have optional elements that are filled from separate files.
Ability to ban reporters.
Ability to moderate directly from the report.
Added a page with information for media files.

But I may be biased.


Anonymous 05/01/2020 (Fri) 12:22:16 [Preview] No.11097 del
Sounds like fun. I think the real question is, what is there to lose? My one major annoyance with the site is uploading a file only to find I need block bypass after upload. I have mentioned this to Lynx before and he has commented that on later versions, this should be avoidable. However, how much of the endchans functionality have you implemented in JS? Can the latest version match that, because it surely would be a hassle to port that stuff over.
The one fun advancement as I see it is custom user CSS and JS. Filters are cool too but people have real fun sharing JS snippets and CSS tweaks on chans.
Again though, not worth it if we have too much to lose.

What ever you choose to do, we support.


odilitime Board owner 05/01/2020 (Fri) 23:59:14 [Preview] No.11098 del
>>11092
>So what would happen if we migrated?
Basically we'd have to deal with bugs, broken CSS and missing frontend features for a bit.

We lose the current frontend, potentially breaking all boards that have customized their CSS. And things would look different. We may lose a couple features that we had in the frontend.

I've already got a copy of the code all merged. We even had a few admins and testers find some bugs we've fixed already.

So the question is what are the pros and cons. Why disrupt the cozy? Is it worth it. Would it make our users happier.

>Would the site be up?
I estimated the down time to be less than an hour.

> Would it only be for the [.]org domain of the site or would it be for all 3 at the same time?
It's a backend upgrade, so all versions of the site would be down for this time.

>Although we do get some "connection failure" messages sometimes. And sometimes the site goes really slow for some reason. But it's nothing major
We think we figured out the slow issue and got it solved.

>>11095
> I would argue that laymen are not the best people to judge technical aspects of software.
We have judged the technical aspects of your software and not asking for that.

> Most users never come in touch with most of the features of a software of this type.
Yea, that's why we're asking.

> If you would ask me, the biggest changes since 1.7 were
Thank you for this list it's very helpful. And even I going over it and like damn that would be nice.

>>11097
> I think the real question is, what is there to lose?
Some of the frontend JS feature that aren't present in other LynxChans.

> Can the latest version match that, because it surely would be a hassle to port that stuff over.
Yea, they would initially be missing but we could add them back over time.

>My one major annoyance with the site is uploading a file only to find I need block bypass after upload. I have mentioned this to Lynx before and he has commented that on later versions, this should be avoidable.
>The one fun advancement as I see it is custom user CSS and JS. Filters are cool too but people have real fun sharing JS snippets and CSS tweaks on chans.
These can easily be add to the current version.


Anonymous 05/02/2020 (Sat) 06:15:10 [Preview] No.11100 del
Individual file removal


Anonymous 05/02/2020 (Sat) 06:17:25 [Preview] No.11101 del
>>11098
but only a few boards are active so custom css isn't that big of an issue and only /kc/ has it


Anonymous 05/02/2020 (Sat) 07:05:59 [Preview] No.11102 del
>>11101
And a couple of other boards. /kc/'s is just very noticable, others are more subtle.


StephenLynx 05/02/2020 (Sat) 13:32:13 [Preview] No.11106 del
>>11098
And even I going over it and like damn that would be nice.
Yeah, it's been a while since moderation tools have been the focus of development.


Anonymous 05/02/2020 (Sat) 15:38:42 [Preview] No.11107 del
(9.13 KB 225x225 684987498494.jpg)
>>11098
>We lose the current frontend, potentially breaking all boards that have customized their CSS. And things would look different. We may lose a couple features that we had in the frontend.

I don't know. Some people are already comfortable with the way things are. They did something similar in my other job with the software we used. People got pissed because of how hard things were to use compared to the old software they had.

>So the question is what are the pros and cons. Why disrupt the cozy? Is it worth it. Would it make our users happier.

Wellll we kinda had this happen before, almost a year ago. We migrated and were down for a while because there were more things to fix. We lost a lot of people from multiple boards after it happened. /v/ and /rus/ being the most notable boards being absent.

I dunno.

>I've already got a copy of the code all merged. We even had a few admins and testers find some bugs we've fixed already.

Do you have a virtual environment or production site where you test everything beforehand? Maybe making it near 100% "bug-free" before updating would be good

Most software updates in bigger companies get done during night shift since most people aren't up during that time, so that's another thing you can try depending on what you choose to do.

There's people from multiple timezones here, ausneets for example, so that's another thing to keep in mind. They wouldn't be able to post for a while


Anonymous 05/02/2020 (Sat) 15:42:54 [Preview] No.11108 del
>>11107
Another thought. Have you considered implementing changes slowly instead of all at once?

Maybe update one thing at a time, see if it breaks anything, and then revert it if it breaks anything? Basically agile development? I don't know. Whatever works best


Stephen Lynx 05/03/2020 (Sun) 11:23:35 [Preview] No.11115 del
I would also point out that penumbra has much better mobile support than what you have here.


Anonymous 05/06/2020 (Wed) 17:58:16 [Preview] No.11119 del
>wanting phone fags


Anonymous 05/19/2020 (Tue) 12:53:17 [Preview] No.11149 del
i just want da new mod tools


Anonymous 05/20/2020 (Wed) 00:36:08 [Preview] No.11152 del
(105.21 KB 633x1130 1705050.png)
>>11091
Out of these >>11095, I pick in this order of preference:

Archives, individual file spoiling, bans per block bypass id, more performance, more reliability, more efficiency (this site still suffers those periods of 500 errors to an extent) ; and warnings as a type of ban that is removed when the user sees it.


Anonymous 05/28/2020 (Thu) 21:19:37 [Preview] No.11185 del
i just would like the new mod tools and i think there's new/different captcha


Anonymous 06/03/2020 (Wed) 11:32:48 [Preview] No.11195 del
>>11149
I would like a mod that works without the captcha


Anonymous 06/03/2020 (Wed) 11:34:55 [Preview] No.11196 del
>>11095
All those features sound lovely.



Top | Return | Catalog | Post a reply