#programming

1 messages ¡ Page 512 of 1

leaden crest
#

no

#

gooooooooooood bye chat

#

not doing this today neurOMEGALUL

stark needle
#

wtf

#

i love onprem high availability servers

warped narwhal
#

God has forsaken us

primal dirge
#

OpenAI should be scared from me Tutel

stark needle
#

holy gradient explosion

primal dirge
#

neurOMEGALUL dont even know how it happened

stark needle
#

also hey havent seen u in a long while in this chat lmao

primal dirge
#

yea I have been not chatting much uni has been killing me lol

mighty thorn
stark needle
#

or vanishing gradients idk

primal dirge
#

but eh the ML isn't important for this project so tbh i dont really care lol

stark needle
#

lmao

maiden geyser
#

monthly edelweiss #baking post

primal dirge
#

Chatting Edelweiss

dull egret
#

I don't even know how most of these modern frameworks can operate without some sorta CGI.

Virtually none of the languages normally used for Web have the capacity to handle any moderately large-scale load-balancing.

Except Elixir, but that's because the GenServer thing basically just IS that, functionally. Except abstract and doesn't need to be Web-related.

But yeah, like, if you're not USING a Web server, virtually no languages can handle load like a large website.

Only ones that come to mind are Actix on Rust and Elixir.

stark needle
rough bloom
# primal dirge <a:Chatting:1089703903534264391> Edelweiss

I don't even know how most of these modern frameworks can operate without some sorta CGI.

Virtually none of the languages normally used for Web have the capacity to handle any moderately large-scale load-balancing.
the answer here is fairly simple, you don't do load balancing in your web server, you delegate that to a load balancer neuroBlankies

#

-# wrong reply EvilNotL

stark needle
dull egret
rough bloom
#

load balancers? Nginx, Apache, Caddy, Traefik, Envoy, Istio
there are a lot

dull egret
rough bloom
#

no, I don't think so

#

the whole point is that you can just use a load balancer like Nginx in front of multiple instances of your slow, shitty application

#

the instances individually can be slow, but as long as you have enough instances you can in theory still handle a lot of load

fiery canopy
#

nginx isnt a load balancer

#

thjats a reverse proxy

#

😭

rough bloom
#

load balancers are usually reverse proxies SMILE

fiery canopy
#

like ig it can be configured to behaviour similarly to oen

#

but

#

it isnt really designed for that

#

from my knowledge

#

iv been using nginx for years

rough bloom
#

it supports it at least

fiery canopy
#

I see I Was wrong

#

I did sm reserch my bad on that

#

I just never even thought of using it for that

true hemlock
#

nixos

trim valve
rough bloom
opaque sigil
fiery canopy
true hemlock
fiery canopy
#

also in what world are u doing load balancing in your web app

#

that should always be delegated seperaltely

#

for good reason

true hemlock
#

no nix

#

my nix

#

gone

rigid snow
opaque sigil
fiery canopy
#

u delegate it

#

😭

#

U dont usually handle it

#

in the app itself

dull egret
# rough bloom the whole point is that you can just use a load balancer like Nginx in front of ...

So then why did you say not to do the load-balancing on the Web server itself?

Apache and Nginx are both Web servers

AND they are both load balancers

The application is just the application that acts as a script being run across the load-balancing threads / workers.

So, if you're using a language that doesn't use some kind of CGI your Web server can control the script / application (PHP, Python, Ruby) of...

So, again, assuming not something that's an all-in-one compiled solution, like Actix, or a lightweight threader with failsafe [Elixir], what is the order here?

I'm used to:

  1. WEB SERVER: Request hits Apache or Nginx
  2. LOAD BALANCER: Apache or Nginx spins up workers for a CGI language
  3. WORKERS: Many CGI workers execute segments of the load
  4. WEB SERVER: The workers return the values for dynamically generated content, as well as hyperlinks for static shit, and the Web server builds the response

So, if Apache or Nginx is STILL the load-balancer in, say, a Node application, what acts as the Web server?

fiery canopy
#

if multi instanced

rigid snow
#

yeah to a load balancer like nginx

fiery canopy
#

Thats what I was agreeing with

#

;sob

#

😭

#

I was reading back in the conversation and respodining to a point the guy made earlier

rough bloom
#

miscommunication classic

opaque wharf
#

Yeah, for NodeJS you usually spin up lots of proccess

#

Make it listen using unix socket

#

Then pass it to nginx

opaque sigil
#

tldr: node runs the server

#

and apache/nginx just forward requests to it

glass jetty
fiery canopy
rigid snow
fast pagoda
primal dirge
nocturne olive
#

neuroThinkSmug Website when?

fast pagoda
#

bro done fused every weight into one

mighty thorn
rough bloom
# dull egret So then why did you say not to do the load-balancing on the Web server itself? ...

it's sort of similar to what you described, except the applications don't use CGI, they aren't started by a webserver
instead they are themselves webservers, all the load balancer does is pass the request on to one of the webservers (instances of your application)
so it's significantly simpler:

  1. LOAD BALANCER: receives request from the client, chooses upstream webserver / application instance
  2. WEB SERVER: returns whatever content you want, builds the response
primal dirge
mighty thorn
fast pagoda
nocturne olive
fast pagoda
nocturne olive
#

Well his job is to make the website

fiery canopy
primal dirge
nocturne olive
true hemlock
nocturne olive
true hemlock
#

and multicontinent clusterfuck server or something

glass jetty
#

load balancer is also kind of web server
database is web server
cache is web server
email service is web server
... what else never gets exposed to user but kinda server?

#

everything is server

fast pagoda
glass jetty
opaque wharf
glass jetty
dull egret
fast pagoda
#

later

glass jetty
rough bloom
# dull egret So ***each worker*** is generated, sends response, and then just dies on the OS ...

So each worker is generated, sends response, and then just dies on the OS level?
no, they're their own completely independent processes, they don't even have to live on the same host or anything
the worker/application processes stay alive between requests, they're usually rarely restarted
Apache/Nginx has no idea if the worker succeeded, failed, or never executed, bc nothing is piped through it?
it does, it's a normal HTTP client
if the worker dies then the load balancer either gets an HTTP error that it can forward to the actual end users client or it runs into a timeout

fast pagoda
#

cloudflare workers be chilling for a long time technically being the same instance but also not

opaque wharf
true hemlock
fast pagoda
#

it's become a whole schizoid delusion dont worry

#

just brace yourself :^)

