NeoDB

1y

Drop <a href="/tags/626/" rel="tag">#626</a> (2025-03-24): Monday Morning Grab BagDjot; Bean CMS; The GitHub ⭐️ Clean Slate Protocol(Two missed Drops due to a week of brutal and Constitution-destroying EOs, the launch of a <a href="https://47-watch.com/blog/posts/2025/2025-03-23-trump-administration-week-9/" rel="nofollow">47 Watch podcast</a>, work on a — for now — seekrit datavis collaboration with an amazing human, and the last couple days before shunting <a href="/tags/4/" rel="tag">#4</a> back up to UMaine.)Technically, this is only a grab bag due to the last section. The first two are joined at the hip, and now I have a fairly strong urge to build an R package for the resource in the first section.<a href="https://dailydrop.hrbrmstr.dev/?post_type=post&p=139505135" rel="nofollow">Subscribe</a>TL;DR(This is an AI-generated summary of today’s Drop using Ollama + llama 3.2 and a custom prompt.)Djot is a markup language that builds on CommonMark’s foundation with improved syntax and parsing, offering features like definition lists, footnotes, tables, and arbitrary attributes while parsing in linear time without backtracking (<a href="https://djot.net" rel="nofollow">https://djot.net</a>). Bean CMS is a minimal content management system built with redbean that stores posts, users, and session information in local SQLite files, providing a spartan but functional interface for content management (<a href="https://github.com/kevinfiol/beancms" rel="nofollow">https://github.com/kevinfiol/beancms</a>). The GitHub Star Clean Slate Protocol suggests removing all GitHub stars to avoid spammy solicitations, using a simple one-liner provided in the last section.Djot<a href="https://djot.net" rel="nofollow">Djot</a> (<a href="https://github.com/jgm/djot" rel="nofollow">GH</a>) is a markup language that tries to do what Markdown never quite pulled off: be simple and precise. It builds on <a href="https://github.com/commonmark" rel="nofollow">CommonMark</a>’s foundation, but smooths out the edges—both in terms of syntax and the way it gets parsed. Djot grew out of John MacFarlane’s essay <a href="https://johnmacfarlane.net/beyond-markdown.html" rel="nofollow">Beyond Markdown</a>, and it reads like a direct response to the awkward corners and performance issues that have haunted Markdown from the start.Right out of the box, Djot supports some things you’d expect from a grown-up markup language in 2025, like:definition lists footnotes tables extra inline formatting (insertions, deletions, highlights, superscript, subscript) math support smart punctuation block and inline containers arbitrary attributes on anythingThese are things Markdown always made you hack around or just skip entirely.Djot’s design is built around a few core ideas that fix longstanding problems with Markdown parsing:it parses in linear time, which means it doesn’t waste cycles trying to guess context or backtrack like CommonMark sometimes does it also parses inline elements locally, so references and links don’t depend on random labels defined somewhere else. This makes Djot friendlier to syntax highlighters and editors that don’t want to parse an entire file just to figure out how to color one line it draws a hard line: _ means emphasis, * means strong. No more “is this italic or bold or both?” ambiguity. it is consistent: syntax behaves the same inside list items, block quotes, and anywhere else—no special rules tucked away in the corners everything can have attributes: ou can attach metadata to any element without needing special syntax extensionsThe format also tightens up a few places where Markdown has always been loose or frustrating:you can’t accidentally break paragraphs with block elements lists behave more predictably—they’re driven by indentation, not whitespace guesswork headings can span multiple lines without special rules raw HTML is opt-in, not just pass-through reference links are parsed locally and are case-sensitive, not scattered and vagueIf you want to try Djot, there’s a JavaScript implementation ready to go:$ npm install -g @djot/djot$ djot --helpYou can also find implementations in Lua, Rust, Go, Haskell, even Prolog—because of course someone did it in Prolog.If you already use pandoc, Djot fits right in. Here’s how to convert a Markdown file to Djot:$ pandoc mydoc.md -f gfm -t json | djot -f pandoc -t djot > mydoc.djAnd here’s going from Djot to a Word doc:$ djot -t pandoc mydoc.dj | pandoc -f json -s -t docx -o mydoc.docxDjot files typically use the .dj extension.The syntax isn’t locked down yet — there may be small changes as it evolves — but the core is stable, and the reference implementation in JavaScript is complete and usable right now.There’s tons more info at the README; there are Go, Rust, TypeScript and more implementations; and you can quickly get a feel for it by using <a href="https://djot.net/playground/" rel="nofollow">the playground</a> and keeping <a href="https://github.com/jgm/djot/tree/main/doc" rel="nofollow">the docs</a> handy.Bean CMSWe introduced Djot in the first section to set up this section.<a href="https://github.com/kevinfiol/beancms" rel="nofollow">Bean CMS</a> is a micro-CMS built with <a href="https://redbean.dev/" rel="nofollow">redbean</a>.A quick refresher on redbean: it is an open-source, single-file web server that runs natively on six operating systems across both AMD64 and ARM64 architectures. It’s written in ANSI C and embeds Lua 5.4, MbedTLS, and SQLite into a single executable.There is not much to “tell” about Bean CMS — it is a bare bones content management system. Posts, users, and session information is stored in local SQLite files, and images used in posts are referenced from a local directory.The binary is meant to be placed in the top-level directory where all the databases and content will be stored, so you should do sometihing like:$ cd /some/path/where/bean/content/goes$ ./beancms -D ./ -p PORT -b 127.0.0.1Config options are minimal but sufficient:Code block rendering is decent:Post editing is spartan but does what you need it to do:And, there’s even an admin panel (at /admin):It’s built on <a href="https://github.com/pkulchenko/fullmoon" rel="nofollow">fullmoon</a> — a redbean-based web framework — (which we’ll cover in some future Drop) with very readable <a href="https://github.com/kevinfiol/beancms/tree/master/src" rel="nofollow">Lua and templates files</a>.I fronted an instance of it with a Caddy reverse proxy, and you can [re]read the Djot section <a href="https://bean.hrbrmstr.app/hrbrmstr/djot" rel="nofollow">over there</a>.It appears to have been born in early December last year, and the author — <a href="https://kevinfiol.com/" rel="nofollow">Kevin Fiol</a> — started using signed commits towards the end of December (which are still spiffy, but with all the GitHub account takeovers, I’m not sure I trust anything signed-but-still-hosted-on-GitHub anymore).Kevin also has his own <a href="https://kevinfiol.com/blog/a-tour-of-beancms/" rel="nofollow">Bean ’splainer</a> up.This has tons of potential to be a personal note-taking system, especially since it’s all backed by SQLite.I’ll definitely be keeping an eye on this one.The GitHub ⭐️ Clean Slate ProtocolI whined on the socials about yet-another skeezy, spammy “Hey! I saw you [starred XYZ repo|were fond of XYZ] and wanted to let you know about this other super cool ZYZ.” unsolicited email.First off: DO NOT DO THIS NO MATTER HOW COOL YOU THINK YOUR PROJECT IS.At least do not do it to me, as you will be marked as a spammer, blocked permanently wherever I can, shunned in person, and be forced to spoon feed ketchup to Donald Trump for eternity when you leave this mortal coil.Anyway.It got a few likes, and friend-of-the-Drop Adam S. (I did not ask permission to use Adam’s handle or full name) remarked about <a href="https://github.com/tpkahlon/github-unstar" rel="nofollow">github-unstar</a> a day or so later. It’s a neat JS-based CLI tool to nuke all your GitHub stars.It honestly never occurred to me to unstar everything I had daftly starred. Adam: you are a genius!But, that tool did not work for me because it did not handle the edge case where your record of a GitHub star event has rotted due to the owner of the repo either no longer having a GitHub account, or having deleted said repo. (I keep thinking there’s a way to take malicious advantage of this condition, but it’s so niche that I will likely not spend much time noodling it.) With all their resources you’d think Microsoft would have some process to help you deal with GH star link rot, but they are woefully incompetent and lack attention to detail in so many areas, that I am not even remotely surprised they do not.Where there’s a will, there’s a Bash script, and we don’t need the bloat of an NPM package anyway if we have GitHub’s <a href="https://docs.github.com/en/github-cli/github-cli/quickstart" rel="nofollow">gh</a> utility handy (which I do since I still have to use GitHub for $WORK).You can easily get info about all your starred repos via:$ gh api --paginate user/starred'That will DoS your terminal, so perhaps you just want to see the URLs:$ gh api --paginate user/starred --jq '.[].html_url'Ideally, you’d back up all your stars (to put into some other system, like Raindrop.io) first, but you can go all Iron Man and just destroy everything:$ gh api --paginate user/starred --jq '.[].full_name' | xargs -I{} sh -c 'echo "💥 {}"; gh api -X DELETE user/starred/{}; sleep 0.5'Bye. Bye. Spammers.FINRemember, you can follow and interact with the full text of The Daily Drop’s free posts on:🐘 Mastodon via <a href="https://dailydrop.hrbrmstr.dev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dailydrop.hrbrmstr.dev</a> 🦋 Bluesky via <a href="https://bsky.app/profile/dailydrop.hrbrmstr.dev.web.brid.gy" rel="nofollow" class="ellipsis" title="bsky.app/profile/dailydrop.hrbrmstr.dev.web.brid.gy">https://bsky.app/profile/dailydrop.hrbrmstr.dev.web.brid.gy</a>Also, refer to:<a href="https://dailydrop.hrbrmstr.dev/2024/12/04/drop-565-2024-12-04-all-strings-attached/" rel="nofollow">this post</a>, and <a href="https://dailydrop.hrbrmstr.dev/2024/12/08/bonus-drop-68-2024-12-08-all-strings-attached-cli-version/" rel="nofollow">this post</a>to see how to access a regularly updated database of all the Drops with extracted links, and full-text search capability. ☮️<a href="/tags/4/" rel="tag">#4</a>

