toad.social

UK<a href="https://www.europesays.com/uk/317426/" rel="nofollow noopener" translate="no" target="_blank">https://www.europesays.com/uk/317426/</a> Lone Design Club launches new Cache pop-up concept at Bristol’s Cabot Circus <a href="https://pubeurope.com/tags/Bristol" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bristol</a> <a href="https://pubeurope.com/tags/Britain" class="mention hashtag" rel="nofollow noopener" target="_blank">#Britain</a> <a href="https://pubeurope.com/tags/Cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cache</a> <a href="https://pubeurope.com/tags/England" class="mention hashtag" rel="nofollow noopener" target="_blank">#England</a> <a href="https://pubeurope.com/tags/GreatBritain" class="mention hashtag" rel="nofollow noopener" target="_blank">#GreatBritain</a> <a href="https://pubeurope.com/tags/LoneDesignClub" class="mention hashtag" rel="nofollow noopener" target="_blank">#LoneDesignClub</a> <a href="https://pubeurope.com/tags/UK" class="mention hashtag" rel="nofollow noopener" target="_blank">#UK</a> <a href="https://pubeurope.com/tags/UnitedKingdom" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitedKingdom</a>

kapierstau <a class="hashtag" href="https://kowelenz.social/tag/google" rel="nofollow noopener" target="_blank">#Google</a> macht <a class="hashtag" href="https://kowelenz.social/tag/invidious" rel="nofollow noopener" target="_blank">#Invidious</a> durch immer neue Änderungen das Leben schwer. Das ewige hin und her dürfte auch die Betreiber ziemlich nerven, nicht nur User wie mich. Habe weder die <a class="hashtag" href="https://kowelenz.social/tag/hoffnung" rel="nofollow noopener" target="_blank">#Hoffnung</a> noch die <a class="hashtag" href="https://kowelenz.social/tag/erwartung" rel="nofollow noopener" target="_blank">#Erwartung</a>, dass das <a class="hashtag" href="https://kowelenz.social/tag/produkt" rel="nofollow noopener" target="_blank">#Produkt</a> <a class="hashtag" href="https://kowelenz.social/tag/youtube" rel="nofollow noopener" target="_blank">#Youtube</a> sich dahingehend in eine (in meinen Augen) "vernünftigere" Richtung entwickelt. Was ich trotzdem nicht verstehe: Sollten (auch) Sperren der Grund dafür sein, dass alternative Frontends zeitweise nicht mehr funktionieren, wäre es nicht einfacher keine <a class="hashtag" href="https://kowelenz.social/tag/ipv4" rel="nofollow noopener" target="_blank">#IPv4</a>-Adressen mehr zu verwenden? Bei der größeren Menge verfügbarer <a class="hashtag" href="https://kowelenz.social/tag/ipv6" rel="nofollow noopener" target="_blank">#IPv6</a>-Adressen dürfte <a class="hashtag" href="https://kowelenz.social/tag/alphabet" rel="nofollow noopener" target="_blank">#Alphabet</a> es doch schwer haben ganze Bereiche zu sperren ohne versehentlich echte User ihrer <a class="hashtag" href="https://kowelenz.social/tag/plattform" rel="nofollow noopener" target="_blank">#Plattform</a> auszuschließen oder vorauszusehen, welche in Zukunft hinter der <a class="hashtag" href="https://kowelenz.social/tag/domain" rel="nofollow noopener" target="_blank">#Domain</a> einer <a class="hashtag" href="https://kowelenz.social/tag/instanz" rel="nofollow noopener" target="_blank">#Instanz</a> steckt? Außerdem ist schätzungsweise der Wechsel für die Betreiber deutlich zügiger und unkomplizierter möglich und User können ohne Einträge im <a class="hashtag" href="https://kowelenz.social/tag/cache" rel="nofollow noopener" target="_blank">#Cache</a> ihres <a class="hashtag" href="https://kowelenz.social/tag/dns" rel="nofollow noopener" target="_blank">#DNS</a> auch fast lückenlos weiter "vernünftiger" YouTube-exklusive Inhalte konsumieren.

