/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


(10.65 KB 215x212 logo.png)
Looking for feedback for 1.7 StephenLynx##8HkpNt 06/15/2016 (Wed) 13:21:33 [Preview] No. 4585
So far this is what I implemented for 1.7:

SFW threads are shown on both NSFW and SFW overboards instead of just the SFW overboard. Displaying them only on the SFW overboard was kind of punishing, since these boards were already going out of their way to filter NSFW content and being pushed out of the main overboard
Improved how the original filename link works, so it uses the download feature of links instead of relying on routing. So now you only have to click on the link to download the file with the original filename. Not only that, but now your browser will be able to use the cache of the file if you already have it
Now small animated PNG's are thumbnailed instead of being directly embedded to the pages
Added a global setting for maximum message length along with a label indicating what is the maximum message length allowed
Implemented textboards, allowing board owners to decide if their boards allow files at all or not
Put back extensions on uploaded files. Thumbnails remain extensionless though
Added total amount of files and their combined size to the global stats that can be displayed on the site's front-page
Added several missing pieces of information to the JSON version of pages
Now content deletion gives a feedback on how many threads and posts were deleted instead of just informing if the operation succeeded
Now board staff can use IP deletion too. Naturally only content from their boards are deleted when using this feature
Added narrow range bans. Until 1.6, you can only create range bans based on the first half of the ip (16 bits for ipv4 and 64bits for ipv6). Now you can create range bans that use 3/4ths of the ip, meaning that you can create range bans with less collateral damage
Made bans easier. Now if you don't provide an expiration or provide an invalid expiration for bans it will default to 5 years from the current date and global staff no longer have to fill a captcha for bans
Added a colored background for ids on posts. That was kind of a hack, since I had to hard-code the value for the style attribute on the back-end. But I think it's tolerable, so I'll see how it goes
Now animated gif thumbnails can be generated using ffmpeg instead of imagemagick. Some gifs had a serious performance issue and this was the best way to get around that. ffmpeg doesn't give the thumbnails the quality imagemagick does, but it was a rather clean solution and it didn't add any new dependencies, so I went with that

Plus a few bug and edge case fixes here and there.

So now I am after feedback. Given what I already added to 1.7, what do you want to see implemented? I have already scheduled 1.7 release to november, with the spec lock happening on october, so there's plenty of time to think about what else could be improved.


Anonymous 06/15/2016 (Wed) 14:43:14 [Preview] No. 4586 del
1. Change the way user deletion works at least for OP. OP as a user should be able to delete his own post but shouldn't be able do delete others' posts. Simple thing like "USER DELETED HIS POST" would suffice.

2. Provide users with ability to loop playback of playable media files.

3. Have the option for users (or at least for BO) to automatically collapse long posts, just like in index of the board.

4. Stop writing wall-of-text changelogs in redtext.


Anonymous 06/15/2016 (Wed) 16:01:20 [Preview] No. 4587 del
>>4586
>4. Stop writing wall-of-text changelogs in redtext
this. and use bullet list, this enhance readability.

Did you checked the code with some tool?
https://github.com/jsverify/jsverify
https://www.w3.org/wiki/JavaScript_best_practices


Anonymous 06/15/2016 (Wed) 16:03:02 [Preview] No. 4588 del
>>4587
I use a lint and strict mode.


Anonymous 06/23/2016 (Thu) 11:55:10 [Preview] No. 4611 del
>Until 1.6, you can only create range bans based on the first half of the ip (16 bits for ipv4 and 64bits for ipv6). Now you can create range bans that use 3/4ths of the ip, meaning that you can create range bans with less collateral damage
[ ] I understood IPv6-ranges
[x] hurr durr~


Anonymous 06/23/2016 (Thu) 15:14:41 [Preview] No. 4612 del
>>4611
Ipv6 contains 128 bits.
Half of that equals to 64 bits.
What is wrong there?