glass jetty
#

i wonder how many sockets is open on phone to make notification work for every app, surely it just sometime request server to poll, and not always open, right?

opaque wharf
#

Google have the highest priority and most other apps rely on it to actually distribute notification

#

Browser push notification may be put to sleep by the Android OS

fast pagoda
#

@jagged turtle i have discovered peak that saves ur life

:omemga actually is required to be making fun of @sick owl not you because of #livestream-chat message

dull egret
# rough bloom > So each worker is generated, sends response, and then just dies on the OS leve...

Ok...

The Web server listens on a port for incoming requests.

The load balancer spins up instances of the script as workers, to handle the many requests.

Apache and Nginx do BOTH of these things.

Unless the application is a long-running process that needs to handle its own memory across interconnected sessions, the only thing it would listen to is whatever the Web server or load-balancer sends it.

In your example, it sounds like Apache or Nginx is listening to incoming ports (e.g. 80, 8080, 443), AND sending the response generated by the workers.

So Apache/Nginx, if I understood what you described, is the Web server.

Are you just saying that these non-CGI systems use a different communication protocol?

What is listening to and responding on the WAN ports? That is the Web server

rough bloom
glass jetty
#

cuz creating process is costly

#

The load balancer spins up instances of the script as workers, to handle the many requests.
it never spin, it round-bound (if correct term), it just send request with same format to other process

dull egret
# glass jetty cuz creating process is costly

Yes. So you want some kinda program handling them and making sure that the routing is done to each worker.

If the application is standalone, that's different.

You may have standalone applications connecting to the workers, as well. And possibly connected to something other than the Web server.

rigid snow
#

it’s so simple really i don’t understand what’s there to be confused about. forget cgi forget everything. you have many web servers, the reverse proxy chooses one of many to proxy the request to (making it a load balancer). that it

opaque wharf
#

They may add proxy header

fiery canopy
# dull egret Ok... The Web server listens on a port for incoming requests. The load balance...

I am gonna try put this in simple terms, to shut this down. Preety much. Web-server [Node, Go, Whatever you are running your actual applicaiton in], (if that webserver has inter connecting btis still not a load balancer just cross instance communication) | Load blancer: the distribution layer, the application that takes the request and distributes it across these instances under 1 URL / IP. so when a requests hits it hits the load balancer and the load balancer then directs to the webserver

warped narwhal
opaque wharf
#

Sans static assets

rough bloom
# dull egret Ok... The Web server listens on a port for incoming requests. The load balance...

The load balancer spins up instances of the script as workers, to handle the many requests.
Apache and Nginx do BOTH of these things.
this is true for ancient PHP deployments, but practically no modern Node.js deployment works like this
the Node.js app runs its own webserver, the load balancer doesn't control its lifecycle at all, all the load balancer has is a hostname and port to forward the HTTP request to
Unless the application is a long-running process that needs to handle its own memory across interconnected sessions, the only thing it would listen to is whatever the Web server or load-balancer sends it.
the application is always a long-running process
In your example, it sounds like Apache or Nginx is listening to incoming ports (e.g. 80, 8080, 443), AND sending the response generated by the workers.
YES it forwards the response generated by the application to the client
So Apache/Nginx, if I understood what you described, is the Web server.
it is a webserver on a technicality but in this setup it functions as a load balancer and as such would usually be called a load balancer
Are you just saying that these non-CGI systems use a different communication protocol?
no, they function differently
What is listening to and responding on the WAN ports? That is the Web server
it is not the web server, it is the load balancer

glass jetty
warped narwhal
warped narwhal
opaque wharf
fiery canopy
opaque wharf
#

So http, then http2

#

In short

warped narwhal
opaque wharf
#

NodeJS app is indeed its own webserver

#

You spin up the process and it is long running

#

It accept http

fiery canopy
#

This is so stupidly simple at its core that im confused how this even turned intto a debate and how many braincells you must lack to not understand the difference between a web server and a load balancer

opaque wharf
#

Nginx and other load balancer just pass the request they received to that long running process

opaque wharf
#

It used to be CGI

fiery canopy
#

I know that but all it takes is a small amount of reserch

#

to find out

#

I think its quite litterally 1 search on yt, google or anything

#

and u can find out

#

instead of debating it here

glass jetty
#

ok i guess i just made ill assumption about configurations in nginx

#

so i can enable both proxy headers and tls?

warped narwhal
#

Just wait till you hear that nginx can serve static webpages

glass jetty
fiery canopy
#

oh yea that is a thing nginx can do

warped narwhal
#

Therefore making it both a load balancer, reverse proxy and a web aerver

fiery canopy
#

I forget nginx can do that smtimes

#

but thats gonna give @dull egret more of a mind fuck atp

rough bloom
#

-# /s

glass jetty
warped narwhal
fiery canopy
#

yep

rough bloom
#

but yeah that makes it extra confusing, since "load balancer" or "reverse proxy" or whatever is really more of a role in your design than it's something inherent to Nginx or whatever

fiery canopy
#

in all reality

opaque wharf
#

Traefik neuroPogHD

fiery canopy
#

@dull egret please use basic reserch materials such as google, youtube or many others. And stop debating about this in a discord server where people are tired of u being wrong

#

:0

#

I think thats the best solution

fiery canopy
#

fe

#

but

#

still

glass jetty
#

i make no research and debate whatever things in rust are correct or not lol

fiery canopy
#

in all reality if they are actually trying to understand it

fiery canopy
#

this is this

#

hence

#

do reserch

#

for this

#

also how long does it take this person to type a message

#

iswtg they've been typing on and off for a solid 10 mins

glass jetty
#

when you thinking actively, and writing it in words

#

you usually delete 80% of what you've typed

fiery canopy
#

ehh fe

glass jetty
#

what is fe

fiery canopy
#

fair enough

warped narwhal
warped narwhal
rough bloom
#

kill

glass jetty
#

but it is not oop language

warped narwhal
#

Not with that attitude

glass jetty
#

you cant have virtual object with data

#

you can only have methods like geters and seters

#

when oop done right oop is nice

#

but usually every one do it wrong

dull egret
#

@opaque wharf @rigid snow @rough bloom

Ok, I think I get what's happening here.

There's a difference in how I learned what these are.

My term, "Web server", means: It listens for and responds to requests. It (may) handle worker instances [in which case it is a load-balancer, as well]. ONLY a "Web server" listens for and responds DIRECTLY to requests. If it doesn't do this, it is NOT a "Web server"