Brad L. :verified:There's a lot talk about "ZeroDisk" infrastructure backed by S3. The pitch is "move your data from locally attached NVMe storage to S3 and your applications will scale easier and be more performant!"Maybe I'm getting too old for this shit, but I swear to dog this is the 4th such cycle in my career:1. NFS 2. iSCSI / Fibrechannel 3. Hadoop / HDFS 4. ZeroDisk with S3Am I the only one that's like: "wait, move TBs of data to S3 from NVMe to increase performance? Are you high?"It doesn't work, so you scale up. Now you're back to local NVMe "cache disks" running instances as expensive as the locally attached NVMe instances when you add those costs to your S3 bill. The performance is worse because of course it is.It always comes back to the two hard problems in computer science: naming things, cache invalidation, and off-by-one errors. 😂 <a href="https://hachyderm.io/tags/zerodisk" class="mention hashtag" rel="nofollow noopener" target="_blank">#zerodisk</a> <a href="https://hachyderm.io/tags/s3" class="mention hashtag" rel="nofollow noopener" target="_blank">#s3</a> <a href="https://hachyderm.io/tags/hadoop" class="mention hashtag" rel="nofollow noopener" target="_blank">#hadoop</a> <a href="https://hachyderm.io/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://hachyderm.io/tags/datalake" class="mention hashtag" rel="nofollow noopener" target="_blank">#datalake</a> <a href="https://hachyderm.io/tags/GetOffMyLawn" class="mention hashtag" rel="nofollow noopener" target="_blank">#GetOffMyLawn</a>

.:\dGh/:.Eventually tagging cache will have to come back to <a href="https://mastodon.social/tags/Laravel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laravel</a> sooner or later.What about trying to re-implement it in time for Laravel 13? That would mean to depend on Symfony Cache.<a href="https://symfony.com/doc/current/cache.html#cache-using-cache-tags" rel="nofollow noopener" translate="no" target="_blank">https://symfony.com/doc/current/cache.html#cache-using-cache-tags</a><a href="https://mastodon.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://mastodon.social/tags/Cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cache</a> <a href="https://mastodon.social/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> <a href="https://mastodon.social/tags/Memcache" class="mention hashtag" rel="nofollow noopener" target="_blank">#Memcache</a> <a href="https://mastodon.social/tags/Memcached" class="mention hashtag" rel="nofollow noopener" target="_blank">#Memcached</a> <a href="https://mastodon.social/tags/Valkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valkey</a> <a href="https://mastodon.social/tags/Dragonfly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dragonfly</a> <a href="https://mastodon.social/tags/KeyDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#KeyDB</a> <a href="https://mastodon.social/tags/SQLlite" class="mention hashtag" rel="nofollow noopener" target="_blank">#SQLlite</a> <a href="https://mastodon.social/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://mastodon.social/tags/Code" class="mention hashtag" rel="nofollow noopener" target="_blank">#Code</a> <a href="https://mastodon.social/tags/Symfony" class="mention hashtag" rel="nofollow noopener" target="_blank">#Symfony</a>

gary<a href="https://infosec.exchange/@kajer" class="u-url mention" rel="nofollow noopener" target="_blank">@kajer</a> well it will be interesting going fwd what you do with new capabilities <a href="https://infosec.exchange/tags/buffer" class="mention hashtag" rel="nofollow noopener" target="_blank">#buffer</a> <a href="https://infosec.exchange/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://infosec.exchange/tags/live" class="mention hashtag" rel="nofollow noopener" target="_blank">#live</a> persistence

robrich<a href="https://gist.github.com/StephenCleary/39a2cd0aa3c705a984a4dbbea8275fe9" rel="nofollow noopener" translate="no" target="_blank">https://gist.github.com/StephenCleary/39a2cd0aa3c705a984a4dbbea8275fe9</a> - a <a href="https://hachyderm.io/tags/dotNET" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotNET</a> <a href="https://hachyderm.io/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a> <a href="https://hachyderm.io/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> class. Nice solution Stephen Cleary.

