>We'll follow you as soon as we get let back on
kek
this
>>16163890 (PB)
>submit your appeal to @elonmusk
>they @twittersupport will respond in kind.
>>16163988 (PB) (Me)
>>16164005 (PB) (Me)
>>16164076 (PB) (Me)
>I am going to follow anons instructs from above and see what do's
>will report back
well
so much for that little "test"
Twitter replies to anons suspension appeal:fucking rejected
womp womp
feels good man
for reference;
I only ever had one account
I never created any alts
I followed less than 10 other accounts
this reply is absolute bullshit
picrel
its fine
my twitter account was my true legal name
uness I can post as myself they can go fuck themselves
so much for authenticating the humans
>"far right" must mean the Bush element….because real libertarian and conservative types do not give a fuck
exactly
I get what Elon is saying
but still
"equally" offending the far-right and the far-left doesnt necessarily imply a nuetral position
>you almost have to set up as a static ip
anon could change the DNS setting on their router instead of their local machine
but, considering how this has been going, that may be a bit beyond this linuxfags pay grade
>Restarting service overwrites changes. :(
well
if you LAN IP is static there is no reason to run dhcpmasq
you already have a static IP set, you dont need a DHCP server to assign an IP address for you
in addition
you local machine is getting its DNS server from the gateway device that it is being pointed at
(what IP address do you have set as the "gateway" IP under the static I settings for your local machine? -I would assume this is the IP of your WAN router?)
If your WAN router has DHCP turned on (which I am assuming it does) then your local machine is asking the "gateway" (you WAN router) for the DNS server it should use
You gateway device (the WAN router) gets this preffered DNS address from your ISP
so it goes:
local machine asks gateway for DNS server IP
gateway asks ISP for DNS server IP
I am assuming everytime you restart the service, this is happening, and you are getting the ISP supplied DNS server which over-writes the custom (9.9.9.9) server you are trying to set
In your gateway device (the WAN router) you SHOULD have a setting for "Use Custom DNS Server" (it should be called something similar to that)
you would select use custom DNS
and you would set the IP adddress to 9.9.9.9 there in your router
then
when your local machine runs its DHCP request to get the DNS server its supposed to use, your router will send back the 9.9.9.9 address that you set instead of the ISP supplied DNS address
this is at least how I understand it!