From when I learned this stuff, back around 2014, what you all are calling "Web servers" were on the "Application Layer". They were not considered "servers". They were "scripts"/"applications"/"workers".

"Workers" were not "Web servers", for the express reason that they are not request handlers. They don't listen or reply on ports

An application that was also a Web server was considered inefficient as hell, something like PHP's built-in server, which is run from the command line and uses NO reverse proxy, period. It's a standalone application. You wouldn't do this, unless debugging, for most languages.

glass jetty
#

last oop thing i did is rewriting object in object in object to interface from interface from interface from interface to usage in wrapper object

#

and practically hide like 70% unneeded exposed code

glass jetty
dull egret
glass jetty
#

and it kinda is

glass jetty
#

it just never expose socket to outer network

#

request goes through proxy

opaque wharf
dull egret
# glass jetty by this definition load balancer is web server, and 'worker' is also web server

No, "workers", in this case, only interact with the Web server or load balancer. They do not receive HTTP requests directly over the Internet.

That, or calls to a standalone application, like a database.

They are strictly controlled by the Web server or load balancer, and they operate internally, only.

By this definition, no worker can be a Web server, unless you have a really funky topology.

opaque wharf
#

However, those running service are put behind load balancer

#

And you don't just run 1 single service

#

You run 5-15 or even more of them

#

So your load balancer would load balance between those running service

glass jetty
#

thing that use http is web server

#

language servers use jrpc (on std io)

glass jetty
#

base socket (custom protocol) is just server

#

when you talk about industrial it is master and slave
master is client and slave is server, so modbus slave is server, but never called server, just modbus or slave

rigid snow
glass jetty
#

sql databases, tbf idk what protocol they use

#

but they are not web servers, they are db servers

#

ftp servers are ftp servers, and not web servers

#

so basically it is client -> routing -> server -> server -> server

opaque wharf
#

It is even more confusing in JS with SSR and Vite existing at the same time neurOMEGALUL

glass jetty
#

just this server -> server -> server
is balance/reverse -> nodejs -> database

opaque wharf
glass jetty
#

ah

opaque wharf
#

What PHP used to do with templating in HTML directly

opaque sigil
#

hydration errors neuroSCHIZO

opaque wharf
#

However, I am grateful for NodeJS so I don't have to touch the mess that is PHP. Like, wdym most intellisense feature are behind paywall

rough bloom
# dull egret <@1318719337540096002> <@383112840229158923> <@105382012671520768> Ok, I think...

An application that was also a Web server was considered inefficient as hell, something like PHP's built-in server, which is run from the command line and uses NO reverse proxy, period. It's a standalone application. You wouldn't do this, unless debugging, for most languages.
not sure where you heard that it's less efficient, because it's quite the opposite kek
even something like PHP which traditionally has one process per request uses persistent worker processes now
it just doesn't use HTTP, it uses FastCGI

and ye the terminology changed a bit I think, because PHP is much less relevant than it was back then web apps aren't really called "scripts" anymore, that's mostly a PHP thing

dull egret
# glass jetty thing that use http is web server

That's the difference in definition, then.

A Web server, operates as a front-end for the Web. It is the gateway between any internal services and any requests over the WAN.


It means something different, now, I suppose.


But, if you're using Apache/Nginx/etc. As a back-proxy, anyway, why is something like Node being thrown in front? Node isn't that performant.

Aren't you handling the request twice? Once to parse the request and forward it to the load-balancer, and then the load-balancer has to process the components of the request to determine what services are to manage that request?

Pretty sure that's the reason AIO solutions exist, at all. To avoid separating the load-balancer and Web server from the application[s] and local services.

rigid snow
mighty thorn
rigid snow
rough bloom
glass jetty
opaque wharf
opaque sigil
#

there's another lsp

glass jetty
#

purpose of them is that they make almost no work to accept request

#

they redirect it
and they can receive more request than web server
(node) 8 web servers -> 100000 requests per second <- doing work
(nginx) 1 balancer -> 10000000 requests per second <- just send to workers

opaque sigil
#

forgot the name though

warped narwhal
#

Sacrifice all mortal possessions to jetbrains

rigid snow
#

true actually it’s free now

#

or is it

warped narwhal
#

Free for non commercial I think

#

Idk I just have the all access pass

broken cipher
#

lmao

rigid snow
#

oh is not part of the ce thing it’s not free

opaque sigil
broken cipher
warped narwhal
broken cipher
#

nah i'm good

warped narwhal
#

cerbyMinaGun I think you should reconsider

glass jetty
#

make web server in assembly
-# (would be faster to write custom compilator and then web server)

rigid snow
#

500 syscalls

opaque wharf
opaque sigil
#

you can write a web server in assembly in like 100 lines

glass jetty
#

omg i just listening to lecture about writing OS and 100% sure i will never use this info

#

soo nice

glass jetty
broken cipher
glass jetty
#

it can be decoded

#

write own compilator, that not just clone c, and use different call convention

dull egret
# opaque sigil nginx: takes in request from outside world and decides which node process to sen...

Ok, yup, different definition. 100%.

Like I said, in this case, from when I did Web, Nginx, in your example, is the "Web server" AND "load-balancer".

In your example, Node would NOT be a "Web server". It's just an application layer worker. Whether script or secondary service, etc. it's local-only, so server or not, it would not have been a Web server.

But the way I learned it, what you described, the only thing in there that qualifies as a "Web server" is Nginx.

It means something different, now.

glass jetty
glass jetty
rigid snow
opaque sigil
#

the node app can function as a web server in your definition too, it just happens to only get requests from nginx in this case

glass jetty
#

or you can make two nginx

warped narwhal
glass jetty
#

tho practically i doubt that make sense, since even nginx support multiple domain at same instance

stark needle
opaque sigil
#

it's important to note that nginx is not in any way necessary here

#

it just does the load balancing

mighty thorn
#

My conditional depth shit has continued to succeed every test I throw at it

#

I’m only a few tests away from a prototype for my actual project

broken cipher
#

crazy style

glass jetty
stark needle
fast pagoda
#

:omemga

rough bloom
rigid snow
glass jetty
mighty thorn
dull egret
# rigid snow you can expose the node “worker” to the internet and it would serve web requests...

The way it was described, it is not being used as a Web server.

The way Shuni described, it was.

If Node listens to the OUTSIDE, it is "Web".

Shuni described a use where there was A Node server, that was also a "Web server", as well as separate Node application servers, acting as workers.