Anonymous 06/29/2016 (Wed) 15:27:47 [Preview] No. 4656 del
Reading a manga on some board I remembered another neat thingy that on another site I had access through a user script (so I don't know if it's possible to implement here exactly as it were - but it doesn't have to be).

Anyway I'm speaking of expanding all images in thread.


Anonymous 06/29/2016 (Wed) 15:47:54 [Preview] No. 4657 del
>>4656
Front-end feature.


Anonymous 06/30/2016 (Thu) 11:15:22 [Preview] No. 4705 del
(370.12 KB 945x1066 lynx.png)
I suppose I should post this here as well if I want it to be useful. Sorry about the tone, and I see that at least one of the things I wrote no longer applies, but I keep getting more and more annoyed.


StephenLynx##8HkpNt 06/30/2016 (Thu) 14:50:46 [Preview] No. 4706 del
>>4705
Thanks for the feedback.

I have been considering changing the behavior for new thread pages for a while new. It wouldn't impact too much and would indeed make it for a better experience. After reading it and talking to balrog, I decided to go through and change it. Now the user only gets a response after the new thread page has been created.

However, for new posts, I really don't think it would be a good idea to give a response after generating the page.
Multiple people could be replying to a thread simultaneously. Plus it could be alleviated with javascript checking if the refresh is being made because the user made a new post and is expecting a new reply. Or it could even just add the post on the page before even getting it from the server, just with the data it knows it would go there. So when we talk about responsiveness for replies most of the gains would be on improving the front-end.



Small comments on some stuff there:
The "refresh every 5s on 404" is an endchan thing.
The selection thing is a front-end feature and endchan already implemented it.
The clarity of the elements at the bottom of the screen is a front-end issue. My front-end, for example, makes it clear when you have or when you don't have to use the captcha.
The feedback on deletion have been improved on 1.7, now it tells you how many threads and posts were deleted.



And some things are incorrect:
You don't have to use a link with a 3s redirect when closing reports. That can be done using javascript for your better convenience.
If the front-end isn't working properly and ends up making only the form button available, that is a front-end issue.

Post history is not implemented at all, even for global staff.

Infinity is not free software anymore at the moment.
https://github.com/ctrlcctrlv/infinity/issues/541#issuecomment-227951724 from the horse's mouth.

You can only report multiple posts on a single action if allowed by the global settings, and that setting is off by default.


Anything I didn't comment about its because I don't intend to change for one reason or another and I am not really looking for an argument here. Your feedback was good in general, but I just don't agree with some parts.


Anonymous 06/30/2016 (Thu) 18:12:50 [Preview] No. 4707 del
>>4706
Thank you for your reply.

>The "refresh every 5s on 404" is an endchan thing.
I know. I explicitly said so.

>The clarity of the elements at the bottom of the screen is a front-end issue. My front-end, for example, makes it clear when you have or when you don't have to use the captcha.
I know that too, but I still think it's bad design to show a captcha in cases where you don't have to use it.

>You don't have to use a link with a 3s redirect when closing reports. That can be done using javascript for your better convenience.
How? Is this something Endchan just doesn't have at the moment?

>You can only report multiple posts on a single action if allowed by the global settings, and that setting is off by default.
Good to know. I wonder why Endchan has it turned on.

>Infinity is not free software anymore at the moment.
>https://github.com/ctrlcctrlv/infinity/issues/541#issuecomment-227951724 from the horse's mouth.
That changed two days ago. There's a "public-site" branch now.


Anonymous 06/30/2016 (Thu) 19:51:00 [Preview] No. 4708 del
>>4707
>I know that too, but I still think it's bad design to show a captcha in cases where you don't have to use it.
The thing is, the captcha might be used always, because reporting always require a captcha.
It ended up very contrived because I have a goal to support users not using javascript.

The other option would be something like 8ch did, where it opens a new window with a captcha and stuff, I wanted to avoid that, specially because that makes it impossible to report multiple items at once, a feature that I wanted to have.


>How? Is this something Endchan just doesn't have at the moment?
Don't know, are going to have to poke odili about that. If you look at it, it seems to load the js file that handles that.
http://endchan.xyz/.static/reports.js


Anonymous 06/30/2016 (Thu) 19:58:10 [Preview] No. 4709 del
>>4708
It seems someone commented out the javascript button, so the script errors and halts when processing open reports.


Anonymous 06/30/2016 (Thu) 22:37:35 [Preview] No. 4712 del
really hoping for a filter system like 8ch


Anonymous 06/30/2016 (Thu) 22:45:56 [Preview] No. 4714 del
>>4712
Front-end feature.


Anonymous 06/30/2016 (Thu) 23:22:38 [Preview] No. 4715 del
>>4708
>The thing is, the captcha might be used always, because reporting always require a captcha.
True, but that's a consequence of putting everything in a single form. You should split it up. A lot of people who want to report something are just going to see the box and stop because it's confusing.

Reporting a post is a simple thing. It shouldn't be made complicated.


Anonymous 07/01/2016 (Fri) 01:59:15 [Preview] No. 4718 del
>>4715
>True, but that's a consequence of putting everything in a single form. You should split it up.
That is not possible if you are not using javascript.
It HAS to be a single form for everything or no deal.
And since a goal of mine is to support people not using javascript, I went with that route.


Anonymous 07/01/2016 (Fri) 09:49:37 [Preview] No. 4719 del
>>4718
Infinity manages to work without putting everything in a single form. You don't need to handle everything with forms.


Anonymous 07/01/2016 (Fri) 11:57:23 [Preview] No. 4720 del
>>4719
Infinity also requires you to use js to report posts.
Having a basic feature like that inaccessible for no-js users is unacceptable for me.


Anonymous 07/01/2016 (Fri) 17:52:11 [Preview] No. 4721 del
>>4720
You need javascript for reasons that are unrelated to the reporting workflow.


Anonymous 07/01/2016 (Fri) 18:02:18 [Preview] No. 4722 del
>>4721
I don't get what you said there.


Anonymous 07/02/2016 (Sat) 00:13:20 [Preview] No. 4723 del
>>4722
You need javascript to follow the link to the reporting page, and some weird results when reporting by directly visiting the URL make me suspect there's javascript involved there too, but those javascript requirements could be removed without really changing the way you report things. Nothing about the way the reports work depends on javascript to be possible, it just happens to use it.


Anonymous 07/02/2016 (Sat) 02:22:37 [Preview] No. 4724 del
>>4723
For that they would have to do the same that I do, use a single form and add the reporting elements at the bottom.

See chans running vanilla vichan, that's what they do.


The other option would be to have a link that opens a page to report one single post, like next does.
But then you are unable to report multiple posts, which is a feature that I want to have.


Anonymous 07/02/2016 (Sat) 16:12:07 [Preview] No. 4725 del
>>4724
I've never had a situation in which I wished people could report multiple posts at once, either as a user or as a moderator. If there are multiple rule-breaking posts in the thread and you're not sure if they'll be noticed you can say so in the report reason. But Lynxchan already forces moderators to view the context of the reported post, so that's unlikely.


Anonymous 07/02/2016 (Sat) 18:38:55 [Preview] No. 4726 del
>>4725
You can also report multiple threads at once, not just posts inside threads.

And as an user, I like to be able to report multiple items at once, it makes easier for me to contribute when reporting.



Top | Return | Catalog | Post a reply