0 0 0 View Post & Replies See Original

1y

I Am The Very Modelfile Of A Modern Workflow General; The Impending ‘Reimagine’ Nightmare;We return to the semi-regular AI-foucused Drop with a quick look at how to (quickly and easily!) make a custom Ollama model to make a small, useful tool.Programming note: due to driving <a href="/tags/4/" rel="tag">#4</a> to college Friday, there may not be a Drop. But, if the round trip is not too taxing, I’ll likley get one out int he late afternoon.<a href="https://dailydrop.hrbrmstr.dev/?post_type=post&p=139503826" rel="nofollow">Subscribe</a>TL;DR(This is an AI-generated summary of today’s Drop using Sonnet via Perplexity.)A guide on creating a custom Ollama model using a Modelfile to generate concise names for CVE vulnerabilities, similar to CISA’s KEV catalog entries (<a href="https://github.com/ollama/ollama/blob/main/docs/modelfile.md" rel="nofollow" class="ellipsis" title="github.com/ollama/ollama/blob/main/docs/modelfile.md">https://github.com/ollama/ollama/blob/main/docs/modelfile.md</a>) Discussion of Google’s new Pixel 9 “Reimagine” feature, which allows users to manipulate photos using AI, raising concerns about the potential misuse of such technology (<a href="https://www.theverge.com/2024/8/21/24224084/google-pixel-9-reimagine-ai-photos" rel="nofollow" class="ellipsis" title="www.theverge.com/2024/8/21/24224084/google-pixel-9-reimagine-ai-photos">https://www.theverge.com/2024/8/21/24224084/google-pixel-9-reimagine-ai-photos</a>) Introduction to “The Inference,” a new editorial project by Danny Palmer published by Darktrace, exploring the impact of AI on cybersecurity and society (<a href="https://darktrace.com/the-inference" rel="nofollow">https://darktrace.com/the-inference</a>)I Am The Very Modelfile Of A Modern Workflow GeneralPhoto by Pixabay on <a href="https://www.pexels.com/photo/selective-focus-photography-of-cairn-stone-268018/" rel="nofollow">Pexels.com</a>Longtime readers know I’m <a href="/tags/notafan/" rel="tag">#notAFan</a> of the “Open AI tax”. TL;DR for new readers is that I believe it is yugely important to ensure everyone had access to LLM/GPT tooling. These tools/services are not going away anytime soon; and, not knowing how to work with them puts other folks at an needless advantage. Ollama does a great job helping to level the playing field.Ollama supports adding layers on top of existing models via something called a <a href="https://github.com/ollama/ollama/blob/main/docs/modelfile.md" rel="nofollow">Modelfile</a>. It’s a plain text file that lets you add in some parameters, prompts, examples, etc. so you don’t have to shunt them along with each new incantation. The format for these is, essentially:# commentINSTRUCTION argumentsSome key instructions include:FROM: Identifies the base model (mandatory) PARAMETER: Customizes model behavior through various settings TEMPLATE: Defines the prompt template sent to the model SYSTEM: Sets up system messages ADAPTER: Integrates adapters for QLoRA LICENSE: Specifies legal licenses MESSAGE: Adds preset message historiesYou can inspect the configuration of models you download and use pretty simply:$ ollama show phi:latest --modelfile# Modelfile generated by "ollama show"# To build a new Modelfile based on this, replace FROM with:# FROM phi:latestFROM /path/to/.ollama/models/blobs/sha256-04778965089b91318ad61d0995b7e44fad4b9a9f4e049d7be90932bf8812e828TEMPLATE "{{ if .System }}System: {{ .System }}{{ end }}User: {{ .Prompt }}Assistant:"SYSTEM A chat between a curious user and an artificial intelligence assistant. The assistant gives helpful answers to the user's questions.PARAMETER stop User:PARAMETER stop Assistant:PARAMETER stop System:LICENSE """MIT License … """(They work in a similar fashion to Dockerfiles.)You can <a href="https://www.pacenthink.io/post/understanding-modelfile-in-ollama/" rel="nofollow">go here</a> for a more in-depth explanation of the instructions and values. I’m just going to briefly show how to make one to solve a fun “problem”.I talk quite a bit about CISA’s <a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" rel="nofollow">Known Exploited Vulnerabilities Catalog</a> (KEV), and one nice thing the Keepers of KEV do for us is create a short name for any vulnerability they add to the catalog. CVE entries only have a longer-length description associated with their identifier, like CVE-2024-38856’s Apache OFBiz contains an incorrect authorization vulnerability that could allow remote code execution via a Groovy payload in the context of the OFBiz user process by an unauthenticated attacker.. The KEV entry for that uses the concise name of Apache OFBiz Incorrect Authorization Vulnerability, making it much easier to reference (and has way more info than just a bare CVE identifier).At $WORK, we got it into our noggins to be as kind as the KEV Keepers and associate a concise name with any CVEs we display (and for an upcoming product/API feature). There is no way we were going to lovingly hand-craft those for a few hundred thousand entries. And, I’m loathe to give any AI vendor money. So, we built a custom PHI model to do this for us! And, are sharing it with y’all right here (we’ll working on posting the CVE ids with concise to GitHub when we’re done cleaning them up).After a few iterations, here’s the Modelfile we ended up with:FROM phi:latestPARAMETER temperature 0.0PARAMETER stop "\n"PARAMETER num_predict 30PARAMETER top_p 0.95SYSTEM """You are an AI system specializing in generating concise short names for vulnerabilities described by CVEs. Your task is to convert verbose CVE descriptions into clear, descriptive titles that resemble entries in CISA's Known Exploited Vulnerabilities (KEV) catalog. Stop generating output immediately after providing the short name.PROMPT Given a CVE description, create a short name similar to those used in CISA's KEV catalog. The short name should be concise, descriptive, and highlight the affected product or vulnerability type. Do not provide additional information or explanations. The response should be under 10 words and should end immediately after the short name.Examples:CVE description: A vulnerability in the TCP/IP stack of Cisco IOS XR Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.Short name: Cisco IOS XR TCP/IP Stack DoS VulnerabilityCVE description: Microsoft Exchange Server Remote Code Execution Vulnerability. This CVE ID is unique from CVE-2021-26855, CVE-2021-26857, CVE-2021-26858, CVE-2021-27065.Short name: Microsoft Exchange Server RCE VulnerabilityNow, create a short name for this CVE:"""The temperature controls the “creativity” of the output, with 0.0 being fully deterministic. Even with that, we were getting some odd output behavior, so we added a “please stop generating” hint at when it outputs a newline, set the max number of output tokens to 30 (I may change that to 20), and asked it to only make high “next token” probability choices.Rather than muck with special tokens, I went with a basic prompt-with-few-shot-examples approach.To make our new model, we just:$ ollama create cve-shortener -f ./ModelfileThen just try it out:$ ollama run cve-shortener 'Topline Opportunity Form (aka XLS Opp form) before 2015-02-15 does not properly restrict access to database-connection strings, which allows attackers to read the cleartext version of sensitive credential and e-mail address information via unspecified vectors.'Topline Opportunity Form (XLS Opp) Database VulnerabilityLike most LLM/GPT output in API contexts, you’ll need to add some guardrails for cleaning up results or retrying the prompt. (Yes, even with all the constraints in the Modelfile, this one still borks output every so often.)On my aging Apple Silicon box, each call takes ~200-600ms, depending on the inputs and other system GPU load.If you find yourself repeating prompts, this is a lightweight way to avoid doing so. And, if you have some similar, focused tasks that need doing, getting a hand from our AI overlords can help save quite a bit of time.The Impending ‘Reimagine’ NightmarePhoto by cottonbro studio on <a href="https://www.pexels.com/photo/balloon-on-a-shattered-window-5427546/" rel="nofollow">Pexels.com</a>Super quick section, since I believe Welch’s examples say everything vs. have me blather much.Chris Welch, an editor over at The Verge, acquired one of Google’s new Pixel 9 devices and gave the new Reimagine feature a go and posted some results on <a href="https://www.threads.net/@chriswelch/post/C-8LF4BOSAP" rel="nofollow">Threads</a> and <a href="https://www.theverge.com/2024/8/21/24224084/google-pixel-9-reimagine-ai-photos" rel="nofollow">The Verge</a>. This, to me, is a pretty terrifying new capability.We’re already awash in deepfakes, photorealistic child image exploitation, advanced phishing, and shady political campaigns making it almost impossible to tell truth from fiction. The last thing we needed was to commodify this tech so anyone who can afford a certain class of portable glowing rectangles can get in on the gambit.Let’s hope the majority of uses are benign/silly.The InferenceAnother quick section, as this content also speaks for itself pretty well.<a href="https://infosec.exchange/@dannyjpalmer#." rel="nofollow">Danny Palmer</a> is an excellent writer on cybersecurity topics. He has a new editorial project that’s being published by cybersecurity vendor Darktrace (yeah, that’s “a thing” in my line of work).<a href="https://darktrace.com/the-inference" rel="nofollow">The Inference</a> explores the impact of AI on the world around us, starting within the security operations center and expanding to business and society writ large. Features on it analyze data, trends, and perspectives from experts inside and outside of Darktrace to educate and inspire readers about the role that AI plays in enabling innovation and how it can be applied safely and securely.I link to it since the first few pieces:<a href="https://darktrace.com/the-inference/ai-and-the-biggest-election-year-ever-are-we-ready" rel="nofollow">AI and the biggest election year ever – are we ready?</a> <a href="https://darktrace.com/the-inference/it-support-engineering-in-the-age-of-ai" rel="nofollow">The role of IT support engineering in the age of AI</a> <a href="https://darktrace.com/the-inference/in-conversation-with-professor-mike-woolridge" rel="nofollow">In conversation with Professor Mike Woolridge</a> <a href="https://darktrace.com/the-inference/malware-as-a-service-what-you-need-to-know" rel="nofollow">Malware-as-a-Service: what you need to know about this persistent cyber threat</a>were very well crafted, and I thought more than a few readers would want to get this into their RSS feeds.(As usual, I get nothing for Dropping a link to this post, save for providing y’all with something I found interesting.)FINRemember, you can follow and interact with the full text of The Daily Drop’s free posts on Mastodon via <a href="https://dailydrop.hrbrmstr.dev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dailydrop.hrbrmstr.dev</a> ☮️<a href="https://dailydrop.hrbrmstr.dev/2024/08/29/drop-523-2024-08-29-happy-thursdai/" rel="nofollow" class="ellipsis" title="dailydrop.hrbrmstr.dev/2024/08/29/drop-523-2024-08-29-happy-thursdai/">https://dailydrop.hrbrmstr.dev/2024/08/29/drop-523-2024-08-29-happy-thursdai/</a><a href="/tags/4/" rel="tag">#4</a>

