This is a thread for all of those little features on 4chan, addons, or wherever else that you miss and would like to have here.
/qa/ - Questions and Answers
Keeping the community together by giving you a voice
176 replies | 53 files | 65 UUIDs | Page 1
76 replies and 16 files omitted.
>>9522
Sorry you got that error. I try to do the updates as fast as I can to prevent anyone notice. But sometimes I fall short of that goal.
Sorry you got that error. I try to do the updates as fast as I can to prevent anyone notice. But sometimes I fall short of that goal.
This site is borderline perfect, as other anons have said it needs a decent thread watcher, if that was implemented then I'd happily make this my home board. Also massive thanks to staff and anons of mlpol for accepting us refugees, it's comfy here. The features on this site such as, lack of cuck timer+captcha and video support with audio are a real eye opener as to how shit 4chan was.
>>9523
It was hardly prolonged, barely a blip. You can never, ever save every packet. You aren't #Deca
It was hardly prolonged, barely a blip. You can never, ever save every packet. You aren't #Deca
>>9530
Very much looking forward to this. For me, thread watcher + dynamic post "read" status based on scrolling are the two big features that would basically make this site perfect.
With some luck, you might even be able to lift some of the frontend javascript directly from 4chanx. It's even MIT licensed.
Very much looking forward to this. For me, thread watcher + dynamic post "read" status based on scrolling are the two big features that would basically make this site perfect.
With some luck, you might even be able to lift some of the frontend javascript directly from 4chanx. It's even MIT licensed.
Just to have this down in a post.
Caution is needed, to almost preemptively gatekeep against knowingly and unknowingly malicious and duplicious actors.
More users in general means bigger more worthwhile target.
Purity spirals are counterproductive, active defense is great.
I recommend considering old school tar traps, there's going to be crawlers and pseudo-ai and something strangely better roaming soon. Ignoring robots text file to extract and harvest whatever it is.
[YouTube] Digital Tar Pits - How to Fight Back Against A.I.![]()
[YouTube] The Art Of Poison-Pilling Music Files![]()
[YouTube] GPT-4chan: This is the worst AI ever![]()
[YouTube] Strange Tech from the Quantum Realm!![]()
As an example but not the point.
Toppling powers and principalities through peace and love and friendship.
The best poison isn't poison, but is honey to people and doom to microbes.
Feed whatever it is, the Holy Bible, select choice cuts of shit posting, deep fryed images of ponies and Christ. A neverending buffet.
Hard times are coming. When I'm not sure, but it is coming.
Caution is needed, to almost preemptively gatekeep against knowingly and unknowingly malicious and duplicious actors.
More users in general means bigger more worthwhile target.
Purity spirals are counterproductive, active defense is great.
I recommend considering old school tar traps, there's going to be crawlers and pseudo-ai and something strangely better roaming soon. Ignoring robots text file to extract and harvest whatever it is.
[YouTube] Digital Tar Pits - How to Fight Back Against A.I.
[YouTube] The Art Of Poison-Pilling Music Files
[YouTube] GPT-4chan: This is the worst AI ever
[YouTube] Strange Tech from the Quantum Realm!
As an example but not the point.
Toppling powers and principalities through peace and love and friendship.
The best poison isn't poison, but is honey to people and doom to microbes.
Feed whatever it is, the Holy Bible, select choice cuts of shit posting, deep fryed images of ponies and Christ. A neverending buffet.
Hard times are coming. When I'm not sure, but it is coming.
>>9533
Your caution is appreciated, but we're well aware. It was one thing when we were fucking nobody - a joke, a dying vestige of a one-time funny-haha - but now we're on radars, and there's lolz to be had from causing chaos and drama. Most of staff is Gen X, and are under no illusions of what is likely to transpire at some point.
Your caution is appreciated, but we're well aware. It was one thing when we were fucking nobody - a joke, a dying vestige of a one-time funny-haha - but now we're on radars, and there's lolz to be had from causing chaos and drama. Most of staff is Gen X, and are under no illusions of what is likely to transpire at some point.
>>9360
>>9364
>>9518
>pdf
I can honestly say with full confidence that our website code was more secure when I first turned the website on drunk and disorderly (thanks pupper for making actually good code) than 4chan was last week, constant security updates were always number 1, in fact I accidentally crashed the server the first week because I wanted to keep a script running for the security updates
we secure the server itself against any ssh, we keep the server code updated, there is a solid separation between our own communications and the server software, and we store NO user data, your ip addresses are on our server for 1 nanosecond before being garbled into a non-reversable encrypted bit of nonsense, the best we can know (for moderation purposes) is that two posts were made by the same person. And all the posts are backed up so they couldn't even just delete everything and leave us in shambles.
even if someone managed to somehow using voodoo magic break into the server the worst thing they could do is momentarily piss us off.
>>9364
>>9518
I can honestly say with full confidence that our website code was more secure when I first turned the website on drunk and disorderly (thanks pupper for making actually good code) than 4chan was last week, constant security updates were always number 1, in fact I accidentally crashed the server the first week because I wanted to keep a script running for the security updates
we secure the server itself against any ssh, we keep the server code updated, there is a solid separation between our own communications and the server software, and we store NO user data, your ip addresses are on our server for 1 nanosecond before being garbled into a non-reversable encrypted bit of nonsense, the best we can know (for moderation purposes) is that two posts were made by the same person. And all the posts are backed up so they couldn't even just delete everything and leave us in shambles.
even if someone managed to somehow using voodoo magic break into the server the worst thing they could do is momentarily piss us off.
Don't know if it has already been mentioned, but for spoilered images, the original filename doesn't show when unspoilering the image (you can still save it with the original filename though).
Can I request the G5 icons to be added to : ?
Can you make a feature where you can move tangents or off topic discussions to the appropriate threads if they exist?
>>9645
Testing it and there's some kind of bug.
If I hold and drag to select, it works.
If I double click on the text to select a single word, it works.
If I triple click on the text to select all of it, it doesn't work.
Testing it and there's some kind of bug.
If I hold and drag to select, it works.
If I double click on the text to select a single word, it works.
If I triple click on the text to select all of it, it doesn't work.
1745360130.mp4 (598.1 KB, Resolution:1064x602 Length:00:00:17, firefox_8ulwLPwpco.mp4) [play once] [loop]
>>9648
Thanks for this, anon. I thought I was going insane with it working half the time and not working the other half.
Thanks for this, anon. I thought I was going insane with it working half the time and not working the other half.
Quickreply pup-up window can only extend horizontally.
Please make it extendable vertically and diagonally too.
Please make it extendable vertically and diagonally too.
>>9715
This has been getting me too since I'm used to scaling the quickreply from the actual input portion. The problem is we're using this site's implementation incorrectly. You need to go to the ENTIRE quickreply box's corner.
This has been getting me too since I'm used to scaling the quickreply from the actual input portion. The problem is we're using this site's implementation incorrectly. You need to go to the ENTIRE quickreply box's corner.
Created a Thread Watcher.
It is first iteration so if you see any bugs or features you would like let me know.
You can Watch a thread by clicking the [Add to Thread Watcher] link or by using keyboard shortcut Shift+W.
It shows:
>(Unread posts) [Title/Text] (page number) and /board/
It is first iteration so if you see any bugs or features you would like let me know.
You can Watch a thread by clicking the [Add to Thread Watcher] link or by using keyboard shortcut Shift+W.
It shows:
>(Unread posts) [Title/Text] (page number) and /board/
>>9227
>>9233
>>9531
Made first attempt at thread watcher. Let me know if you see things missing, or features you would like me to cange/improve.
>>9723
I might also mention that if you got the "[TEXT MISSING]" for thread, it was a small bug on first upload that I fixed. To get it to work just remove using [Remove Thread from Thread Watch] and add it again.
>>9233
>>9531
Made first attempt at thread watcher. Let me know if you see things missing, or features you would like me to cange/improve.
>>9723
I might also mention that if you got the "[TEXT MISSING]" for thread, it was a small bug on first upload that I fixed. To get it to work just remove using [Remove Thread from Thread Watch] and add it again.
>>9724
Fucking based.
So far looking great. Obviously some small things are missing but I assume you probably have plans to add more so far so I'm not gonna blurt out a todo list immediately, and this is already a huge help. One thing I will ask though, is how difficult would it be to have a setting to auto-watch threads on reply?
Fucking based.
So far looking great. Obviously some small things are missing but I assume you probably have plans to add more so far so I'm not gonna blurt out a todo list immediately, and this is already a huge help. One thing I will ask though, is how difficult would it be to have a setting to auto-watch threads on reply?
>>9726
>so I'm not gonna blurt out a todo list immediately, and this is already a huge help
Feel free to blurt them out, Any pointers to what is desired will be a huge help in coding. This way I don't have to speculate what people wants and can instead try to do the best I can to implement what is desired.
>how difficult would it be to have a setting to auto-watch threads on reply
It should be possible to do that.
The current thread watcher is a work in progress. So info on styling and what info and functionality that is desired will be a great help.
>so I'm not gonna blurt out a todo list immediately, and this is already a huge help
Feel free to blurt them out, Any pointers to what is desired will be a huge help in coding. This way I don't have to speculate what people wants and can instead try to do the best I can to implement what is desired.
>how difficult would it be to have a setting to auto-watch threads on reply
It should be possible to do that.
The current thread watcher is a work in progress. So info on styling and what info and functionality that is desired will be a great help.
>>9727
>Feel free to blurt them out,
Alright sure! Here's a wishlist of what I'd love to see in the finished product, then:
>as already mentioned, auto-watch on reply (with an option?)
>similarly, auto-watch your own thread when you make one
>a minimise button for the watcher popup
>maybe make it draggable like the quick reply window? I don't super mind but it'd be nice to have the ability
>periodic auto-refresh (like every 10 or 30 or 60 seconds or so)
>I haven't tested if this already works, but (You) notifications, if enabled in the settings, should then work for any watched threads when the watcher updates them, even if they aren't open in any other tabs (but! beware of duplicate notifications if the thread IS also independently open in a tab)
>a better highlight on (You)s - I like that threads on the last few pages are already red, so I'm not sure how to best highlight that, but maybe maybe the reply count deep red and bold for example? ideally you'd also be able to tell if a thread is on page 10 AND has a (You) so I'm not sure, might need some experimenting
>speaking of last page highlights, I'm not sure if p9 needs highlighting, but p8 definitely doesn't IMO (even 4chanx didn't highlight it)
>also a "you have unread (You)s" icon in the modal titlebar itself, for when it's minimised/collapsed
>also, I would be ecstatic if we had a closeable threadwatcher with (You) alerts still working, that means:
>>>that same notification icon also being in the sticky header with the boardlist, next to the "[ Options ]" button
>>>a close button on the watcher window, and a way to reopen it
>>>clicking the (You) notification in the boardlist header would either open the entire thread watcher window if it's closed, or open a mini-view just listing the threads that have unread (You)s
>a "delete thread" (i.e. unwatch it) button directly in the thread watcher, so you don't have to open the thread and click remove
>a dynamically synced watcher so that adding a thread in one tab also shows up in the watcher modal in another tab without having to reload the page, and also reading the posts in a thread marks it as read in the watcher and is reflected in all open tabs
>for the future, I haven't tested it yet but I assume because it's in alpha you probably don't have it yet, mentioning just in case - archived threads should be un-highlighted (shown faded) and should also get automatically pruned/unwatched after a few days or so (but not immediately so you can look back and check at any threads you were following that got archived) (maybe the auto-delete period can also be configurable in settings and disable-able for those who want to only manually clean their watchers)
I think that's about all I'd want out of a perfect feature-complete watcher. Obviously I don't expect all of this to be implemented immediately, I just tried to give you as comprehensive a list as I could to hopefully guide development.
Styling-wise, the main question is how to display (You)s properly without interfering with the p9/10 highlighting, otherwise it's already looking great. Maybe for p9/10, only the page number should be red ad maybe experiment with making the thread italic, and for an unread (You) the entire thread should be red (and bold because unread posts)?
Hmm, really scrutinising it, also the board title at the end can be hard to read if considered important, maybe making it at the start of the name and constant width could make it more table-like and readable, so e.g.
> (0) /poner/ - We are so BACK (p1)
> (0) /qa/ - Quality of Life Improvements (p1)
but I'm not entirely certain about that.
>Feel free to blurt them out,
Alright sure! Here's a wishlist of what I'd love to see in the finished product, then:
>as already mentioned, auto-watch on reply (with an option?)
>similarly, auto-watch your own thread when you make one
>a minimise button for the watcher popup
>maybe make it draggable like the quick reply window? I don't super mind but it'd be nice to have the ability
>periodic auto-refresh (like every 10 or 30 or 60 seconds or so)
>I haven't tested if this already works, but (You) notifications, if enabled in the settings, should then work for any watched threads when the watcher updates them, even if they aren't open in any other tabs (but! beware of duplicate notifications if the thread IS also independently open in a tab)
>a better highlight on (You)s - I like that threads on the last few pages are already red, so I'm not sure how to best highlight that, but maybe maybe the reply count deep red and bold for example? ideally you'd also be able to tell if a thread is on page 10 AND has a (You) so I'm not sure, might need some experimenting
>speaking of last page highlights, I'm not sure if p9 needs highlighting, but p8 definitely doesn't IMO (even 4chanx didn't highlight it)
>also a "you have unread (You)s" icon in the modal titlebar itself, for when it's minimised/collapsed
>also, I would be ecstatic if we had a closeable threadwatcher with (You) alerts still working, that means:
>>>that same notification icon also being in the sticky header with the boardlist, next to the "[ Options ]" button
>>>a close button on the watcher window, and a way to reopen it
>>>clicking the (You) notification in the boardlist header would either open the entire thread watcher window if it's closed, or open a mini-view just listing the threads that have unread (You)s
>a "delete thread" (i.e. unwatch it) button directly in the thread watcher, so you don't have to open the thread and click remove
>a dynamically synced watcher so that adding a thread in one tab also shows up in the watcher modal in another tab without having to reload the page, and also reading the posts in a thread marks it as read in the watcher and is reflected in all open tabs
>for the future, I haven't tested it yet but I assume because it's in alpha you probably don't have it yet, mentioning just in case - archived threads should be un-highlighted (shown faded) and should also get automatically pruned/unwatched after a few days or so (but not immediately so you can look back and check at any threads you were following that got archived) (maybe the auto-delete period can also be configurable in settings and disable-able for those who want to only manually clean their watchers)
I think that's about all I'd want out of a perfect feature-complete watcher. Obviously I don't expect all of this to be implemented immediately, I just tried to give you as comprehensive a list as I could to hopefully guide development.
Styling-wise, the main question is how to display (You)s properly without interfering with the p9/10 highlighting, otherwise it's already looking great. Maybe for p9/10, only the page number should be red ad maybe experiment with making the thread italic, and for an unread (You) the entire thread should be red (and bold because unread posts)?
Hmm, really scrutinising it, also the board title at the end can be hard to read if considered important, maybe making it at the start of the name and constant width could make it more table-like and readable, so e.g.
> (0) /poner/ - We are so BACK (p1)
> (0) /qa/ - Quality of Life Improvements (p1)
but I'm not entirely certain about that.
>>9724
Incredible turnaround fren!
Glad that my detailing of 4x functions helped out.
I am impressed that you got it out this fast while 8moe admins got asked about this a week ago and it's still broken with no sign of clear skies anytime soon. In fairness, they're getting butfucked by glowniggers right now so they have their hands tied.
It's a little easy to miss as a link at the top, but I'm used to it being a button or key so I can adjust quick. I'll be sure to spread the goodnews and report back if there's any bugs. Am I to assume right that it doesn't auto-update and you have to refresh manually?
Incredible turnaround fren!
Glad that my detailing of 4x functions helped out.
I am impressed that you got it out this fast while 8moe admins got asked about this a week ago and it's still broken with no sign of clear skies anytime soon. In fairness, they're getting butfucked by glowniggers right now so they have their hands tied.
It's a little easy to miss as a link at the top, but I'm used to it being a button or key so I can adjust quick. I'll be sure to spread the goodnews and report back if there's any bugs. Am I to assume right that it doesn't auto-update and you have to refresh manually?
>>9728
Pretty extensive, and very much 4chanX again. I was going to suggest things in chunks until we get closer to the old home thread watcher. But if Pupper want's to absorb all the autism at once, then it's certainly right there for him to go over.
Pretty extensive, and very much 4chanX again. I was going to suggest things in chunks until we get closer to the old home thread watcher. But if Pupper want's to absorb all the autism at once, then it's certainly right there for him to go over.
>>9732
>Am I to assume right that it doesn't auto-update and you have to refresh manually?
That is correct. It updates when you load a page and when you click the update button. To clear the "Unread" counter you have to update it on the thread that has unread posts on it.
If you have any suggestions or requests for features or changes please let me know and I will do my best to implment it.
>Am I to assume right that it doesn't auto-update and you have to refresh manually?
That is correct. It updates when you load a page and when you click the update button. To clear the "Unread" counter you have to update it on the thread that has unread posts on it.
If you have any suggestions or requests for features or changes please let me know and I will do my best to implment it.
>>9733
>But if Pupper want's to absorb all the autism at once, then it's certainly right there for him to go over.
Always welcome. I might ask for more suggestions after each iteration, and would welcome suggestions restated if they were not implemented but desired. This way I don't have to keep track of what I missed and hopefully can faster finetune features for this and other stuff.
I am not the best at writing to-do lists they tend to end up as walls of text I loose track of.
>But if Pupper want's to absorb all the autism at once, then it's certainly right there for him to go over.
Always welcome. I might ask for more suggestions after each iteration, and would welcome suggestions restated if they were not implemented but desired. This way I don't have to keep track of what I missed and hopefully can faster finetune features for this and other stuff.
I am not the best at writing to-do lists they tend to end up as walls of text I loose track of.
>>9734
Understood.
While you're here, what's the deal with with the double filenames with the huge string being the biggest one? Is it necessary or can it be trimmed down to just normal filenames. Which this guy brought up but didn't really clarify >>9228
It looks like it displays a hash on the first filename of the thumbnail hosted on the server, and then the real filename that was uploaded. Which is just "spoilered" when a file is under a spoiler
It would probably be best if the hashname was hidden or significantly sized down, unless there's a reason for it
Understood.
While you're here, what's the deal with with the double filenames with the huge string being the biggest one? Is it necessary or can it be trimmed down to just normal filenames. Which this guy brought up but didn't really clarify >>9228
It looks like it displays a hash on the first filename of the thumbnail hosted on the server, and then the real filename that was uploaded. Which is just "spoilered" when a file is under a spoiler
It would probably be best if the hashname was hidden or significantly sized down, unless there's a reason for it
>>9740
Argh, some good some bad. It looks better on the eyes but it would be ideal if the full filename was mostly visible and the larger one, not truncating each so heavily. Or just hiding the hash by defualt
The suggestion stems from making an effort to preserve the culture around naming files manually, which can each have its own commentary or meme which enhances it being just an image.
See when the full filenames can be meme-y and very /mlp/, but hovering over it just makes more effort that I don't think people would bother with.
>>>/poner/6839 →
>>>/poner/4754 →
>>>/poner/6688 →
Argh, some good some bad. It looks better on the eyes but it would be ideal if the full filename was mostly visible and the larger one, not truncating each so heavily. Or just hiding the hash by defualt
The suggestion stems from making an effort to preserve the culture around naming files manually, which can each have its own commentary or meme which enhances it being just an image.
See when the full filenames can be meme-y and very /mlp/, but hovering over it just makes more effort that I don't think people would bother with.
>>>/poner/6839 →
>>>/poner/4754 →
>>>/poner/6688 →
>>9745
>Argh, some good some bad. It looks better on the eyes but it would be ideal if the full filename was mostly visible and the larger one, not truncating each so heavily. Or just hiding the hash by defualt
>See when the full filenames can be meme-y and very /mlp/, but hovering over it just makes more effort that I don't think people would bother with.
I will do some tinkering and tweaking to make it better. And I will have a more functional and better implementation tomorrow. I might have rushed this tweak a bit, but good to get feedback on so I can make it better.
>Argh, some good some bad. It looks better on the eyes but it would be ideal if the full filename was mostly visible and the larger one, not truncating each so heavily. Or just hiding the hash by defualt
>See when the full filenames can be meme-y and very /mlp/, but hovering over it just makes more effort that I don't think people would bother with.
I will do some tinkering and tweaking to make it better. And I will have a more functional and better implementation tomorrow. I might have rushed this tweak a bit, but good to get feedback on so I can make it better.
>>9749
Made a small update to the css so the original names are shown (as long as they don't go over three lines on multi file posts).
Made a small update to the css so the original names are shown (as long as they don't go over three lines on multi file posts).
>>9750
I think it's an improvement over truncating everything, I would still like to axe the hash being displayed.
From a UI it's visually cluttered and the filename is easy to miss since it's so very tiny. Sandwhiched between the bigger hash and the reverse lookup tools. Maybe have the other stuff as hover-over to display the tool/hashes?
Comparing to 8moe and End the UI is clean, and it looks like moe do use hover to full filename so maybe its workable.
I think it's an improvement over truncating everything, I would still like to axe the hash being displayed.
From a UI it's visually cluttered and the filename is easy to miss since it's so very tiny. Sandwhiched between the bigger hash and the reverse lookup tools. Maybe have the other stuff as hover-over to display the tool/hashes?
Comparing to 8moe and End the UI is clean, and it looks like moe do use hover to full filename so maybe its workable.
>>9737
Have you considered something like trello? Just shove the suggestions everyone gives into it, and when you wanna work on something, check the backlog and pick something out.
That's if you wanna keep better track of course.
Have you considered something like trello? Just shove the suggestions everyone gives into it, and when you wanna work on something, check the backlog and pick something out.
That's if you wanna keep better track of course.
Add an option to disable the automatic scrolling when an image is un-maximized. Its such a terrible anti-feature and every altchan seems to do it.
Added function so you should automatically scroll to the last post you read upon load of a thread. It might need some fine tuning, so let me know of any improvements you would like to see.
>>9762
Oh shit MASSIVE
I haven't tested yet right this moment on whether this also implements per-post "unread post" decrementing (vs. having to scroll down to the bottom to mark the entire thread as read simultaneously), but the actual scrolling to last position works perfectly and is a huge gamechanger in how easy it is to go back and catch up to threads (and goes hoof-in-hoof with the thread watcher letting me close a bunch of tabs and re-open them when I see new posts)
Oh shit MASSIVE
I haven't tested yet right this moment on whether this also implements per-post "unread post" decrementing (vs. having to scroll down to the bottom to mark the entire thread as read simultaneously), but the actual scrolling to last position works perfectly and is a huge gamechanger in how easy it is to go back and catch up to threads (and goes hoof-in-hoof with the thread watcher letting me close a bunch of tabs and re-open them when I see new posts)
>>9752
Tried to clean up the look a bit adding an 🖫# for download of image as normal making the original file name a bit mor prominent, but might need a little more tweaking.
Tried to clean up the look a bit adding an 🖫# for download of image as normal making the original file name a bit mor prominent, but might need a little more tweaking.
>>9765
I am open to suggestions. Nothing it set in stone, and I am just testing out a different view setting to try to make it cleaner.
I am open to suggestions. Nothing it set in stone, and I am just testing out a different view setting to try to make it cleaner.
1745511293_1.jpg (3.9 MB, 3654x2511, 1ebd86cff6fdb75080fae359271542d2782905c75cb917d12d2a5fdd27a47785.jpg)
>>9772
Great that the giant hash has been mostly cleaned up since that was the giant fucking file being moaned about, but if that's what it was I think you could just add it like [hash#] and satisfy people who don't like the unicode. It would still be less messy than truncating the string.
I am pretty neutral about it since I dont think I would ever use the hash file over the filename file.
>>9772
I am not neutral about this though, I'd like to see is the filename size/info on the same row as the hash, but right now it's inconsistent on how it's stacked, different sizes, and sets off my autism. Pic2 vs Pic3, Pic4 vs Pic5
Great that the giant hash has been mostly cleaned up since that was the giant fucking file being moaned about, but if that's what it was I think you could just add it like [hash#] and satisfy people who don't like the unicode. It would still be less messy than truncating the string.
I am pretty neutral about it since I dont think I would ever use the hash file over the filename file.
>>9772
I am not neutral about this though, I'd like to see is the filename size/info on the same row as the hash, but right now it's inconsistent on how it's stacked, different sizes, and sets off my autism. Pic2 vs Pic3, Pic4 vs Pic5
dev plz fix
>>9766
>>9772
Question: what is the purpose of that first hash-link? Why can't the original filename be in that spot?
I see that the original filename, right now, links to a download by original filename, while the hash links to a download by the hash/site filename. I suggest that either
>a: the original filename becomes the default download, with a "hash filename" button next to it or something; or
>b: the current hash download link is still replaced with the actual filename; and add a button to download with original filename next to it (e.g. replace the tiny font text that currently has the original filename with just "(orig)").
Here's a quick devtools mockup of what I mean for option b - both of the links go to the same places they do now (i.e. clicking on "image.png" saves a file called "EA2F....png", and clicking on "(orig)" saves a file called image.png).
Arguably I also find the hash filenames to be pretty useless to save by, but doing it this way will preserve mlpol functionality and even the way 4chan also did it (except 4chan did not have a convenient original-filename download button at all).
>>9772
Question: what is the purpose of that first hash-link? Why can't the original filename be in that spot?
I see that the original filename, right now, links to a download by original filename, while the hash links to a download by the hash/site filename. I suggest that either
>a: the original filename becomes the default download, with a "hash filename" button next to it or something; or
>b: the current hash download link is still replaced with the actual filename; and add a button to download with original filename next to it (e.g. replace the tiny font text that currently has the original filename with just "(orig)").
Here's a quick devtools mockup of what I mean for option b - both of the links go to the same places they do now (i.e. clicking on "image.png" saves a file called "EA2F....png", and clicking on "(orig)" saves a file called image.png).
Arguably I also find the hash filenames to be pretty useless to save by, but doing it this way will preserve mlpol functionality and even the way 4chan also did it (except 4chan did not have a convenient original-filename download button at all).
>>9774
Yes I messed up in one of the css files, but should have been fixed already. Try reload page. If it still is messed up let me know and I will look more into it.
Yes I messed up in one of the css files, but should have been fixed already. Try reload page. If it still is messed up let me know and I will look more into it.
>>9777
Thank you, and you're good you're insanely responsive. The site is already good quality and we're flooding you with an endless amount of small items to fix-up everywhere, and the motivation with which you're tackling improvement is not going unappreciated.
Thank you, and you're good you're insanely responsive. The site is already good quality and we're flooding you with an endless amount of small items to fix-up everywhere, and the motivation with which you're tackling improvement is not going unappreciated.
is there a option to temporarily hide thread watcher? The thing makes it difficult to long posts
>>9775
>Question: what is the purpose of that first hash-link? Why can't the original filename be in that spot?
I can set the original filename in that spot, but sometimes the original filename can be really long. I could do an similar to "save as original" and have "save as timestamp" instead of the hash. But I will do some testing. As it has been hashes for so long some might prefer that as you know if you have saved that image before preventing duplicates, but also some prefer the timeline of saves.
>>9775
>>9773
I will try to do some thinking and mockup and testing to see if I can clean up the file info part.
>Question: what is the purpose of that first hash-link? Why can't the original filename be in that spot?
I can set the original filename in that spot, but sometimes the original filename can be really long. I could do an similar to "save as original" and have "save as timestamp" instead of the hash. But I will do some testing. As it has been hashes for so long some might prefer that as you know if you have saved that image before preventing duplicates, but also some prefer the timeline of saves.
>>9775
>>9773
I will try to do some thinking and mockup and testing to see if I can clean up the file info part.
>>9783
I saw it as soon as I came back to check, it looks like it works well. I dont think that part needs anything changes like completely hiding it ala 4chanx and I'm fine with that function as is it now.
For the thread watcher my first feedback I think the glowing red warning is set too low where it is right now (5). Page 9-10 is the typical one as the glowing red purpose for page info was so you could save a thread from getting archived.
BUT this should come with a caveot, have a rule against excessive necrobumps as trolls abused on /mlp/. /mlp/ had punished necrobumping with bans at one point but they stopped giving a damn and the board suffered for it as trolls quickly adapted to update their new slide-strategies bumping all their page9-10 threads around the same time and just leaving it to rot like stale bread.
I saw it as soon as I came back to check, it looks like it works well. I dont think that part needs anything changes like completely hiding it ala 4chanx and I'm fine with that function as is it now.
For the thread watcher my first feedback I think the glowing red warning is set too low where it is right now (5). Page 9-10 is the typical one as the glowing red purpose for page info was so you could save a thread from getting archived.
BUT this should come with a caveot, have a rule against excessive necrobumps as trolls abused on /mlp/. /mlp/ had punished necrobumping with bans at one point but they stopped giving a damn and the board suffered for it as trolls quickly adapted to update their new slide-strategies bumping all their page9-10 threads around the same time and just leaving it to rot like stale bread.
>>9791
>For the thread watcher my first feedback I think the glowing red warning is set too low where it is right now (5). Page 9-10 is the typical one as the glowing red purpose for page info was so you could save a thread from getting archived.
I will do some tinkering and make "notification" colors better. Also making the watcher itself more conforming (or how to say it) to the different themes.
>For the thread watcher my first feedback I think the glowing red warning is set too low where it is right now (5). Page 9-10 is the typical one as the glowing red purpose for page info was so you could save a thread from getting archived.
I will do some tinkering and make "notification" colors better. Also making the watcher itself more conforming (or how to say it) to the different themes.
So two things maybe a options toggle for to only see shotened uploaded file and a toggle to have the thread watcher be on the left side?
>>9811
>options toggle for to only see shotened uploaded file
The hash filename was an bug from my side, I had swapped the class on one of the uploads.
>a toggle to have the thread watcher be on the left side
I added an setting in the options menu to set the thread watcher to be on the left side.
>options toggle for to only see shotened uploaded file
The hash filename was an bug from my side, I had swapped the class on one of the uploads.
>a toggle to have the thread watcher be on the left side
I added an setting in the options menu to set the thread watcher to be on the left side.
>>9784
>I can set the original filename in that spot, but sometimes the original filename can be really long
Personally, I think the ideal solution would be to have a max limit beyond which it gets truncated with an ellipsis ... , and the full title is in the HTML "title" element to let you hover it.
>as it has been hashes for so long
Perfectly understandable, having an option would please everyone but probably adds an annoying amount of extra work to fit in
>"save as timestamp"
That will be absolutely tremendous if you add it, speaking as a refugee
>I can set the original filename in that spot, but sometimes the original filename can be really long
Personally, I think the ideal solution would be to have a max limit beyond which it gets truncated with an ellipsis ... , and the full title is in the HTML "title" element to let you hover it.
>as it has been hashes for so long
Perfectly understandable, having an option would please everyone but probably adds an annoying amount of extra work to fit in
>"save as timestamp"
That will be absolutely tremendous if you add it, speaking as a refugee
>>9815
>That will be absolutely tremendous if you add it, speaking as a refugee
Did some updates and added Timestamp download, Cleaned up the file header and some minor tweaks to the file handling.
>That will be absolutely tremendous if you add it, speaking as a refugee
Did some updates and added Timestamp download, Cleaned up the file header and some minor tweaks to the file handling.
>>9822
Glad you like it. Feel free to give feedback on any improvements or bugs you might encounter.
Going to take a little rest from coding, and then tomorrow try to look over what all have said and my notes on other improvements that are desired.
There is a bug where the "hide image" don't save it to user settings, so on reload the image is show again, but I will look at that tomorrow.
Glad you like it. Feel free to give feedback on any improvements or bugs you might encounter.
Going to take a little rest from coding, and then tomorrow try to look over what all have said and my notes on other improvements that are desired.
There is a bug where the "hide image" don't save it to user settings, so on reload the image is show again, but I will look at that tomorrow.
>>9823
By the way, aside from the huge wall of text I posted earlier, having used the thread watcher for a little while now I can say that currently the top really big improvements for usability are:
>1. Auto-refresh the watcher once a thread is marked as "read", so when you scroll down you don't have to also click on the watcher refresh icon to register the thread as read
>2. At least a force-refresh of state when another tab updates it (i.e. reading a thread in one tab would mark it as read in every tab), but you can kill two pegas with one stone by just adding periodic auto-refresh, to also check for new posts every n seconds without having to again manually refresh the watcher
>... gap in priority here...
>3. An option to auto-watch threads on reply
Roughly in order of priority. Right now it works great but it's a bit clunky to use across multiple tabs due to how manual the refreshes are, so having it automatically take into account once you scrolled a thread would be a game-changer, and having it passively auto-update in the background would be another one. (Would probably need some extra logic though to make sure out-of-focus tabs don't all spam refresh requests for all threads all the time.)
By the way, aside from the huge wall of text I posted earlier, having used the thread watcher for a little while now I can say that currently the top really big improvements for usability are:
>1. Auto-refresh the watcher once a thread is marked as "read", so when you scroll down you don't have to also click on the watcher refresh icon to register the thread as read
>2. At least a force-refresh of state when another tab updates it (i.e. reading a thread in one tab would mark it as read in every tab), but you can kill two pegas with one stone by just adding periodic auto-refresh, to also check for new posts every n seconds without having to again manually refresh the watcher
>... gap in priority here...
>3. An option to auto-watch threads on reply
Roughly in order of priority. Right now it works great but it's a bit clunky to use across multiple tabs due to how manual the refreshes are, so having it automatically take into account once you scrolled a thread would be a game-changer, and having it passively auto-update in the background would be another one. (Would probably need some extra logic though to make sure out-of-focus tabs don't all spam refresh requests for all threads all the time.)
>>9823
Ok, so after using it a bit:
- scrolling should be instant instead of smooth scrolling
- should highlight the first unread comment (same as #postid does in the url)
- longer thread names should be shortened instead of braking it into multiple lines
Ok, so after using it a bit:
- scrolling should be instant instead of smooth scrolling
- should highlight the first unread comment (same as #postid does in the url)
- longer thread names should be shortened instead of braking it into multiple lines
Can we do something about the current state of /vx/? Threads from 8 years ago are still on the catalog.
I like the overboard but it doesn't actually show ALL the latest posts on the this chan. If the thread is autosaging it doesn't show up on the top of the list as the latest most recent post. I don't know if this is working as intended or something that is warranted for a change, but something I noticed.
Love the thread wather. What do people think about having the originating board of the watched thread on the left, instead of the right like in the second picture?
>>9851
>>9858
Did some improvements to the thread watcher. It should now update across tabs when you update it in one. Also added an option to add "remove" button next to thread links so you can easily remove from there. Also moved the /board/ to the front of links.
Will do some more tinkering later on improvements in other areas of thread watcher, scroll to last read and other areas.
>>9858
Did some improvements to the thread watcher. It should now update across tabs when you update it in one. Also added an option to add "remove" button next to thread links so you can easily remove from there. Also moved the /board/ to the front of links.
Will do some more tinkering later on improvements in other areas of thread watcher, scroll to last read and other areas.
>>9862
Thanks for that Pupper, I appreciate it. Doing {YOUR_FAVOURITE_PONE}s work. I suppose it depends on the resolution of someones monitor or it's orientation but you can keep adding threads to the watcher past where you can interact with it, though I doubt there will be many people with a list as long as picrel.
Thanks for that Pupper, I appreciate it. Doing {YOUR_FAVOURITE_PONE}s work. I suppose it depends on the resolution of someones monitor or it's orientation but you can keep adding threads to the watcher past where you can interact with it, though I doubt there will be many people with a list as long as picrel.
>>9863
As an aside, all tabs updated when removing all those threads from the watcher, so that works as intended.
As an aside, all tabs updated when removing all those threads from the watcher, so that works as intended.
>>9871
I added that icon due to the way resize of textarea works in the Quickreply (resize the quickreply dialog box), and people had trouble finding out how. I added it in hope that it would be a little guide/hint. It has not been there for long so could be reason you didn't notice it before.
I added that icon due to the way resize of textarea works in the Quickreply (resize the quickreply dialog box), and people had trouble finding out how. I added it in hope that it would be a little guide/hint. It has not been there for long so could be reason you didn't notice it before.
Here's another frequently used QoL suggestion while you nail down the thread watcher.
Thread hiding from the catalog.
>Either with a [hide] button next to the others like [last 50] or with Shift+Click.
It looks like nhnb does have it but the function is broken, no surprises there. It can hide threads, but never keeps track of it in the filter list. So if you accidentally hide a thread, you're just permanently going to live with that. And if you wanted to hide a thread for a while, but look at it later can't do that either.
Thread hiding from the catalog.
>Either with a [hide] button next to the others like [last 50] or with Shift+Click.
It looks like nhnb does have it but the function is broken, no surprises there. It can hide threads, but never keeps track of it in the filter list. So if you accidentally hide a thread, you're just permanently going to live with that. And if you wanted to hide a thread for a while, but look at it later can't do that either.
>>9872
It's a nice addition, truth be told. The standard size of the QR box shrinks when you add a picture, which is confusing for a new user. Thank you.
>>9873
When I want to hide a thread, I don't plan on revisiting it afterward, though a catalogue hide button would be helpful for the inevitable shitposting that'll be incumen in.
It's a nice addition, truth be told. The standard size of the QR box shrinks when you add a picture, which is confusing for a new user. Thank you.
>>9873
When I want to hide a thread, I don't plan on revisiting it afterward, though a catalogue hide button would be helpful for the inevitable shitposting that'll be incumen in.
>>9874
>When I want to hide a thread, I don't plan on revisiting it afterward,
Granted, that is usually how most people will use it. Though for nhnb it was just testing out the function and now that thread is gone like a blackhole to me.
>When I want to hide a thread, I don't plan on revisiting it afterward,
Granted, that is usually how most people will use it. Though for nhnb it was just testing out the function and now that thread is gone like a blackhole to me.
>>9875
Clear your cache, if that doesn't work then try another browser in private mode and report back.
Clear your cache, if that doesn't work then try another browser in private mode and report back.
1745645817.png (471.1 KB, 3000x2040, 1ebbadc92b19c874a49de2271ebc45f72ffa539f866c75c0f23b40a0958141a8.png)
>>9876
It worked, thread that was hidden was brought back when I cleared browser settings. However, ALL of the watched threads I had were deleted with it too. I genuinely do not like anything about that board, it's made with spaghettis code and run by a team of aspies.
At least now I might know why the thread watcher would fail at random, it was probably cache/cookie related. And all the threads I watched from here are gone too, but the ones on 4chanX remain even if I clear the browser data. This could also be why people were complaining about watched threads here not working right, more browser hiccups
It worked, thread that was hidden was brought back when I cleared browser settings. However, ALL of the watched threads I had were deleted with it too. I genuinely do not like anything about that board, it's made with spaghettis code and run by a team of aspies.
At least now I might know why the thread watcher would fail at random, it was probably cache/cookie related. And all the threads I watched from here are gone too, but the ones on 4chanX remain even if I clear the browser data. This could also be why people were complaining about watched threads here not working right, more browser hiccups
If you get around to an auto-updating a thread watcher...
8moe has a counter for unread updates in their thread watcher. With the watcher set to minimized here it could benefit from a similar update like [(#) TW] the # being how many threads have updates since last opened.
8moe has a counter for unread updates in their thread watcher. With the watcher set to minimized here it could benefit from a similar update like [(#) TW] the # being how many threads have updates since last opened.
Pardon, but might I make a suggestion?
76 replies and 16 files omitted.
[View All] [Last 50 Posts] [Last 200 Posts]Post pagination: [Prev] [1-100] [101-176] [Next]
176 replies | 53 files | 65 UUIDs | Page 1
[Add to Thread Watcher]