home.social

#expire — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #expire, aggregated by home.social.

  1. 🐘 Mastodon Account Archives 🐘

    TL;DR Sometimes mastodon account backup archive downloads fail to download via browser, but will do so via fetch with some flags in the terminal. YMMV.

    the following are notes from recent efforts to get around browser errors while downloading an account archive link.

    yes, surely most will not encounter this issue, and that's fine. there's no need to add a "works fine for me", so this does not apply to your situation, and that's fine too. however, if one does encounter browser errors (there were several unique ones and I don't feel like finding them in the logs).

    moving on... some experimentation with discarding the majority of the URL's dynamic parameters, I have it working on the cli as follows:

    » \fetch -4 -A -a -F -R -r --buffer-size=512384 --no-tlsv1 -v ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256

    the primary download URL (everything before the query initiator "?" has been substituted as ${URL_PRE_QMARK}, and then I only included Amazon's algo params, the rest of the URL (especially including the "expire" tag) seems to be unnecessary.

    IIRC the reasoning there is about the CDN's method for defaulting to a computationally inexpensive front-line cache management, where the expire aspects are embedded in the URL instead of internal (to the CDN clusters) metrics lookups for cache expiration.

    shorter version: dropping all of the params except the hash algo will initiate a fresh zero-cached hit at the edge, though likely that has been cached on second/non-edge layer due to my incessent requests after giving up on the browser downloads.

    increasing the buffer size and forcing ipv4 are helpful for some manner of firewall rules that are on my router side, which may or may not be of benefit to others.

    - Archive directory aspect of URL: https://${SERVER}/${MASTO_DIR}/backups/dumps/${TRIPLE_LAYER_SUBDIRS}/original/
    - Archive filename: archive-${FILE_DATE}-{SHA384_HASH}.zip

    Command:

    » \fetch -4 -A -a -F -R -r --buffer-size=512384 --no-tlsv1 -v ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256

    Verbose output:

    resolving server address: ${SERVER}:443
    SSL options: 86004850
    Peer verification enabled
    Using OpenSSL default CA cert file and path
    Verify hostname
    TLSv1.3 connection established using TLS_AES_256_GCM_SHA384
    Certificate subject: /CN=${SEVER}
    Certificate issuer: /C=US/O=Let's Encrypt/CN=E5
    requesting ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256
    remote size / mtime: ${FILE_SIZE} / 1742465117
    archive-${FILE_DATE}-{SHA384_HASH}.zip 96 MB 2518 kBps 40s

    @stefano looks to be working now :)

    #mastodon #freebsd #terminal #cli #cdn #cache #expire

  2. Let's Encrypt 終止 e-mail 通知到期的服務

    之前如果在申請 Let's Encrypt 時有將 e-mail 填寫進去的話 (大多數人應該沒填),Let's Encrypt 會在快要到期的時候寄信給你。而 Let's Encrypt 打算終止這個服務:「Endin

    blog.gslin.org/archives/2025/0

    #Computer #Mail #Murmuring #Network #Security #Service #certificate #email #email #end #expiration #expire #letsencrypt #mail #notification #of #security #ssl #support #tls

  3. The fire crackled. Colorful flames danced hypnotically. Sparks traveled up into the air, vanishing into the smoke. Every so often the fire would pop, casting glowing embers out to #expire on the ground. As the fire died down, I added a few more pieces of wood and roused the fire up again.

    #wss366

  4. Bullish Bitcoin traders better positioned for Friday’s $5.5B options expiry - Bullish Bitcoin options traders expect a hefty profit from Friday’s expi... - cointelegraph.com/news/bullish #bankrupt #markets #genesis #germany #options #deribit #expiry #expire #sale #sell #call #put #okx

  5. @simon

    #Domains #expire, but you can always renew them. You don't know if any given corporation will even exist, much less be offering the same hosting services, in a year.

    My recommendation would be using a static site generator to produce HTML output. Serve that with any webserver from any hosting solution (dedicated box in a datacenter, shared hosting service, Raspberry Pi server in your basement) on domains you own and control, and have multiple backups/redundant serving solutions.