EpiphytAfter I published a recent article where I showed how to mitigate an accidental DDoS after enabling ActivityPub for WordPress with the Surge plugin, I found an optimization for improved cache handling. Out of the box, there’s a problem with the default configuration since Surge ignores the Accept header. […]<a href="https://epiph.yt/en/blog/2025/optimize-surge-configuration-for-activitypub/" rel="nofollow noopener" translate="no" target="_blank">https://epiph.yt/en/blog/2025/optimize-surge-configuration-for-activitypub/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/activitypub/" target="_blank">#ActivityPub</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/cache/" target="_blank">#Cache</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/ddos/" target="_blank">#DDoS</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/plugin/" target="_blank">#Plugin</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/surge/" target="_blank">#Surge</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/wordpress/" target="_blank">#WordPress</a>

Teodor Sandu<a href="https://mastodon.online/tags/fun" class="mention hashtag" rel="nofollow noopener" target="_blank">#fun</a> <a href="https://mastodon.online/tags/meme" class="mention hashtag" rel="nofollow noopener" target="_blank">#meme</a> <a href="https://mastodon.online/tags/it" class="mention hashtag" rel="nofollow noopener" target="_blank">#it</a> <a href="https://mastodon.online/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://mastodon.online/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a> <a href="https://mastodon.online/tags/browsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#browsing</a> <a href="https://mastodon.online/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://mastodon.online/tags/funny" class="mention hashtag" rel="nofollow noopener" target="_blank">#funny</a> <a href="https://mastodon.online/tags/memes" class="mention hashtag" rel="nofollow noopener" target="_blank">#memes</a> <a href="https://mastodon.online/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mastodon.online/tags/webcomic" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomic</a> <a href="https://mastodon.online/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://mastodon.online/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://mastodon.online/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#network</a>

Eva Winterschön🐘 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-SHA256the 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}.zipCommand: » \fetch -4 -A -a -F -R -r --buffer-size=512384 --no-tlsv1 -v ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256Verbose 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<a href="https://mastodon.bsd.cafe/@stefano" class="u-url mention" rel="nofollow noopener" target="_blank">@stefano</a> looks to be working now :) <a href="https://mastodon.bsd.cafe/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a> <a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> <a href="https://mastodon.bsd.cafe/tags/terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#terminal</a> <a href="https://mastodon.bsd.cafe/tags/cli" class="mention hashtag" rel="nofollow noopener" target="_blank">#cli</a> <a href="https://mastodon.bsd.cafe/tags/cdn" class="mention hashtag" rel="nofollow noopener" target="_blank">#cdn</a> <a href="https://mastodon.bsd.cafe/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://mastodon.bsd.cafe/tags/expire" class="mention hashtag" rel="nofollow noopener" target="_blank">#expire</a>

Łukasz HorodeckiEch kurde. Właśnie odkryłem, że plugin od cache psuje mi wyświetlanie map na blogu. Gdy jestem zalogowany widzę na mapie wszystkie markery POI, profil wysokości trasy i mam możliwość pobrania pliku gpx, ale bez logowania jest tylko mapa z narysowaną trasą.Znowu trzeba będzie dłubać, albo wyłączyć keszowanie całkiem, bo i tak nie ratuje bloga przed FediDDoS-em, a cała reszta ruchu jest znikoma.<a href="https://pol.social/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> <a href="https://pol.social/tags/wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#wordpress</a> <a href="https://pol.social/tags/leaflet" class="mention hashtag" rel="nofollow noopener" target="_blank">#leaflet</a> <a href="https://pol.social/tags/wtyczka" class="mention hashtag" rel="nofollow noopener" target="_blank">#wtyczka</a> <a href="https://pol.social/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a>

K@rsten :verified_gay:Die <a href="https://m.k-behrens.de/tags/Medien" class="mention hashtag" rel="nofollow noopener" target="_blank">#Medien</a> im <a href="https://m.k-behrens.de/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> <a href="https://m.k-behrens.de/tags/Cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cache</a> steigen jeden Tag um ungefähr 10 GB an, um dann nachts wieder gelöscht zu werden :mastolol:

