eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

218
active users

#Cache

0 posts0 participants0 posts today
Epiphyt<p>After 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.</p><p> […]</p><p><a href="https://epiph.yt/en/blog/2025/optimize-surge-configuration-for-activitypub/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">epiph.yt/en/blog/2025/optimize</span><span class="invisible">-surge-configuration-for-activitypub/</span></a></p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/activitypub/" target="_blank">#ActivityPub</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/cache/" target="_blank">#Cache</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/ddos/" target="_blank">#DDoS</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/plugin/" target="_blank">#Plugin</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/surge/" target="_blank">#Surge</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://epiph.yt/en/blog/tag/wordpress/" target="_blank">#WordPress</a></p>
Eva Winterschön<p>🐘 Mastodon Account Archives 🐘</p><p>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.</p><p>the following are notes from recent efforts to get around browser errors while downloading an account archive link. </p><p>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). </p><p>moving on... some experimentation with discarding the majority of the URL's dynamic parameters, I have it working on the cli as follows:</p><p>» \fetch -4 -A -a -F -R -r --buffer-size=512384 --no-tlsv1 -v ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256</p><p>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. </p><p>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.</p><p>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. </p><p>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.</p><p>- Archive directory aspect of URL: https://${SERVER}/${MASTO_DIR}/backups/dumps/${TRIPLE_LAYER_SUBDIRS}/original/<br>- Archive filename: archive-${FILE_DATE}-{SHA384_HASH}.zip</p><p>Command: </p><p>» \fetch -4 -A -a -F -R -r --buffer-size=512384 --no-tlsv1 -v ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256</p><p>Verbose output:</p><p>resolving server address: ${SERVER}:443<br>SSL options: 86004850<br>Peer verification enabled<br>Using OpenSSL default CA cert file and path<br>Verify hostname<br>TLSv1.3 connection established using TLS_AES_256_GCM_SHA384<br>Certificate subject: /CN=${SEVER}<br>Certificate issuer: /C=US/O=Let's Encrypt/CN=E5<br>requesting ${URL_PRE_QMARK}?X-Amz-Algorithm=AWS4-HMAC-SHA256<br>remote size / mtime: ${FILE_SIZE} / 1742465117<br>archive-${FILE_DATE}-{SHA384_HASH}.zip 96 MB 2518 kBps 40s</p><p><span class="h-card" translate="no"><a href="https://mastodon.bsd.cafe/@stefano" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stefano</span></a></span> looks to be working now :) </p><p><a href="https://mastodon.bsd.cafe/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mastodon</span></a> <a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>freebsd</span></a> <a href="https://mastodon.bsd.cafe/tags/terminal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>terminal</span></a> <a href="https://mastodon.bsd.cafe/tags/cli" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cli</span></a> <a href="https://mastodon.bsd.cafe/tags/cdn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cdn</span></a> <a href="https://mastodon.bsd.cafe/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a> <a href="https://mastodon.bsd.cafe/tags/expire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>expire</span></a></p>
Łukasz Horodecki<p>Ech kurde. Właśnie odkryłem, że plugin od cache psuje mi wyświetlanie map na blogu. </p><p>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ą.</p><p>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.</p><p><a href="https://pol.social/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>blog</span></a> <a href="https://pol.social/tags/wordpress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wordpress</span></a> <a href="https://pol.social/tags/leaflet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>leaflet</span></a> <a href="https://pol.social/tags/wtyczka" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wtyczka</span></a> <a href="https://pol.social/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a></p>
Kushal Das :python: :tor:<p>Is there any sane way to get <a href="https://toots.dgplug.org/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a> warmed up for different URLs in <a href="https://toots.dgplug.org/tags/fastly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fastly</span></a>? <a href="https://toots.dgplug.org/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTP</span></a> <a href="https://toots.dgplug.org/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>web</span></a></p>
Drupal Developer Days<p>🎤 Drupal Developer Days Leuven 2025: Speaker Spotlight Series 🎤</p><p>Join Kristiaan Van den Eynde at <a href="https://drupal.community/tags/DrupalDevDays" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DrupalDevDays</span></a> this April to understand the common caching mistakes.</p><p>💡 This session aims to inform developers about possible pitfalls, helping them avoid making common mistakes and providing some information along the way as to why these mistakes are so common and how they can mess with your site.</p><p>🎟️ Register now to secure your spot: <a href="https://www.drupalcamp.be/en/drupal-dev-days-2025/tickets" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">drupalcamp.be/en/drupal-dev-da</span><span class="invisible">ys-2025/tickets</span></a></p><p><a href="https://drupal.community/tags/DDD25" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DDD25</span></a> <a href="https://drupal.community/tags/Drupal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Drupal</span></a> <a href="https://drupal.community/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a> <a href="https://drupal.community/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a></p>
Kushal Das :python: :tor:<p>Not reading the <a href="https://toots.dgplug.org/tags/limitations" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>limitations</span></a> of <a href="https://toots.dgplug.org/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a> in <a href="https://toots.dgplug.org/tags/HAProxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HAProxy</span></a> was a mistake <a href="https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#6.1" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">haproxy.com/documentation/hapr</span><span class="invisible">oxy-configuration-manual/latest/#6.1</span></a> Should have read the documentation first.</p>
K@rsten :verified_gay:<p>Die <a href="https://m.k-behrens.de/tags/Medien" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Medien</span></a> im <a href="https://m.k-behrens.de/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a> <a href="https://m.k-behrens.de/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a> steigen jeden Tag um ungefähr 10 GB an, um dann nachts wieder gelöscht zu werden :mastolol:</p>
Jessica D Dooley<p><span class="h-card" translate="no"><a href="https://social.kernel.org/users/corbet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>corbet</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@LWN" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>LWN</span></a></span> I sympathize, it's an exasperating problem. I've found microcaching all public facing content to be extremely effective.</p><p>- The web server sits behind a proxy micro cache<br>- Preseed the cache by crawling every valid public path<br>- Configure the valid life of cached content to be as short as you want <br>- Critically, ensure that every request is always served stale cached content while the cache leisurely repopulates with a fresh copy. This eliminates bot overwhelm by decoupling requests from ANY IP from the request rate hitting the upstream<br>- Rather than blocking aggressive crawlers, configure rate-limiting customized by profiling max predicted human rate<br>- For bots with known user agents, plus those detected by profiling their traffic, divert all their requests to a duplicate long lived cache that never invokes the upstream for updates</p><p>Micro caching has saved us thousands on compute, and eliminated weekly outages caused by abusive bots. It's open to significant tuning to improve efficiency based on your content.</p><p>Shout out to the infrastructure team at NPR@flipboard.com - a blog post they published 9 years ago (now long gone) described this approach. </p><p><a href="https://infosec.exchange/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nginx</span></a> <a href="https://infosec.exchange/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a></p>
Rees<p><strong>A COAST Module For My Pentium 100</strong></p> <p><a href="https://makertube.net/videos/watch/43d97776-d9e9-4608-9bfa-e2e1aae2e7fe" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">makertube.net/videos/watch/43d</span><span class="invisible">97776-d9e9-4608-9bfa-e2e1aae2e7fe</span></a></p>
WinFuture.de<p>Das komplette <a href="https://mastodon.social/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPU</span></a>-Lineup von <a href="https://mastodon.social/tags/Intel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Intel</span></a> für die <a href="https://mastodon.social/tags/CES2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CES2025</span></a> ist bereits durchgesickert, inkl. Infos zu <a href="https://mastodon.social/tags/Takt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Takt</span></a> und <a href="https://mastodon.social/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a>. 22 <a href="https://mastodon.social/tags/Prozessor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Prozessor</span></a>-Modelle in vier verschiedenen Linien werden auf der Messe wohl vorgestellt. <a href="https://winfuture.de/news,147639.html?utm_source=Mastodon&amp;utm_medium=ManualStatus&amp;utm_campaign=SocialMedia" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">winfuture.de/news,147639.html?</span><span class="invisible">utm_source=Mastodon&amp;utm_medium=ManualStatus&amp;utm_campaign=SocialMedia</span></a></p>
Łukasz Horodecki<p>Po 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. </p><p>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.</p><p>Pogrzebałbym teraz, ale panel też zwraca 500 i 503. Trzeba przeczekać napór i poszukać rozwiązania później.</p><p><a href="https://pol.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WordPress</span></a> <a href="https://pol.social/tags/ActvityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActvityPub</span></a> <a href="https://pol.social/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a> <a href="https://pol.social/tags/LSCache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LSCache</span></a> <a href="https://pol.social/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>blog</span></a> <a href="https://pol.social/tags/fediwers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fediwers</span></a></p>
ThreeDollarBill<p><a href="https://mstdn.ca/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a> Creek vicinity (near Mcabee Fossil Beds),sagebrush rangeland, stiched pano, British Columbia, BC, Canada. <br><a href="https://mstdn.ca/tags/BC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BC</span></a> <a href="https://mstdn.ca/tags/BritishColumbia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BritishColumbia</span></a> <a href="https://mstdn.ca/tags/Canada" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Canada</span></a> <a href="https://mstdn.ca/tags/landscape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>landscape</span></a> <a href="https://mstdn.ca/tags/photography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>photography</span></a></p>
Barry Schwartz<p>Bing 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 noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">seroundtable.com/bing-drops-ca</span><span class="invisible">che-link-officially-38566.html</span></a></p><p><a href="https://c.im/tags/bing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bing</span></a> <a href="https://c.im/tags/microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microsoft</span></a> <a href="https://c.im/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a> <a href="https://c.im/tags/bingseo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bingseo</span></a> <a href="https://c.im/tags/seo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>seo</span></a></p>
Ellie<p>Despite the <a href="https://ellieayla.net/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mastodon</span></a> media <a href="https://ellieayla.net/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></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?</p><p>$ du -sh *<br>18G avatars<br>36G headers</p><p>`tootctl media remove-orphans` cleared only 77MB.</p><p>`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?</p><p> <a href="https://ellieayla.net/tags/meta" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meta</span></a></p>
onion<p>The storage usage of <a href="https://mastodon.tal.org/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mastodon</span></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 noreferrer" target="_blank">#<span>cache</span></a> </p><p><a href="https://github.com/mastodon/mastodon/issues/15195" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/mastodon/mastodon/i</span><span class="invisible">ssues/15195</span></a></p>
AmiW Streetart ❄️<p>⚪ Ein Wochenend... Lieblingsfoto. <br> 🟤 A weekend... Favorite photo.<br>📷 by Artist: <a href="https://mastodon.online/tags/%C3%89milieM%C3%B6ri" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ÉmilieMöri</span></a> / <a href="https://mastodon.online/tags/EmilieMori" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EmilieMori</span></a> in Loc.: <a href="https://mastodon.online/tags/Paris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Paris</span></a> France 🇨🇵 03/2024 - Title: "Cache-Cache" ("Versteckspiel") - <a href="https://mastodon.online/tags/Art" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Art</span></a> <a href="https://mastodon.online/tags/Streetart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Streetart</span></a> <a href="https://mastodon.online/tags/PhotoArt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PhotoArt</span></a> <a href="https://mastodon.online/tags/Artist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Artist</span></a> <a href="https://mastodon.online/tags/Fotografie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fotografie</span></a> <a href="https://mastodon.online/tags/Photography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Photography</span></a> <a href="https://mastodon.online/tags/Weekend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Weekend</span></a> <a href="https://mastodon.online/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a> ➡️ <a href="https://mastodon.online/tags/APhotoLove" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>APhotoLove</span></a></p>
dorotaC<p>Does anyone know how to increase <a href="https://fosstodon.org/tags/audio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>audio</span></a> <a href="https://fosstodon.org/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a> size in <a href="https://fosstodon.org/tags/mpv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mpv</span></a> ?</p><p>I have:</p><p>mpv <a href="https://somafm.com/defcon130.pls" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">somafm.com/defcon130.pls</span><span class="invisible"></span></a> --cache-secs=60 --demuxer-max-bytes=4M</p><p>and the cache stays around 16s/600KB, meaning the radio stream often cuts out :/</p><p><a href="https://fosstodon.org/tags/streaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>streaming</span></a> <a href="https://fosstodon.org/tags/radio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>radio</span></a></p>
Plone<p>Thijs Feryn discusses Varnish caching in Plone <a href="https://2024.ploneconf.org/en/schedule/talks/varnish-caching-in-plone" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">2024.ploneconf.org/en/schedule</span><span class="invisible">/talks/varnish-caching-in-plone</span></a> <a href="https://plone.social/tags/ploneconf2024" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ploneconf2024</span></a> <a href="https://plone.social/tags/pythoncerrado2024" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pythoncerrado2024</span></a> <a href="https://plone.social/tags/plone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>plone</span></a> <a href="https://plone.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>python</span></a> <a href="https://plone.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://plone.social/tags/varnish" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>varnish</span></a> <a href="https://plone.social/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a> <a href="https://plone.social/tags/cookies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cookies</span></a> <a href="https://plone.social/tags/brasilia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>brasilia</span></a></p>
The FPGA Hero<p>Today, we dropped our first post in a series about designing caches. This post by <span class="h-card" translate="no"><a href="https://mastodonczech.cz/@xtrollyj00" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>xtrollyj00</span></a></span> introduces data locality, cache types, and the core concepts you'll need. By the end of the series, you'll have the knowledge to create your own high-performance cache! Read more here: <a href="https://fpgahero.com/blog/20241126-cache-1-introduction/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">fpgahero.com/blog/20241126-cac</span><span class="invisible">he-1-introduction/</span></a> <a href="https://fosstodon.org/tags/FPGA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FPGA</span></a> <a href="https://fosstodon.org/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cache</span></a></p>
WinFuture.de<p>Bald möchte <a href="https://mastodon.social/tags/Intel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Intel</span></a> neue <a href="https://mastodon.social/tags/Prozessor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Prozessor</span></a>-Modelle mit "lokalem <a href="https://mastodon.social/tags/Cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cache</span></a>" ausstatten. Der ist das Gegenstück zum 3D V-Cache von <a href="https://mastodon.social/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AMD</span></a>. Intel geht es aber nicht um den <a href="https://mastodon.social/tags/Gaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gaming</span></a>- bzw. <a href="https://mastodon.social/tags/Desktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Desktop</span></a>-Markt. Der sei zu unrentabel. <a href="https://winfuture.de/news,146818.html?utm_source=Mastodon&amp;utm_medium=ManualStatus&amp;utm_campaign=SocialMedia" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">winfuture.de/news,146818.html?</span><span class="invisible">utm_source=Mastodon&amp;utm_medium=ManualStatus&amp;utm_campaign=SocialMedia</span></a></p>