>>491
>Implying nextchan /b/ isn't also just /meta/ complaints about pedos

Hahahahahahaha anon, nice meme

>>489

Hey /b/oard owner (/b/awss? /b/O?), can we get this one on a corner like on 8/b/?

>>495

Give me the CSS and I'll copy paste it.

>>495

Oh yeah current CSS somewhere here, keep it in mind.
https://nextchan.org/b/info.html

>>498

FIRST GET

>>499

SECOND GET

>>500

m8 GETs start at 1000

>>497

body {
    background-image: url('https://nextchan.org/b/file/1421/1478633613-0.gif');
    background-repeat: no-repeat;
    background-position: right bottom;
    background-attachment: fixed;
}

>>503

What part of "keep the old css in mind" did you not get?

>>503

"The CSS you've supplied contains references that are not allowed."

Try again.

>>507

fug

>>506

I don't see the problem, when I tried it on the console the CSS was the same

>>509
>Added an = next to url
>Stopped saying reference wrong
>Also not working

What.

>>510

I think URLs are just outright banned, regardless if they come from the same domain

Scripts are a dark art to me but can the .gif not be saved somewhere like /var/something/somethingelse and the script pointed to the path?

>>514

You'd need access to the server, which can't be done unless m712 has a special preference for this board, to do that
You could try to change the tomoko gif url with something hosted elsewhere and see if it works

>>515

Okay, thanks. As i posted, scripts are a dark art to me, what i was trying to work out in my feeble brain is that, presumably the board assets and custom scripts are saved somewhere, so I don't understand what the obstacle is to adding the .gif into that directory?

Genuine question here, not trying to troll

>>516

The obstacle is having actual access to the host as to place the image in the directory
I think m712 or someone else simply made URLs unavailable with some protection system, as in theory CSS can load an image from anywhere using the url() function

>>517
>in theory CSS can load an image from anywhere using the url() function

Yes, I can see the DANGER WRIT LARGE in that. I just didn't realize the board-specific asset stuff was locked away.

Thanks for taking the time.

>>518

No problem, though this locking is recent
Before the takedown /b/ had one of the hamsters from the hampster dance dancing in a corner

>>515
>m712 has a special preference for this board

Of course he does desu this is the only actually active board besides /next/

>>515

Oh yeah forgot:

>You could try to change the tomoko gif url with something hosted elsewhere and see if it works
>Implying I'm genuinely stupid enough not to have thought of that

>>520

== I post on my board(s) from time to time ==

>>521

:^)

>>522

Well fuck you too markup, why don't you let me spoiler

>>523

the spaces maybe?

>>517

I wrote that originally. It's half-baked.

What you can do is turn the gif or image into a base64'd data-uri. Then it will work no problem.

>>529

Although, it does work better than Fred's attempt at doing such a thing. I'm sure the parser that I used is not the best for the task at hand, which is checking for invalid references.

Also, here's how to put images in your CSS with data URIs:
https://css-tricks.com/data-uris/

>>559

The board owner should be able to add any image to the CSS by making it a base64'd data uri.

>>559

Jesus christ anon, I almost threw up. The background is now a very vivid and clashing green and I can't take a screenshot because Cyanogen fucked my shit up.

>>565

Will the css ever work?
I just copied the values from a nsfw board and it worked on the console

>>565

tfw admin can't read rgb to realize I memed the settings

>>572

Kek

fuck you OP

>sage

>>488

Well...im out