>>24021 userjs field is deprecated as the csp breaks it and it was barely functional to begin with it needs removed from the dialog the script should still work as a userscript (but not violentmonkey in firefox, it respects that weird tryhard page/context security shit)

>>24022 Huh, it does work as a userscript. Had no clue they deprecated it. Thanks for the heads up anon.

Looks like FullchanX is completely broken now and throwing "fcxs.init is not a function". I switched to 8chanSS and it looks like all the features have been reimplemented

>>24072 End of an era I guess. Fullchan-x was a very well written script. He is also the kickstarter of the 8chan scripts thread so that deserves big praise too. Thanks for all the other devs for carrying the legacy.

complete shitter when it comes to CSS here. what do i need to change if i like Penumbra but hate the font choice?

>>24116 body { font-family: ; } select, textarea { font-family: ; } ask an llm or search up a font family string for what you want

>>24117 wow, that was fast. thanks.

can confirm that the post form will sometimes disappear in 8chanSS. seems to happen when switching themes.

Lynxchan Extended-- now has the ability to filter a post by attachment. It's very hacky and probably would have been better off if it was integrated into the site, but it works.

>>24253 Thanks. I agree with the second sentence.

>>24253 Adjusted the UI a tiny bit

>>24261 the way I would like to do it for the native feature is just expose the sha256 hash lynxchan already generates and stores to normal users in a dataset var, swap the mod view to display that instead of as a text field, and then add a filter type for it but filters kind of need rewritten to to use 4chan-x/xt style filters, since those are way better ... which necessitates a settings dialog rework ... which fuck me when are you joining the team

>>24262 Looks a bit of a pain in the ass. I'm not confident enough to do it all with the most performance optimized code.

>>24263 the front end is a huge pain in the ass, you basically have to throw out everything and write something sensible in its stead, then patch all the retarded assumptions the rest of the front-end made about the bit you changed that can be guided but also anything is generally an improvement over what currently exists worst case we point out some nonsense and it gets patched I didn't really know js a couple months ago and I manage, so surely anyone else can also llms generally know js really well since it's so prevalent

>>24264 The problem with working on the front-end is that there is no docker image or equivalent so getting the frontend running for development already requires taking time to set up a VM and getting it installed and configured

>>24285 i guess that's one thing jschan has over lynxchan/aleph maybe i'll take a crack at it soon(tm)

>>24285 if it's just front end, most of the time dev overrides on the live site are enough and things go up on the dev server to double check before going live there have been images. latest look for doomkek on dockerhub, but I had a hard as fuck time trying to work with docker lynxchan itself isn't that hard to set up, just poorly documented >grab its repository, aleph, and moemods, and requirements as listed in https://gitgud.io/LynxChan/LynxChan/-/tree/master?ref_type=heads >>>distro will probably have most already >run the little lynxchan setup and tell it to use latest (default, 2.10.x) and not master, but they're not that different at the moment and stephen might ship the next version in the next couple months >>>the aliases don't work on mint and I never cared to bother setting it up manually >>>node src/be/kernel.js -fd works well enough >make an admin user per docs: lynxchan -ca -l login -p pass -gr 0 >moemods goes in src/be/addons/ (have to hard link it iirc) >link aleph to src/fe >drop config into src/be/settings/general.json file 1, ports are shifted to run behind a webserver on the same machine, and everyone runs lynxchan behind a webserver for ssl instead of figuring out its native implementation apparently default db.json config should work for mongo defaults file 2, nginx config; use http2 if you want; doesn't really make a difference yet but it will when SSE is in change cert paths if necessary, selfsign or letsencrypt; manually visit host:8888 in browser to accept the cert there for websockets not sure about the CORS headers, testing for the event server >configure alternate language packs if you're going to do anything with them, they're stored in a db because fuck you file 3 then make a board. default settings are fine unless you need to test specific features might also want to make bvol/gvol accounts if you're testing mod features could maybe copy over users/board/language dbs to an image

It's ticking me off that ctrl+clicking a cross thread link doesn't open the thread in a new tab. I can't see an event handler attached. How does it work and how do I remove it?

>>24344 because it's a global listener the logic's in tooltips.clickHandler

>>24345 Yeah that should really check if ctrl is not being pressed first before executing preventDefault() at line 509 I guess I can email a patch since it would just be adding if (event.ctrlKey) return;

>>24346 https://gitgud.io/8chan/Aleph/-/merge_requests/152 gotcha, just ignoring events with ctrl entirely so you can temporarily nullify hovering, too, if that's useful at all

The catbox embed script (the custom one in this thread) is finally broken... script devs tasukete....

>>24462 is it the script or the csp blocking it

>>24463 csp methink

>>24464 csp is blocking the script itself, not the catbox connection (which is what I thought it would do and probably still will) tampermonkey solves that first bit

>>24465 So... just migrate back to tamper? *sigh gfdi

>>24466 blame firefox and retarded extension writers they have this weird ass concept of making userscripts "safe" by not allowing them to manipulate things in the page context

So the quick reply box is this color now on Tomorrow. Who do I report this to? Script or site devs?

>>24491 site hasn't changed in months, so it's probably on your end whatever it is darkreader or similar extension?

>>24492 I have midnight lizard but I have tried disabling it and then hard refresh. I think it's 8chanSS because the setting panel's looking like this now. Then again, even the site's own setting panel's looking like that too. Other than an attempt to export and import scripts to switch to Tampermonkey and then back, I haven't touched anything else in ages.

>>24493 clear browser cache maybe with ctrl+ f5

>>24494 Well, as I said, I had tried hard refresh. Turns out it's a browser (Floorp) problem, because it does not look like that on Brave...

>>24498 that's unfortunate since I like floorp, but haven't upgraded since they switched from ESR yet you can probably just stylish around it with a few css rules

>>24498 got around to updating, can confirm it's a floorp problem it seems like --menu-color can't be set on :root {} for whatever reason it just gets forced to #ffffff maybe it's using that specifically for some of its own ui shit like those retarded fucking web panels and not even !important forces it body { --menu-color: #333; } works around it

>>24549 and looking into it, it may be related to this https://github.com/Floorp-Projects/Floorp/issues/2058 where userChrome can't overwrite floorp's internal lepton css not going to bother testing whether using something other than lepton fixes it or not hopefully it gets sorted out one way or the other

>>24550 actually, I lied, I did test it, and it does fix it if you use proton/fleurial instead of the others they also let you disable the back/forward buttons, so that's nice