Toast described a situation where Nginx was the "Web server", and performed load-balancing to distribute processing to several non-Web services using Node.

I literally just explained where the difference was, and now you say there is no difference.

glass jetty
rigid snow
fiery canopy
#

this is what I said earlier

#

hence me saying just google it

#

prior

rigid snow
#

a web server is something that serves web requests, usually meaning http but more broadly any web protocol

glass jetty
#

several ppl typing in #programming
on neuro sama discord server

fiery canopy
#

I know that ever hapepning is insane

broken cipher
#

like if a web server will not listen any ports on the outside it will not stop being a web server

glass jetty
broken cipher
#

true

rigid snow
glass jetty
#

but for client (user), nginx serve as web server

#

cuz client not see implementation details

rigid snow
#

no, it just forwards the request onto the node instance, it’s a proxy

mighty thorn
#

The Digital Millennium Copyright Act and its consequences have been a disaster for the human race.

glass jetty
broken cipher
#

if you will see a piece of bread made of plastic but think that it is real it will not become real bread

#

you see what i mean?

glass jetty
broken cipher
#

yes but it is not changing the reality

rough bloom
# dull egret The way it was described, it is ***not*** being used as a Web server. The way S...

Shuni described a use where there was A Node server, that was also a "Web server", as well as separate Node application servers, acting as workers.
vedalNeuroHUH when did I ever say any of that
I didn't mention Node.js that often I think, it makes no difference whether the application is written in JS or Rust or C or whatever
I don't like the "worker" terminology, but it's what you used to describe the CGI processes, so I called it that too

glass jetty
#

yes it not change reality

#

but user does not have to observe reality

#

omg why me misspelling so frequently lately

#

user does not verb <expr> .. is even valid english?

tropic spindle
glass jetty
frozen igloo
glass jetty
#

waaaait

#

at cpu lvl

#

atomic ops for locking is just locking cache line?

#

cpu can even never write but just lock cache

tropic spindle
#

My gif got unstarred FRICK you Discord

dull egret
# rigid snow this is just bs i’m sorry but you’re arguing about a topic you don’t know much a...

A server: Any application that performs a continuous process, listening to input and generating output

A Web server: A server that directly handles inbound and outbound HTTP requests, performing routing to scripts, applications, and static assets.

A Web server is capable of returning an asset, such as favicon.ico. Without THIS running, favicon.ico cannot be retrieved, and your website has no icon in the tab.

A Web server reads a URI/URL, and it determines the processes to send the request to for further processing.

A Web server returns the HTTP response object, including all dynamic content generated by scripts or other processes, and URI references to media assets, etc. to the over-the-Internet client. The client receives no request, no error, nothing except a browser timeout, without this service running.

In the case described, if Nginx is not operating, the website will return a network error or timeout. The remote host does NOT respond, period. Not a service ON the host, which doesn't perform the correct processing or times out, but the entire remote host will not reply. Nothing is listening to that request.

If the "Web server" IS running, but you requested bullshit, it will return a PAGE NOT FOUND error, or maybe a BAD GATEWAY or a PAGE MOVED.

If the Web server is not running, you cannot even get a server-generated error message, because you cannot connect to the host, at all.

If you can connect to the host and initiate HTTP processing, THAT is the "Web server", whatever that server may be.
(Based on the way I learned the meaning of that term)

There is apparently a NEW definition for THAT term, or different architectural changes for how Web is handled, than what I worked with.

But if the physical network device is replying, only the thing that sends YOU a response is the "Web server".

glass jetty
#

screamer

fast pagoda
tropic spindle
amber fractal
rigid snow
#

like you almost got it but your stubbornness keeps you like an inch away from understanding it

#

yes the reverse proxy is technically the thing that you send requests to and receive responses from. yes. doesn’t change the terminology. we don’t call it a web server in this scenario

#

only when that nginx instance starts serving static files it becomes a web server, like favicon.ico you mentioned. but it rarely does nowadays - it’s either a separate server or a part of the app (which is the server)

rough bloom
glass jetty
# dull egret A server: ***Any** application that performs a continuous process, listening to ...

a server: any application that perform io, when user of this io is another application or server
web server: server that handle web protocols, usually http cuz it is most popular one

static information like icon.ico is just data that any server answer on request; if it was web request, it will be returned in web format; if it was some custom request, will be returned in format request (protocol) specify; to return some data like this server should be aware of protocol, http protocol is literally protocol for transferring files

web server almost never read uri, it is always url, uri is something something LSP
on requested url, following configuration of web server, it can either just return result or proxy it to another server

omg where you got uri:

  1. client request index.html
  2. server send index.html
  3. client see that index.html also request ico.png
  4. client request ico.png
  5. server send ico.png

The client receives no request, no error,...
client can and will receive error; what request means here?

it will return error indicating that this port cant be accessed, it is linux tcp stack task to reply with error
if there no 'workers' under nginx, it will return nginx error, or maybe timeout

bad gateway is proxy error, 404 (not found) is web server error, yes it will return error if request is bullshit
gateway error (no api running): https://charaverk.online/api/
web server error (no file found): https://charaverk.online/web/boobs.pnh

web server is thing that answer your web request
wtf is initiate http processing? http is request-answer, it have no process
dont confuse with web socket

definition of web server.. pretty sure it never changed
reinterpretation maybe, idk is there even official definition

#

only the thing that sends YOU a response is the "Web server".
practically yes; you send request to proxy, server handle, proxy send back to you
for you it looks like you requested to web server directly #programming message

amber fractal
#

What are these link choices AINTNOWAY

sage crag
#

pluu

glass jetty
#

something wrong with boobs being not found?

sage crag
#

something

#

eyes

leaden crest
#

konii is that you SMILE

#

undercover again I see

sage crag
#

nrr

opaque wharf
#

Are we still discussing server?

sage crag
#

me fox🦊ying

glass jetty
glass jetty
sage crag
#

bzzzz

hard delta
#

a server is a person who brings you drinks

rigid snow
sage crag
#

ghost enub

stark needle
#

bbbbbbb

rigid snow
rigid snow
sage crag
#

MitoOhISee

glass jetty
sage crag
#

and

glass jetty
#

meow

sage crag
#

Ert

sage crag
#

nam

rigid snow
sage crag
#

ye

#

why

rigid snow
#

🗜️

opaque wharf
glass jetty
#

meeeeew

#

i hear this meeew

sage crag
#

