''have to split this post up or it won't work…kek''
ANONS
Thank you so much for supporting 8kun.
Admins working 24/7 to determine what's going on that results in "server took too long" messages.
Need your help too - see below.
WHAT WE KNOW SO FAR:
-
Some and maybe MOST of the problems are related to upstream servers.
-
May be accidental. Could also be the result of deliberate efforts to shut 8kun down via censorship as in China - where certain words or symbols are blocked to mess up the works.
-
there's a problem with longer posts (where you can post a one liner but not several paragraphs). Could also be censorship-related (where longer posts get filtered out at some nodes in the network).
POSSIBLE CENSORSHIP VIA UPSTREAM SERVERS
We have identified some of the characters that will block (or sometimes block) transmission:
The double hyphen that generates small purple text
This is not working for me or engineers in the USA. may or may not work for those outside the USA - try it and see.
-
Quote marks (single or double)
Do not always work (in very specific contexts) but only for USA users. Practice thread shows the testing we've been doing - there's a certain messages that will not post when a specific instance of the word SERVER is surrounded by single or double quotes. (if i do it here, won't post).
DO YOU HAVE TROUBLE LIKE THIS?
Please LET US KNOW here in General or in the META DISCUSSION thread.'''
LENGTH OF POST
Normally, users can post at least 4500 characters. But right now, not always true.
One-liners ok, but longer posts, not always.
WHAT WORKS FOR YOU?
''Helpful if you can say whether you are posting from within or outside USA.''
Sometimes "server took too long" messages are due to overbooked upstream server nodes. Changing the DNS is the solution. Brief overview with links to instructions.
DEALING WITH SERVER PROBLEMS ON 8KUN on Windows10
>>17721740 two things to check:1-routing & 2-DNS settings
>>17721741 1. How to check data transmission nodes in Win 10
>>17721742 2. How to Change the DNS in Win 10
>>17721744 instructions for DNS
>>17721745 set credentials again
>>17721751 CAPS
>walloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftestwalloftest
will this post for me too?
test
purple
i can't post using purple text, still.
>don't care if purple text can't be posted
ah, well, that's not the point
it's that the function not working
-
demonstrating the possible use of upstream FILTERING to mess things up - doing it in a way that's hard to detect because it seems RANDOM.
Looks like NO BAKER
going to try to BAKE next bread and LOCK this one sooner after
to keep bun size moderate
fingers crossed, next baker or notetaker can generate a list of postable notables
if you have NOTES, please post them now
bakes can be challenging atm
bread length varies, we are just trying to keep the flow going & maintain manageable notables
sorry didn't see b4 baking
should be able to edit these in and update the bread
THANX