>>1
can i get uhhh
> post box gets cleared when you close quick reply
> change clover icon on tab from green to red when you get (you)'d
> there are no (you)s

Currently on the list:
>download button for images
>make media thumbnails static

>>3
The (you) system is currently not implemented at all on LynxChan's backend, so it would require a lot of dev time unfortunately.
As for "post box gets cleared when you close quick reply", what do you mean by this?

>>4
Even though I said that thumbnail gifs were annoying because of no-fap and they were distracting, I didn't realize there was a hide option for the images. I don't know what the rest of the anons think of it, but a very good pro for thumbnail gifs, is that you can obverse several at the same time and know if it's worth expanding it and saving it. Usually one has to open every individual gif in order to evaluate it, and alot of the times the static image isn't very good to use to judge the gif's animation quality on. With gif thumbnails one can asses the animation quality instantly.

if you click to reply, then close the quick reply window, what was previously written stays there

>>6
Ah, I see the issue. That is pretty annoying.
I'll try to get around to fixing that, should be a somewhat simple fix hopefully.

Clover support for mobile posters.
And also /pol/ style thread post ids so we know when a shitposter is replying to their own posts to derail the thread.

>>8
Clover support is possible but requires a 4chan-like API and cooperation with the Clover dev(s) since they require hardcoded support. This is something you'd have to bring up with the LynxChan devs.

As for visible poster IDs, I am personally not a fan. This site will receive moderation, so it shouldn't be a huge issue in terms of post quality. I don't think i'd implement this unless there was a very large outcry.

>>8
Much as I love anonymity, I definitely appreciate the value in IDs.

>>8
IP-hopping is trivial so I don't think IDs would do much good.

>>4
>download button for images
Click on the filename after the dimensions.

>>12
Haha oh damn, I didn't even realize that was a feature of this frontend. Not super clear tho so I should probably still make that button but still.

>>13
That's not a FE feature, tho. It's a back-end one.

>>14
Very interesting, looks like you're right. Search turns up no real work on divposts container in the frontend.
Odd that that kind of formatting is handled on the backend but sure.

>>15
So nojs users can download files.

>>15
Also, of course I'm right, I wrote the damn thing.
:v

>>17
Oh damn, hey there Stephen!
Didn't expect to see you around here.

>>1
WHERE IS THE CATALOG
IT IS LITERALLY IMPOSSIBLE TO BROWSE ADEQUETLY WITHOUT A CATALOG
FUCK!!!

>>19
Are you serious?
Top right, the button that looks like a catalogue.

>>1
number of unique IP's would be nice.

>>22
Absolutely this

Individual threads don't work for Qutebrowser, meaning I can't scroll. It works find in the catalog and thread scroll.`

>>24
>Qutebrowser
Interesting. Can't say I'm at all familiar with that. As for the issue, is it a problem with scrolling on the board view (furchan.net/meta/) or in a thread (furchan.net/meta/res/1.html)?

>>25
thread (furchan.net/meta/res/1.html)

>>30
Interesting. From what I can see, the frontend just loads cells in dynamically using the same set of inputs whether in thread or board view. It almost treats posts and threads the exact same, even uses the same functions.
So if you can browse on the board view you should be able to browse on the thread view.

I honestly have no idea how Qutebrowser works or what it looks for to enable scrolling, maybe posts need to have an attached element with a numerical counter or something? That would require engine modifications, and we're already overdue for an engine update so I don't think that's a project I'd want to embark upon right now.

As for >>22 >>23
unique IPs will be in the new version of LynxChan I've heard, so that feature is coming once the site updates. It's just a matter of syncing up local changes and making sure the database doesn't suicide. This is something I may not get to for a while. For now this site is kind of on upkeep mode, though I'd obviously like for it to work for all users (Qutebrowser users included).
Eventually I'll have to transfer site hosting and when that happens, that's probably when I'll get back to this project and update everything.

I just want to get notified when I get a reply I'm on mobile or maybe a (you)

>>40
Yeah, unfortunately that'd be a backend tweak or the mother of all plugins, so it would require some serious dev time. I asked the developer that created the backend this site is running on about (you)s over irc once and he didn't seem to be a fan of the idea, so it seems unlikely. Believe me, if it were easy to implement I would have done so already.

On the plus side, mobile support is somewhat doable and when I get around to updating the engine I'll probably implement that at the same time with support for a certain chan browsing app, so that should help you out a lot.

>>44
Sweet glad to hear

>>1
The site lacks https/tls

>>184
I agree with this. This is important to implement. Also I assume as the site develops we will be getting other features as well such as custom CSS. Not a deal breaker but it would be nice to have.

>>1
if theres any way we can help either with donations, merch, telling others about this board, or even helping with lynxchan development please let us know

>>1
Do you know what would be really cool? A mascot.

>>191
But what kind of mascot accurately portrays the desire to bone animal women?

>>192
An animal woman, obviously.

>>184
seconded

something needs to be done to stop the bot posting it is very annoying

>>196
So, I can give a bit of a spread on what can be done there.
The posts appear to be botted, but they're coming in at rates indicative of a human poster making them. I can confirm this by looking at that big spam attack they did a couple weeks ago, it was entirely done on only two different IPs. Usually with an actual bot setup you'd use a different IP for each post, but as is it was really easy to clean up with a simple IP delete.

The solution to full bots is to implement captchas, which I can do very easily since it's built in the the LynxChan engine. But it would be annoying for regular users, and honestly the spam is pretty easy to clean up once a day or so (there's only ever a couple random posts here and there).

A filter wouldn't be effective because there's not much to filter when they're changing IPs and can just change their copypasta/image.

If you guys want to put on a captcha, go ahead and weigh in, but for now I'll just keep cleaning it up as it comes in.

>>196
>>197
Alright, I'm going to roll out captchas for now. We'll see if it does anything or if it's just an annoyance.

add dashchan support
https://im663.com/post/dashchan-setup-guide/

Alright, you all should be happy to know that I've finally gotten around to adding SSL support and mobile support.

As explained in >>199's guide, you have to install DashChan first
https://dashchan.en.uptodown.com/android

Then install the FurChan DashChan extension:
https://github.com/FurChan/DashChanFurChanAPK/raw/main/Dashchan-Extension-LynxChan-Generic-debug.apk

you should get on 2.5

>>202
Starting to think I should. Been getting random crashes ever since setting SSL to mandatory, which seem to have resolved by setting it to just enabled. Very weird behavior.

>>203
>setting SSL to mandatory
are you sure you need to

>>204
Nah, and I figured as much when I just set it back to enabled.
The workers are still crashing, but haven't hit any catastrophic ones so far after making that change. No idea what's causing it, logs seem pretty unhelpful.

how did you make node use the certificates

>>206
Just set the permissions on the key and certfiles such that node can access them. You think that's the issue?

>>207
idk ask stephen

>>208
That seems to be the plan. Thanks tho, bud.

>>200
>>199
Okay, update on mobile app - testing revealed that it wasn't loading boards for a while due to complaints about an "invalid certificate". After a little digging around in the source, I figured out that DashChan for some reason requires a fullchain SSL certificate to validate it. After reimplementing fullchain SSL (it was previously disabled for testing), it is now working again.