3 ms·

Huh, I just moved my NSFW scraper to serve me content through HTTP2 server push. Guess it’s back to the drawing board. [le: curious about the downvotes (-3), f

Huh, I just moved my NSFW scraper to serve me content through HTTP2 server push. Guess it’s back to the drawing board. [le: curious about the downvotes (-3), for anyone willing to shed some light] (le2: turns out I’m using Server Side Events and not HTTP2 server push; sry for the noise)

coolspot 4y ago
Can you elaborate, for my friend, please.
- ThalesX 4y ago
  Not all that complicated, I have some places on the interwebz where my kind of NSFW content is posted so I scrape those and maintain an SQLite database of direct urls. Over that database I have a tiny Koa server that checks if URL is still active, processes image in memory and serves it through HTTP2 over to a Preact app that handles displaying them. I do this so I can share this with some people, and allow them to share some stuff without exposing myself to liability for hosting.
  - detaro 4y ago
    I'm fairly certain you are confusing Server Push with something else, because as far as I can tell Server Push is not useful for doing what you describe.
    - ThalesX 4y ago
      Clients connect to server, connection kept open and server push the base64 data to all connected clients.
      - detaro 4y ago
        that's not Server Push, but Server-Sent Events probably
        ThalesX 4y ago
        Thanks for this! You are right. I’ll update my posts and perhaps this also answers my question of why I am downvoted! I’m using SSE indeed.
  - cmeacham98 4y ago
    > I do this so I can share this with some people, and allow them to share some stuff without exposing myself to liability for hosting. I don't know what country you live in, but here where I live (in the US) you definitely aren't avoiding any legal definition of hosting by only relaying.
infensus 4y ago
You can use HTTP3... unless they find out it also has a design flaw and it's time to move to the next thing
- ocdtrekkie 4y ago
  This is one of the reasons HTTP/1.1 will still be reliable and workable decades from now, and every HTTP/2 and HTTP/3 client will be long gone. Google has just taken their ridiculous deprecation policies and applied them to web standards bodies.
  - charcircuit 4y ago
    Server push was removed from Chrome, but it wasn't removed from HTTP/2.

coolspot 4y ago

Can you elaborate, for my friend, please.

ThalesX 4y ago
Not all that complicated, I have some places on the interwebz where my kind of NSFW content is posted so I scrape those and maintain an SQLite database of direct urls. Over that database I have a tiny Koa server that checks if URL is still active, processes image in memory and serves it through HTTP2 over to a Preact app that handles displaying them. I do this so I can share this with some people, and allow them to share some stuff without exposing myself to liability for hosting.
- detaro 4y ago
  I'm fairly certain you are confusing Server Push with something else, because as far as I can tell Server Push is not useful for doing what you describe.
  - ThalesX 4y ago
    Clients connect to server, connection kept open and server push the base64 data to all connected clients.
    - detaro 4y ago
      that's not Server Push, but Server-Sent Events probably
      - ThalesX 4y ago
        Thanks for this! You are right. I’ll update my posts and perhaps this also answers my question of why I am downvoted! I’m using SSE indeed.
- cmeacham98 4y ago
  > I do this so I can share this with some people, and allow them to share some stuff without exposing myself to liability for hosting. I don't know what country you live in, but here where I live (in the US) you definitely aren't avoiding any legal definition of hosting by only relaying.

infensus 4y ago

You can use HTTP3... unless they find out it also has a design flaw and it's time to move to the next thing

ocdtrekkie 4y ago
This is one of the reasons HTTP/1.1 will still be reliable and workable decades from now, and every HTTP/2 and HTTP/3 client will be long gone. Google has just taken their ridiculous deprecation policies and applied them to web standards bodies.
- charcircuit 4y ago
  Server push was removed from Chrome, but it wasn't removed from HTTP/2.