I fixed the issue where hidden threads were showing on catalog view. You still can't hide threads from catalog view but it will at least respect your settings from list view.
https://github.com/divSelector/divchan/commit/a6385f209c760573487ae2f4792cbe5d529eca7d
I noticed it still kinda flashes the hidden content at you on page refresh. I don't really feel like messing with it anymore tho so.
I wrote a build guide for people who want to contribute to the working on the source code of this site. https://github.com/divSelector/divchan?tab=readme-ov-file#build-guide
Here are some visual aids for Windows users.
Notice here I am right clicking in the folder and selecting, "Open in Terminal"
It's going to download Docker images and do a lot of crazy stuff and it's eventually going to tell you "Be Patient, This Takes Awhile" as it is generating fake content for the site.
Just wait.
When it finally says "celery@2397whatever ready", that it is when it is ready to open in the browser.
One thing I noticed is that Docker Desktop for Windows does not seem to broadcast on 0.0.0.0 but you can still access the link at http://localhost:8000
When you're done working on the development site you can do CTRL + C in the terminal window to close down divchan or you can click the Stop button in Docker Desktop
If we want to put the development server back up, we don't want to generate fake content a second time since it is rather time consuming. set FAKE_CONTENT=False in the .env file.
Then the next time you do docker compose up --build, it will not take as long.
Keep in mind when you modify the code, the changes will not update on the localhost site until you bring the docker containers down and rebuild. This means you can't just hit Play in Docker Desktop.
If you have questions, lmk.
It was requested on github and I thought it was a good idea.
https://github.com/divSelector/divchan/issues/13
It should be done tonight or tomorrow some time.
I hope you've noticed that I have been building every requested featured btw. So feel free to post others.
nice
This was a feature that was requested on github
https://github.com/divSelector/divchan/issues/12
Feel free to post issues :)
It was getting pretty annoying to have to delete and repost over small typos.
Now you can fix those typos with the edit button.
You still can't edit the images though so if you accidentally post the wrong images you'll still have to use delete for now
:)
yeah can that be a thing or is wave for music in general?
>>0x000001
> yeah can that be a thing or is wave for music in general?
so yeah /wave/ is for music in general, and /mood/ is for art in general. Perhaps this is not clear enough. I will think about how to make it more clear.
also divchan when I revisit next day:
>"who thaa fck are you"
>>0x000016
> also divchan when I revisit next day:
I noticed this bug yesterday. I will fix it when I get off work. :)
>>0x000018
> I noticed this bug yesterday. I will fix it when I get off work. :)
indeed I noticed it next day of when I created the account but ignored by saying that I must have cleared cache
>>0x000019
> indeed I noticed it next day of when I created the account but ignored by saying that I must have cleared cache
It's logging everyone on the entire site out every time I deploy an update lol. I'll fix it though
>>0x00001a
It will log you out one last time but after logging back in it should now keep your session for 30 days.
>>0x000006
> It will log you out one last time but after logging back in it should now keep your session for 30 days.
>Day 1 of bro remembering me
Pls div vidya board pls I beg
>>0x00001a
> Pls div vidya board pls I beg
Oh yeah that's a great idea. I wonder what we should call it...
...please report to me which thread you had the problem in.
I believe I have discovered a horrible bug but I have to spend more time studying it before I will have a fix.
if my suspicions are correct, the bug should never occur again in new threads, but it may (likely) occur again in old threads.
I've been noticing that a lot of threads that belong in /meta/ are getting posted to /main/, and I was thinking about why that is. It's most likely because there aren't a lot of links to this board on the site and it may not be incredibly obvious that it's even an option.
The reason I had /meta/ hidden in the first place is I didn't want chatting about the board to clog up the space where content-based threads belong. But I've decided that at least for now, until I find a better way to direct users to this board, I'm just putting it here.
It's not entirely a bad thing to show off that there are early adopters talking about the board.
What do you think?