[ Home / * / RSS ] [ b / c / g / lit / guestbook ] [ k / a / min / t / m ] [ Deepswarm / Services ] [ Search / Rules / Mod ]

/g/ - Technology

"The version with Linux, we call “GNU/Linux.” It is OK to call it “GNU” when you want to be really short, but it is better to call it “GNU/Linux” so as to give Torvalds some credit."
[Return][Go to bottom]
Name
(Name could be empty, then a random name will be used from a pool.)
Options(sage: append your comment to a thread without bumping it; noko: after commenting, make your url stay inside the thread.)
Subject
Comment
File
Ext: jpg|jpeg|png|txt|conf|org|md|pdf|epub, Media:mp3|flac|webm; Max Size: 12M (Sum of all files);
Embed

Markup Guide

  • heading: use ## as 2nd heading and ### as 3rd.
  • inline code, use `
  • strong text, use **
  • italic text, use * or _ (single underscore)
  • slash the text, use ~~
  • underline the text, use __, enclosing text in double underscores.
  • Make hyperlink, directly paste url or use markdown syntax: [Link name](the url)
  • Goth the text, use [[ and ]]; Garamond the text, use (( and ))
  • Spolier the text, use ==; Make the text glowing, use ::
  • Make Kiketext, use ((( and )))
  • link inline meme/smiley, use double plus signs ++http://dswarmsikhttkg7jgsoyfiqpj3ighupfrvuz5ri3lu5q2dlqyrpgk7ad.onion/css/e/b0.webp++
  • code block, use ```:

    ```
    // comment
    some code
    ```

  • A place for testing markup: /test. I'll clean test threads from time to time, so use it when you're not sure.
  • Use >>NUM (double) to make reference in-board,
  • use >>>/SLUG/NUM (triple) to reference any post of any board.

    File: 1731159519574.png (3.67 KB, 250x250,txtdot.png)

     No.58

    >Making the internet readable again
    >TxtDot
    Looks like typical small software but this requires npm pnpm nodejs or docker. The official installation guide is useless and outdated. I tried to not use docker at first place but the bloatness of npm and nodejs family really disgusted me.

    New instance: http://txtdot.deep-swarm.xyz/

     No.59

    File: 1731165584009.png (170.26 KB, 1204x939,imageMagick.png)

    Parsing: https://rsarchive.org/Books/GA006/English/APC1928/
    - Result
    - Onion

    Parsing normal wp article:
    - Result

    For web.archive.org:
    - Result

    But I found it may block tor ips: 403 Forbidden and show 404 for above links. Nope it was just caused by my bad nginx config.

     No.60

    >>59
    My config. Remember to set limit:
    limit_req_zone $binary_remote_addr zone=txtdotapi:10m rate=2r/s;
    server {
            server_name txtdot.deep-swarm.xyz ;
    
            location / {
                limit_req zone=txtdotapi burst=4;
                proxy_pass http://127.0.0.1:8070;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
            }
    
    
        listen [::]:443 ssl http2; # managed by Certbot
        listen 443 ssl http2; # managed by Certbot
        ssl_certificate /etc/letsencrypt/live/txtdot.deep-swarm.xyz/fullchain.pem; # managed by Certbot
        ssl_certificate_key /etc/letsencrypt/live/txtdot.deep-swarm.xyz/privkey.pem; # managed by Certbot
        include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
        ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
    
    }
    
    server {
        if ($host = txtdot.deep-swarm.xyz) {
            return 301 https://$host$request_uri;
        } # managed by Certbot
    
            server_name txtdot.deep-swarm.xyz ;
            listen 80;
            listen [::]:80;
            return 404; # managed by Certbot
    
    }
    
    server {
        if ($host = txtdot.deep-swarm.xyz) {
            return 301 https://$host$request_uri;
        } # managed by Certbot
    
            server_name txtdot.deep-swarm.xyz ;
            listen 80;
    
            location / {
                limit_req zone=txtdotapi burst=4;
                proxy_pass http://127.0.0.1:8070;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
            }
    
            server_name txtdot.deep-swarm.xyz txtdot.dschanlrufh4hvwygr65e7sathicyp5fce4ypuzizath36372ag6jxyd.onion ;
            listen 4447;
            listen [::]:4447;
    
    }

    Change the proxy_pass port to what you specify on your docker-compose.yml, this line:
    8087:8080
    And 4447 is tor port configured on /etc/tor/torrc:
    HiddenServicePort 443 127.0.0.1:4447
    So this is how a tor subdomain configured. I managed to do so several months ago but never write a guide like this.

    If it does not work, try systemctl restart nginx.service and systemctl restart tor.service several times (reasonable restart after changing the config…).