0 0 0 View Post & Replies See Original

1y

Pipet; Need For Speed; Poisoning AI ScrapersA midweek visit to see <a href="/tags/4/" rel="tag">#4</a> means I’m still “recovering” from a total of seven hours of intraday driving. So, y’all get a potpouri of resources, today, since I’m way too tired to knit together a themed Drop.<a href="https://dailydrop.hrbrmstr.dev/?post_type=post&p=139504077" rel="nofollow">Subscribe</a>TL;DR(This is an AI-generated summary of today’s Drop using Ollama + llama 3.2 and a custom prompt.)I can report that the VS Codium plugin I made worked super well today!Pipet is a Golang-based command-line tool for web scraping and data extraction, operating in three primary modes: HTML parsing, JSON parsing, and client-side JavaScript evaluation. <a href="https://github.com/bjesus/pipet" rel="nofollow">Pipet</a> Need For Speed includes two resources: speedtest-rs (a Rust implementation of a speed test tool) and LibreSpeed (a web-based tool for measuring internet connection speeds). <a href="https://github.com/nelsonjchen/speedtest-rs" rel="nofollow">speedtest-rs</a>, <a href="https://librespeed.org/" rel="nofollow">LibreSpeed</a> Poisoning AI scrapers involves using techniques like generating garbled content deterministically and serving alternative versions to detected AI scrapers, as demonstrated by Tim McCormack’s project. <a href="https://www.brainonfire.net/blog/2024/09/19/poisoning-ai-scrapers/" rel="nofollow">Poisoning AI scrapers</a>PipetPhoto by Pixabay on <a href="https://www.pexels.com/photo/ageing-plant-357440/" rel="nofollow">Pexels.com</a><a href="https://github.com/bjesus/pipet" rel="nofollow">Pipet</a> is a net and well-thought-out Golang-based command-line tool designed for web scraping and data extraction. It operates in three primary modes: HTML parsing, JSON parsing, and client-side JavaScript evaluation. Rather than do the webops on its own, Pipet leverages existing utilities like curl and integrates seamlessly with Unix pipes, letting us extend its built-in capabilities in ways we’re all pretty much used to.Pipet can be used for various data extraction tasks, including (their words) “tracking shipments, monitoring concert ticket availability, observing stock price changes, and extracting any online information”.They have examples, but let’s make another one. This Bash script wraps around pipet to get the news headlines from BBC’s nigh plaintext “On This Day” page for the current day:#!/usr/bin/env bashtemp_file=$(mktemp)month_name=$(date +%B)cat <<EOF >"${temp_file}"curl <a href="http://news.bbc.co.uk/onthisday/low/dates/stories/$" rel="nofollow" class="ellipsis" title="news.bbc.co.uk/onthisday/low/dates/stories/$">http://news.bbc.co.uk/onthisday/low/dates/stories/$</a>{month_name,,}/$(date +%-d)/default.stma[href^="/onthisday/low/dates/stories"] spanEOFcommand pipet --json "${temp_file}" | command jq -r '.[0][0] | map(select(length > 0)) | .[]'That Pipet file will:grab the HTML target all the /onthisday links extract the text from the span elementsI feed the JSON output to jq for cleaning. Here’s a demo:$ ./on-this-day.sh1995: OJ Simpson verdict: 'Not guilty'1975: London's Spaghetti House siege ends1944: Poles surrender after Warsaw uprising1981: IRA Maze hunger strikes at an end1952: Tea rationing to end1979: Anti-racists tackle South African rugby touristsNOTE: A far more robust version of that script can be had at <a href="https://rud.is/dl/on-this-day-robust.sh" rel="nofollow" class="ellipsis" title="rud.is/dl/on-this-day-robust.sh">https://rud.is/dl/on-this-day-robust.sh</a>.The README is fairly extensive with details on how to use Pipet’s headless mode, and advanced JSON filtering mode (when the curl responses are JSON).Since I have some boilerplate Go template projects for quickly creating custom scrapers, I’m not sure I’ll be using Pipet much, but it’s definitely a neat tool that others may find useful.Need For SpeedPhoto by Pixabay on <a href="https://www.pexels.com/photo/lighted-roadside-rings-290470/" rel="nofollow">Pexels.com</a>I came across the two resources in this section:<a href="https://github.com/nelsonjchen/speedtest-rs" rel="nofollow">speedtest-rs</a> <a href="https://librespeed.org/" rel="nofollow">LibreSpeed</a> (<a href="https://github.com/librespeed/speedtest" rel="nofollow">GH</a>)after reading this post on “<a href="https://foosel.net/blog/2021-03-28-homelab-uplink-monitoring/" rel="nofollow">Homelab uplink monitoring</a>“.speedtest-rs is a Rust implementation of a tool similar to the popular Python speedtest-cli, designed to measure internet connection speeds. The project was originally a learning exercise for the author to explore Rust and its ecosystem. It’s evolved a bit and is designed primarily for lower-end residential connections using “<a href="https://web.archive.org/web/20161109011118/http://www.ookla.com/support/a84541858" rel="nofollow">HTTP Legacy Fallback</a>“.Here’s a run from my pseudo-high bandwidth abode:$ ./speedtest-rsRetrieving speedtest.net configuration...Retrieving speedtest.net server list...Testing from Comcast Cable (37.141.13.125)...Selecting best server based on latency...Hosted by Optimum Online (White Plains, NY) [272.08 km]: 31.164 msTesting download speed..............Download: 503.23 Mbit/sTesting upload speed..............Upload: 39.62 Mbit/sWARNING: This tool may not be accurate for high bandwidth connections! Consider using a socket-based client alternative.(Ookla, the company behind speedtest.net, has their own non-FOSS CLI tool that’s native and available for many platforms. It’s TCP-based and capable of handling higher bandwidths. While not open-source, it’s supported by Ookla and can be used for non-commercial purposes.)LibreSpeed is a web-based tool that provides a simple and straightforward way to measure internet connection speeds. It’s designed to be easy to use and provides a clear and concise interface for folks to view their internet connection speeds. It’s self-hostable (with very minimal requirements) and has its own <a href="https://github.com/librespeed/speedtest-cli" rel="nofollow">CLI</a> tool as well.Poisoning AI Scrapers(I had to sneak one ThursdAI post in here.)Our AI overlords are <a href="https://www.tanayj.com/p/openai-and-anthropic-revenue-breakdown" rel="nofollow">raking in billions</a> (but are all still losing money whilst also killing the planet because that’s how late stage capitalism “works”). While I have yet to finish deploying a network of “tarpits” designed to slow down and poison AI scrapers, Tim McCormack has gone and done it!In “<a href="https://www.brainonfire.net/blog/2024/09/19/poisoning-ai-scrapers/" rel="nofollow">Poisoning AI scrapers</a>“, Tim covers his path towards a project to deter AI companies from using his blog content for training large language models without permission. To achieve this, he implements a system that serves garbled versions of his blog posts to detected AI scrapers.His approach involves several components. First, for content generation, he uses a <a href="https://en.wikipedia.org/wiki/Dissociated_press" rel="nofollow">Dissociated Press</a> algorithm implemented in Rust to generate nonsensical content that looks superficially normal. The algorithm takes the original blog post as input and produces garbled text while maintaining some structural elements.For content storage, the system generates an alternative version of each blog post (named “swill.alt.html“) and stores this alongside the regular post content. Scraper detection and content serving is handled using Apache httpd .htaccess rules with mod_rewrite to detect AI scrapers based on User-Agent strings. When a scraper is detected, the server serves the garbled “swill” version instead of the real content.Key aspects of the system includes generating garbled content deterministically using the post’s SHA256 hash as a seed, regenerating alternative content only for draft posts to maintain stable “swill” versions for published posts, and excluding comments from the garbled versions to avoid associating others’ names with nonsensical content.Tim ACKs that this approach alone won’t significantly impact LLM training. However, he sees it as a fun exercise, a way to practice programming skills, and potentially an inspiration for others to implement similar measures. The post concludes by inviting discussion on alternative technical approaches and other poisoning techniques, while discouraging broader debates about AI ethics or the merits of LLMs.FINRemember, you can follow and interact with the full text of The Daily Drop’s free posts on Mastodon via <a href="https://dailydrop.hrbrmstr.dev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dailydrop.hrbrmstr.dev</a> ☮️<a href="https://dailydrop.hrbrmstr.dev/2024/10/03/drop-539-2024-10-01-toss-up-thursday/" rel="nofollow" class="ellipsis" title="dailydrop.hrbrmstr.dev/2024/10/03/drop-539-2024-10-01-toss-up-thursday/">https://dailydrop.hrbrmstr.dev/2024/10/03/drop-539-2024-10-01-toss-up-thursday/</a><a href="/tags/4/" rel="tag">#4</a>

Edited 1y ago

0 0 0 View Post & Replies See Original

1y

Death of Piro <a href="/tags/4/" rel="tag">#4</a> is out <a href="http://stanleylieber.com/2025/03/04/0/" rel="nofollow" class="ellipsis" title="stanleylieber.com/2025/03/04/0/">http://stanleylieber.com/2025/03/04/0/</a>

0 0 0 View Post & Replies See Original

242d

读过 <a href="https://neodb.social/search?r=1&q=https://neodb.social/book/25QidPlYhi9dGXY61LrbpO" rel="nofollow">Fantastic Four by Ryan North Vol. 1: Whatever Happened to the Fantastic Four?</a> 🌕🌕🌕🌕🌑 <a href="/tags/1/" rel="tag">#1</a>-3特别棒，<a href="/tags/4/" rel="tag">#4</a>-6稍微逊色一些，但整体还是很好看、很抓人，非常适合作为starting point来看

0 0 0 View Post & Replies