edelposterneuroLookDown

stark needle
rigid snow
stark needle
#

wtf yuri convention exists

sage crag
#

brain dmaga

sage crag
woven coralBOT
#
im\_shadowo
Server Avatar
fast pagoda
sage crag
#

konyin

glass jetty
fast pagoda
#

i am sorry mother but i had to follow my heart

#

:omemga

sage crag
#

unfilial

fast pagoda
#

banger

fast pagoda
rigid snow
sage crag
#

i want a million dolar

fast pagoda
#

damn old witch

#

demanding my millions

sage crag
#

witch young

#

NOT hag

stark needle
fast pagoda
stark needle
#

symbxl my beloved

glass jetty
stark needle
#

best oshi

glass jetty
fast pagoda
glass jetty
fast pagoda
#

yeah this is ripped off the site

#

i use the site as a speedtest

#

lol

glass jetty
#

i just download new music and save it locally

#

cuz one day i will be cut out from internet

#

and i will at least have music

#

until ill leave

fast pagoda
#

me too

#

it just happens that it's all on r2 so it's a really good test for downloading a lot of files

fast pagoda
#

ive cost cloudflare billions

glass jetty
#

@lavish nest ban this guy

#

🐀

fast pagoda
#

it's free egress

#

have mercy

glass jetty
#

also plz

#

remove

#

notify about lvl

dull egret
# broken cipher like if a web server will not listen any ports on the outside it will not stop b...

But a generic server that does not listen to inbound/outbound ports, specifically for HTTP requests, is NOT a "Web server".

If it DOES listen for those things, it's a "Web server".

Not using the functionality does change what [that instance] is.

For instance, a "load-balancer" may or may not handle Web requests. If you are not using it to route traffic, it's NOT a "Web server". It's only a "load-balancer". If it ALSO routes inbound/outbound requests, it is ALSO a "Web server"

If you run an AI on Node.js (which I've seen somewhere, at least once), that instance of Node is NOT a "Web server". It is an AI application server.


By YOUR definition, MANY ENTIRE LANGUAGES are """Web servers""", because they have "Web server" functionality built in, such as for debugging network applications.

Does everything with an HTTP implementation in their standard library qualify as a "Web server"?

A """"Web server""" ha[s|d] a VERY SPECIFIC definition.

I'm leaning more towards, Devs don't know what they're doing, now, with how dead certain you are about what you just said.

If the meaning changed, because the architecture changed, that's one thing. I may be wrong, then.

If the meaning changed, because people stopped knowing how Web Dev works, then they're wrong.

And it's certainly not for nothing, because Web Dev is TRASH, these days. So it's clear most Web devs don't know anything about their field.


A car can have the tires removed and put on tracks. Does that make it a train? No, it's not a train, unless you DO that. (Whether or not that's a good idea)

Node.js is NOT a "Web server", but can be used to make one.

Literally how it's described.

fast pagoda
kind nimbus
# fast pagoda banger

I still really like this unofficial duet

https://youtube.com/watch?v=tvmb1eeb5GQ

I do not own any clips, i just try to save neuro content so everyone can watch it

Disclaimer:
original edit was made my queenpb herself

https://www.youtube.com/watch?v=zEDnhTRsbaI original song

https://www.twitch.tv/vedal987 dont miss any stream

https://discord.gg/MZPyedT check out the offical discord
https://twitter.com/NeurosamaAI Ne...

▶ Play video
stark needle
#

holy walls of text

glass jetty
#

why two accounts?

glass jetty
#

.
there so many bangers
evil voice is better tho

fast pagoda
#

usually weirdly good

glass jetty
#

time to ytdlp

kind nimbus
glass jetty
#

how many songs i still missing

fast pagoda
fast pagoda
glass jetty
#

and i filtred to 480

fast pagoda
#

lol this guy fucked up the glass shattering

#

Las letras no han sido traducidas por mĂ­ (sĂłlo un pequeĂąo extracto de la canciĂłn, cuando canta Gumi)

SUBTÍTULOS DE HIBIKASE:
https://www.youtube.com/watch?v=ablLyWpcXVQ

SUBTÍTULOS DE ECHO:
https://www.youtube.com/watch?v=v09szDPryXE

LIVE (SIN SUBTÍTULOS):
https://www.youtube.com/watch?v=hS8SPYtD1Ds

Me gustĂł mucho ese concierto, por...

▶ Play video
#

my beloved

sage crag
#

wrr

midnight sigil
#

https://x.com/trq212/status/2052811606032269638

these mf said Markdown is the next only "programming" language you need to know(because of AI skills ig), and now they say Markdown is going to be eliminated. They want to do everything to keep to bubble going huh

HTML is the new markdown.

I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why.

stark needle
wispy pike
sage crag
glass jetty
fast pagoda
glass jetty
#

symbiaaaosis, the synergy of conflict in theee brain

#

reverse the loop of swallowing

fast pagoda
glass jetty
#

is discord not enough for you?

sage crag
fast pagoda
#

im boutta click this

wispy pike
kind nimbus
fast pagoda
fast pagoda
midnight sigil
glass jetty
#

use firefox :nooo:

warped narwhal
midnight sigil
glass jetty
#

some one actually maintain nixos

#

so its fine

midnight sigil
#

big boss Google rules the internet, their engine should comply the specs better neuroKufufu

analog junco
leaden crest
glass jetty
#

i not listen japanise and i always want to skip it, but only way is failing it

analog junco
glass jetty
glass jetty
fast pagoda
analog junco
dull egret
# glass jetty a server: any application that perform io, when user of this io is another appli...

HTTP is the protocol for transferring Hypertext. Hypertext Transfer Protocol.

Multiple protocols handles "files". One of the other ones I'm sure you've heard of is FTP.


Not every server can handle static assets. And without the "Web server", you will NOT get that file.

You DO know that you can ALSO have MULTIPLE of the thing I call "Web servers" on the same physical hardware, right?

And that, likewise, disparate hardware in disparate locations can all handle different components of a request, right?

When you get a remote CDN link to static assets, BOTH the application server AND the CDN host have separate "Web servers".

And a NEW request is made to access the static content on the CDN.

So that is sent like this:
[Client] Gimme page

[Address 1 Web Server] Here's where these request parts go

[Various Services] Here are the resources, formatted as HTTP/S
~~~
[Address 1 Web Server] I need some ceap from the CDN... <Generates NEW request>

[Address 2 Web Server] Here is a list of those uploads!