Anthony (Toni) Tomkins 🏳️‍🌈If you are in Northern Utah, consider checking out the Bear River Region LGBTQ+ Community Coalition. It is a group of LGBTQ+ people and allies dedicated to improving the well-being for LGBTQ+ people in Northern Utah.<a href="https://mastodon.social/tags/lgbtq" class="mention hashtag" rel="nofollow noopener" target="_blank">#lgbtq</a>+ <a href="https://mastodon.social/tags/utah" class="mention hashtag" rel="nofollow noopener" target="_blank">#utah</a> <a href="https://mastodon.social/tags/lgbt" class="mention hashtag" rel="nofollow noopener" target="_blank">#lgbt</a> <a href="https://mastodon.social/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://mastodon.social/tags/boxelder" class="mention hashtag" rel="nofollow noopener" target="_blank">#boxelder</a> <a href="https://mastodon.social/tags/bearriver" class="mention hashtag" rel="nofollow noopener" target="_blank">#bearriver</a>BRR LGBTQ+ Community Coalition www.brrlgbtqcommunitycoalition.org

Crazy-to-Bike<a href="https://federation.network/@PuschyMTB" class="u-url mention" rel="nofollow noopener" target="_blank">@PuschyMTB@federation.network</a> Wenn man manches davon braucht, will oder wie auch immer: Das Meiste der genannten Beispiele kann man statt mit deren <a href="https://fediworld.de/tags/App" rel="nofollow noopener" target="_blank">#App</a> auch im <a href="https://fediworld.de/tags/Browser" rel="nofollow noopener" target="_blank">#Browser</a> nutzen. Dem <a href="https://fediworld.de/tags/Firefox" rel="nofollow noopener" target="_blank">#Firefox</a> gibt man keinen Zugriff auf <a href="https://fediworld.de/tags/Standort" rel="nofollow noopener" target="_blank">#Standort</a> etc. , setzt entsprechende <a href="https://fediworld.de/tags/Datenschutzeinstellungen" rel="nofollow noopener" target="_blank">#Datenschutzeinstellungen</a>, arbeitet im privaten Modus, löscht bei jedem Schließen <a href="https://fediworld.de/tags/Cache" rel="nofollow noopener" target="_blank">#Cache</a> und <a href="https://fediworld.de/tags/Cookies" rel="nofollow noopener" target="_blank">#Cookies</a> und nutzt <a href="https://fediworld.de/tags/uBlockOrigin" rel="nofollow noopener" target="_blank">#uBlockOrigin</a> u.a. <a href="https://fediworld.de/tags/Addons" rel="nofollow noopener" target="_blank">#Addons</a>. Standort u.ä. aktiviert man eh nicht dauerhaft am <a href="https://fediworld.de/tags/Smartphone" rel="nofollow noopener" target="_blank">#Smartphone</a>. Dann ist das <a href="https://fediworld.de/tags/Tracking" rel="nofollow noopener" target="_blank">#Tracking</a> zumindest sehr deutlich reduziert. <a href="https://fediworld.de/tags/Datenschutz" rel="nofollow noopener" target="_blank">#Datenschutz</a> <a href="https://fediworld.de/tags/TeamDatenschutz" rel="nofollow noopener" target="_blank">#TeamDatenschutz</a>

ReesA COAST Module For My Pentium 100<a href="https://makertube.net/videos/watch/43d97776-d9e9-4608-9bfa-e2e1aae2e7fe" rel="nofollow noopener" translate="no" target="_blank">https://makertube.net/videos/watch/43d97776-d9e9-4608-9bfa-e2e1aae2e7fe</a>

David Bisset"A quick <a href="https://phpc.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener" target="_blank">#WordPress</a> Super Cache fix"<a href="https://www.phpied.com/a-quick-wordpress-super-cache-fix/" rel="nofollow noopener" translate="no" target="_blank">https://www.phpied.com/a-quick-wordpress-super-cache-fix/</a> <a href="https://phpc.social/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a>