[Address 1 Web Server] Here's your page, Client!
~~~

{Alternatively}
~~~
[Address 1 Web Server] Here's you page, Client!

[Client] Hmmm... I don't have these assets, but there's a link... <Requests the static files in NEW request to CDN>

[Address 2 Web Server] Yeah, I got those... Here is a list of those uploads!
~~~

Whether the separate Web servers are on one or multiple machines and in one or multiple locations, they each take inbound requests over a port

You can even have a single physical server do NOTHING but handle Web requests, and routes those requests to NUMEROUS other computers on or off the network.

You could have Nginx routing all relevant requests to services that handle a cluster of databases, Apache routing all relevant requests to services handling static assets in a whole other campus, and Actix generating real-time session stuff and handing off stuff to Redis for caching. It may also be doing server protection, by reading in something from Cloudflare or CAPTCHA, services not native to the local provider.

What is "initiate HTTP processing?"
You send HTTP request. The Web server then either processes it directly or hands it off to a service that does.

HTTP is request-answer. It has no process. Don't confuse with WebSocket
WebSocket is a continuous streaming connection to a remote host. It is not a request. But it will be opened BY a response providing credentials to open a streaming socket.

HTTP is a stateless protocol that requires state to be handled on the endpoints. The Web server launches a process (thread, script, whatever handler is configured and that it's designed for), in response to an HTTP request. That process handles the request HEADERS

And the REQUEST ITSELF is handled by the "Web server" (does the routing for that request)

fast pagoda
sage crag
fast pagoda
#

lutel

#

the first approval ive ever receive

sage crag
#

im running low on cash

fast pagoda
#

but i just sent you a million

sage crag
#

i spent it

fast pagoda
#

on what D:

sage crag
#

financial investment

#

in vegas

fast pagoda
#

how're the tickers looking

#

im sure you're up big

#

in your portfolio

rigid snow
#

chip mentioned omg

sage crag
#

the red number

dull egret
olive sable
#

goodmorning

rigid snow
sage crag
#

catpcha

#

meow

fast pagoda
sage crag
#

its down

fast pagoda
#

no i do not see

dull egret
sage crag
#

the part where essaying

warped narwhal
fast pagoda
#

i found a pic of you earlier

sage crag
#

even if the contents is correct its emotionally wrong

#

doxx

fast pagoda
#

when you were younger

sage crag
#

child idiot

glass jetty
# dull egret HTTP is the protocol for transferring *Hypertext*. Hypertext Transfer Protocol. ...

i dont understand you trying to say what you are understanding, or trying to correct me

2 things: any server that allow you to access resource by name on server file system return to you static asset, and there still no such thing as http processing in term of session, http is per file request-answer, no session, this is why REST also stateless

web server not launch process thread or script, it launch coroutine, subroutine if it is correct term

sage crag
fast pagoda
#

that your fault AtorinSmadge

sage crag
warped narwhal
fast pagoda
#

NO

sage crag
#

again

rigid snow
warped narwhal
sage crag
#

no wonder this one is stupid

rigid snow
#

did you hear they signed ninja

maiden geyser
analog junco
glass jetty
#

it should be really unusual when server side want to request something from cdn

#

tho im not web dev and not entirely sure
that just common sense for me

dull egret
# warped narwhal All of it

Well, I've hosted Websites, configured them to operate through Apache and Nginx, and handled the "worker" scripts on the backend; including the entire separation of routing, static files, and dynamically -generated content; and the whole database architecture, as well as POST handlers, and, in a few instances, HTTP Authentication over the browser.

And manual XMLHTTPRequest handling for AJAX.

So, very interesting you say that.

sage crag
#

cdn stands for clinician denial note

sage crag
fast pagoda
#

think again

rigid snow
rough bloom
sage crag
#

file transfer protocol

#

@sage crag

bitter phoenix
#

Hey @fast pagoda random question, do you have any decent ideas for procurement/creation of SFT datasets for casual conversation. Currently I’m leaning into rlhf progres patching up my pipeline insufficiencies

sage crag
#

whopingedme

rigid snow
sage crag
#

o

#

why

rigid snow
#

idk

kind fable
#

i'm sorry to inflict you guys this pain

sage crag
rigid snow
#

because you’re cool

sage crag
#

thanks

rigid snow
#

⭐

glass jetty
#

and why

sage crag
#

i am idol

#

✅

olive sable
sage crag
glass jetty
#

it make no sense for it to be powerpoint

rigid snow
#

it makes no sense to begin with because it is intended to not make sense

#

it just acronym soup

glass jetty
sage crag
#

coke is so sour

nocturne olive
sage crag
kind fable
rigid snow
kind fable
#

i just forward

sage crag
kind fable
#

cause i'm myself in physical pain

#

so much nesting

glass jetty
sage crag
#

mku mku oo ee oo

rough bloom
#

🎤 🎶 agem nub

kind fable
#

someone i know

#

but that's it

sage crag
#

agem

rough bloom
#

bun

sage crag
rigid snow
#

bun

sage crag
kind fable
#

deno

sage crag
#

no

#

your career is over

kind fable
#

wrong

sage crag
#

you will be blocklisted across all entertainment platforms

kind fable
#

wrong

sage crag
#

i'll make sure you never ger another acting job ever again

kind fable
#

kek

sage crag
#

all of your promotions? cancelled

olive sable
#

i woke up with dementia, i dont remember what iw as doing besides clone hero

dull egret
# rigid snow just actual babble

Actual babble

He probably never wrote up routing rules in the service config file, not created separate domains and public/private content hosting paths

I bet you don't even know what AJAX is. Or how to hot load new content and inject it into the DOM on timers or events?

Do you know what asynchronous form submissions are and how to manipulate and update cookies and sessions?

Can you generate an SQL query without some ORM engines?

Temporary page files that initiate an entire sequence of SQL actions to orderly generate a database?

ElivFrickoff EvilFrickYou

kind fable
#

i alr have no job

sage crag
#

all of your drama romcom series? cancelled

kind fable
#

if you prevent me from getting a job it cancel

kind fable
sage crag
#

the currently airing 12 episode series about the fall of rome? cancelled

#

you'll never survive

olive sable
molten island
sage crag
rough bloom
#

tradtional format

dull egret
olive sable
#

i see

dull egret
#

Ok, I wasted 3 hours. I have to go

sage crag
#

by

rough bloom
#

neuroWaveA bye Edel

glass jetty
molten island
sage crag
#

neuroCatUuh emug

olive sable
#

i dont get what was wrong about the http thing. but i have no clue how that shit works so evilShrug

sage crag
#

ttast emug lt officer

molten island
sage crag
rough bloom
sage crag
#

mug fan

glass jetty
#

who need nitro

sage crag
#

how mug become more popular every day

glass jetty
#

just use images

sage crag
molten island
#

too lazy

molten island
glass jetty
#

big bwaa

amber fractal
#

Emotes convient

#

Easily accessible

opaque wharf
#

Got some nice ice cold water in 00.00

fast pagoda
# bitter phoenix Hey <@146797401720487936> random question, do you have any decent ideas for proc...

that is random
best advise i can give (dont listen to me) is that quality > quantity mostly as tends to be the case in all but if trying to go for a specific persona without steering it live it will be extremely random what you get unless you're very picky about what you include. but being too specific with it will kinda still steer it, just into a really cringy version of what you're going for. too unspecific and you get a regular model out the back but i find that the noise does help because it removes predictability. especially if you are using like, your data, because you're REALLY good at next token predicting yourself and it wont work for you. dont fine tune instruct tuned most for conversation as that's pretty contrary to the indifferent persona a regular person typically portrays, i like to make synthetic slightly instruct flavoured subsets to sample from when starting the training but only enough to help it hold a thread of intent and that's it. rlhf dont use regular sets like ultrafeedback or w/e cuz they are not helpful for sovl. they will give you a lotta slop tho

glass jetty
#

llms again....

fast pagoda
#

i am instruct tuned so i cant not respond to a query

#

better than http

#

maybe

olive sable
olive sable
#

my new phone

#

has decided

#

no more audio via bluetooth

olive sable
#

and videos wont play for more than 5 seconds

kind nimbus
#

Dafuq

olive sable
#

i already did

kind nimbus
#

Is it running windows

olive sable
fast pagoda
#

more

kind nimbus
#

Reboot harder

fast pagoda
#

i rebooted my stupid magic sand shelf probably 20 times while trying to fix it not realizing it had 4 nics but didnt initialize any of them

bitter phoenix
bitter phoenix
#

Magic sand shelf

fast pagoda
#

yeah the occult shrine in my closet

kind nimbus
fast pagoda
olive sable
kind nimbus
fast pagoda
#

i still have extra laying around

#

when i replaced my cpu cooler

#

i suddenly had 8 excess fans

fast pagoda
#

and already had ordered more

#

so

#

i be moving air

kind nimbus
#

I have 10 fans in my computer

Why? Because the case gave me the opportunity to put that many fans in there

sick owl
#

Wrong vid lmao

#

Same channel though

#

Turns out that Unitree backdoor is way worse than I thought

kind nimbus
maiden geyser
glad path
bitter phoenix
#

Is there any chance you have a research journal you could send me @fast pagoda? I could provide you mine as well, not to be too imposing

#

I really think you’re super smart

#

Through obvious experience

sick owl
sage crag
#

i need another million dolar

bitter phoenix
#

I can give you a high five

sage crag
#

not you

olive sable
sage crag
#

the unfilial child

#

@fast pagoda

#

did you know youre adopted

tiny edge
#

nixos sucks holy

bitter phoenix
tiny edge
#

im 3 days trying to put cachyos kernel without building the kernel

bitter phoenix
#

My best advice is to forget what you know about generic Linux systems, there’s no knowledge crossover

amber fractal
#

insert the nixos defender response here

kind nimbus
tiny edge
sage crag
#

i did it myself

tiny edge
#

everyone just expects you to know

bitter phoenix
kind nimbus
sage crag
#

if it confusing, say how, i help

tiny edge
rough bloom
#

rude

shrewd cloak
sage crag
#

enub it take 10 minute

fast pagoda
sage crag
#

just add substituter before rebuilding

tiny edge
#

its like the second result in google search idk

shrewd cloak
bitter phoenix
sage crag
opaque wharf
kind nimbus
#

I created a whole entire nix module for the CachyOS kernel because why not lmao

olive sable
opaque wharf
opaque wharf
kind nimbus
bitter phoenix
# tiny edge deprecated

Only source I can think of for a binary, the other option is disabling as many kernel modules as you can so that the build is fast

sage crag
rough bloom
#

has GitHub CI apparently

sage crag
kind nimbus
rough bloom
#

so should all be cached

sage crag
#

wrrr

kind nimbus
#

Also Nvidia

tiny edge
fast pagoda
rough bloom
#

vedalWow even has separate branch for only cached versions

#

never need to rebuild

sage crag
#

Tutel lutel

kind nimbus
sage crag
bitter phoenix
amber fractal
#

I'll never get NixOS defenders, it's a hard OS in general. Has some helpers but it is just challenging to use.

sage crag
fast pagoda
rough bloom
sage crag
fast pagoda
#

u

#

make

#

use

#

nik

olive sable
opaque wharf
kind nimbus
fast pagoda
sage crag
fast pagoda
#

@tender river

sage crag
#

no

fast pagoda
#

@true hemlock ?

tiny edge
#

i think i see what i did wrong

sage crag
rough bloom
sage crag
fast pagoda
#

no i want them to be my 2nd mother

sage crag
#

vetoed

fast pagoda
rough bloom
#

no

#

mabe in 2027

#

2026 is banana campaign year

amber fractal
sage crag
bitter phoenix
# amber fractal I'll never get NixOS defenders, it's a hard OS in general. Has some helpers but ...

I don’t think so, it is learning the language. Okay take this example from a few days ago, there’s this new TTY replacement with color and GPU rendering super, just a directly better TTY. On a generic Linux system that would be a difficult process where if you do any step out of order or incorrectly then you won’t be able to boot. On NixOS it’s one line to do it and you keep everything instead of overwriting your kernel for the modified one. And it’s like that for any process, changing GPU driver version etc. and you’re never “stuck in a hole” you have to climb out of like you could be in other systems

opaque wharf
#

This channel in a nixshell

fast pagoda
#

actualy me holy

bitter phoenix
kind nimbus
opaque wharf
sage crag
kind nimbus
bitter phoenix
#

NixOS never breaks, I like it a lot

#

I was gonna make a blog about it

#

Did you know there’s tons of blogs about nixos

sage crag
#

you can go yourself

#

you have a phone

kind nimbus
amber fractal
#

I like the concept of being able to do something once and have it mostly work. I appreciate all of the effort that NixOS goes through to make it as easy as it does. I'm not saying I dislike it, I just say it is hard.

sage crag
#

make an appointment

sage crag
#

your grades are dropping

rough bloom
# opaque wharf Honestly, I can get behind those statement

I could see that being the case if containers and other escape hatches didn't exist
like, I run some services in Docker containers because porting them to a proper NixOS module is too annoying kek
but I prefer the stuff that has good NixOS modules running natively

sage crag
#

im not joking

fast pagoda
#

:(

tiny edge
#

nixos is good as most distros, the problem is tweaking it for your liking

bitter phoenix
kind nimbus
fast pagoda
sage crag
#

my

#

my stuff

opaque wharf
#

TV?!

sage crag
opaque wharf
#

konii?!

sage crag
amber fractal
#

Good to know every counteraegument is Skill issue
Great look neuroD

fast pagoda
#

that's right

kind nimbus
sage crag
#

patricide

fast pagoda
#

it's weird that you keep grandpa in the den liek that

rough bloom
#

there's a difficulty spike as soon as you have to modify derivations or make your own modules or something

sage crag
rough bloom
#

or understand how linking works

opaque wharf
#

Man, I am too tired for this. Good night everyone neuroSleep

sage crag
#

whyyy

fast pagoda
#

i inheretid

olive sable
#

i dont find it hard, but your millage may vary i guess

fast pagoda
#

his fans

sage crag
#

we needed his money

#

not his organs

kind nimbus
olive sable
kind nimbus
glass jetty
glass jetty
#

someone got 39bit mmu

sage crag
#

i hav

#

11 core processor

maiden geyser
glass jetty
maiden geyser
stark needle
bitter phoenix
# kind nimbus Uh Well i need tons of different tools for pentesting I ported some tools to ni...

Ahh, if there’s anything outside of nix I need I just use distrobox.

Also I think it’s generally useful to have this, basically if there’s something you’re trying to run like cowsay but you don’t have it but it is a nix package then it will automatically be imported and ran as if you prefixed it with nix shell:
environment.sessionVariables.NIX_AUTO_RUN = "1";

glass jetty
bitter phoenix
#

It’s like having a super terminal when you can just run anything

kind nimbus
fast pagoda
#

Arch Linux

glass jetty
#

use ArchLinux

bitter phoenix
kind nimbus
bitter phoenix
#

Breaks easily

glass jetty
glass jetty
#

use arch for desktop and server

bitter phoenix
glass jetty
#

had one issue with keyring, its all

kind nimbus
bitter phoenix
bitter phoenix
glass jetty
sage crag
#

what if you

#

turn on gnu coreutils fuzzer

rough bloom
silent cloak
#

bros not gonna land a programming job

sage crag
#

i had spicy food earlier but it wasnt enough and i can still smell it

fast pagoda
#

Stinky

kind nimbus
kind fable
bitter phoenix
sage crag
glass jetty
#

just use consteval

glass jetty
#

rust stable consteval functions soon @tm

silent cloak
rough bloom
silent cloak
#

ive yet to move past constexpr

glass jetty
sage crag
# glass jetty just use consteval
Natural := fn($c: type): type return struct {
    suc := Natural(@CurrentScope())
    pre := c

    erm := fn($n: @Any()): @TypeOf(n) return n
    $fold := fn($base: @Any(), $step: @Any()): @TypeOf(erm) return fn($n: type): @TypeOf(base) {
        acc := base
        $while n != zero { acc = step(acc) n = n.pre }
        return acc
    }

    add := fold(@CurrentScope(), fn($x: type): type return x.suc)
    sub := fold(@CurrentScope(), fn($x: type): type return x.pre)

    mul := fold(zero, fn($x: type): type return x.add(@CurrentScope()))

    fact := fn(): type {
        $base := struct { p := zero.suc c := @CurrentScope() }
        return fold(base, fn($x: @Any()): @Any() return struct { p := x.p.mul(x.c) c := x.c.pre })(@CurrentScope()).p
    }

    to_uint := fn(): uint {
        return fold(0, fn($x: uint): uint return x + 1)(@CurrentScope())
    }
}
zero := Natural(never)

fib := fn($x: type): type {
    $a := zero
    $b := zero.suc

    $while x != zero {
        $t := a.add(b)
        a = b
        b = t
        x = x.pre
    }

    return a
}

one := zero.suc
two := one.suc
four := two.add(two)

main := fn(): uint {
     return @eval(fib(four.mul(two).suc.suc.suc.suc.suc).to_uint())
}
rough bloom
silent cloak
#

i barely touch templates tbh

#

i dont like that type of abstraction besides for small things

kind nimbus
glass jetty
fast pagoda
#

Btrfs snapshots that hook on Pacman etc handles a lot of the generations rebuild stuff

Although yes nix rollback is much more granular, and it has to build properly first so it has a much more difficult time forcing anything broken severely in the first place, and nix you can just do your configuration not everything else with more ease

fast pagoda
#

But. I'm already too lazy to properly use snapshots

rough bloom
#

your home directory and databases hopefully not in RAM

sage crag
#

wrong language

glass jetty
#

just fuse rust and cpp

kind nimbus
rough bloom
#

ye

silent cloak
rough bloom
#

still have writable mountpoints

#

will just recurse into those mountpoints

#

and delete stuff

kind nimbus
#

If you delete my home it's still not gone

fast pagoda
sage crag
#

oops! all nim

fast pagoda
#

Wolf from twilight

#

Jacob perhaps

#

I hate him so I don't look at him

#

Naw his fur is different

bitter phoenix
sage crag
#

i dont know anything about twilight but i have strong opinions about how to make it better

#

you cant guess

silent cloak
#

just a bad romance series

fast pagoda
#

Think that's Leah kek

kind nimbus
glass jetty
# silent cloak but with C++ syntax pls

nah
some things in rust are better
for example let instead of auto, types by default can nothing, move by default and copy only if derived, matching, break on label, lambdas syntax -> i actually want both cpp and rust lambdas

rough bloom
#

can do that on Arch or whatever too

silent cloak
fast pagoda
#

I do it on arch

olive sable
kind nimbus
fast pagoda
#

Geologists do it in the dirt

silent cloak
#

ill take pretty much any other language over its design

wispy pike
#

I hate twilight all it did is give me nothing to talk about with the opposite gender when I was a kid

fast pagoda
#

I talked to them about it instead

#

It was greT

sage crag
silent cloak