Łukasz HorodeckiPo tym jak przy ostatnich publikacjach na blogu, serwer dławił się na jakiś czas (najprawdopodobniej przez federację), wymieniłem plugin od cache z WP Super Cache na podobno lepszy LS Cache, licząc że dzięki temu żądania z instancji fedi pobierających kartę podglądu dla wpisu nie zamulą mi strony. Rzeczywiście strona po wymianie pluginu śmigała żwawo, więc miałem nadzieję, że przy następnej publikacji będzie dobrze, ale gdy przyszło co do czego, to okazało się, że niestety nic to nie dało.Pogrzebałbym teraz, ale panel też zwraca 500 i 503. Trzeba przeczekać napór i poszukać rozwiązania później.<a href="https://pol.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener" target="_blank">#WordPress</a> <a href="https://pol.social/tags/ActvityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActvityPub</a> <a href="https://pol.social/tags/Cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cache</a> <a href="https://pol.social/tags/LSCache" class="mention hashtag" rel="nofollow noopener" target="_blank">#LSCache</a> <a href="https://pol.social/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> <a href="https://pol.social/tags/fediwers" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediwers</a>

ThreeDollarBill<a href="https://mstdn.ca/tags/Cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cache</a> Creek vicinity (near Mcabee Fossil Beds),sagebrush rangeland, stiched pano, British Columbia, BC, Canada. <a href="https://mstdn.ca/tags/BC" class="mention hashtag" rel="nofollow noopener" target="_blank">#BC</a> <a href="https://mstdn.ca/tags/BritishColumbia" class="mention hashtag" rel="nofollow noopener" target="_blank">#BritishColumbia</a> <a href="https://mstdn.ca/tags/Canada" class="mention hashtag" rel="nofollow noopener" target="_blank">#Canada</a> <a href="https://mstdn.ca/tags/landscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#landscape</a> <a href="https://mstdn.ca/tags/photography" class="mention hashtag" rel="nofollow noopener" target="_blank">#photography</a>

Barry SchwartzBing has also officially dropped the cache link from its search results <a href="https://www.seroundtable.com/bing-drops-cache-link-officially-38566.html" rel="nofollow noopener" translate="no" target="_blank">https://www.seroundtable.com/bing-drops-cache-link-officially-38566.html</a><a href="https://c.im/tags/bing" class="mention hashtag" rel="nofollow noopener" target="_blank">#bing</a> <a href="https://c.im/tags/microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#microsoft</a> <a href="https://c.im/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://c.im/tags/bingseo" class="mention hashtag" rel="nofollow noopener" target="_blank">#bingseo</a> <a href="https://c.im/tags/seo" class="mention hashtag" rel="nofollow noopener" target="_blank">#seo</a>

EllieDespite the <a href="https://ellieayla.net/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a> media <a href="https://ellieayla.net/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> duration option being set to 14 (now 7) days, system/cache/accounts/ is 50gb. Blegh. Are there really that many different people tooting on my timeline?$ du -sh * 18G avatars 36G headers`tootctl media remove-orphans` cleared only 77MB.`tootctl media remove --prune-profiles --days 90 --dry-run` claims to remove 36GB. That's all strangers I haven't fingered in more than 3 months? So retoots/boosts/replies/etc? <a href="https://ellieayla.net/tags/meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#meta</a>

onionThe storage usage of <a href="https://mastodon.tal.org/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a> media caching is getting out of hand, even with quite aggressive cleaning (and pretty much single user instance). There should be options to adjust how much prefetching, if at all is done. It's a waste of both bandwidth (most of it is never seen by me anyway) and storage. <a href="https://mastodon.tal.org/tags/cache" class="mention hashtag" rel="nofollow noopener" target="_blank">#cache</a> <a href="https://github.com/mastodon/mastodon/issues/15195" rel="nofollow noopener" target="_blank">https://github.com/mastodon/mastodon/issues/15195</a>

Recent searches

Search options

Administered by:

Server stats:

#Cache