04-05 00:01 · AI,技术,HackerNews,AI
Training mRNA Language Models Across 25 Species for $165
On top of that, we don't have a clear understanding on how certain positions (conformations) of a structure affect underlying biological mechanisms.
Yes, these models can predict surprisingly accurate structures and sequences. Do we know if these outputs are biologically useful? Not quite.
This technology is amazing, don't get me wrong, but to the average person they might see this and wonder why we can't go full futurism and solve every pathology with models like these.
We've come a long way, but there's still a very very long way to go.
0.https://pubmed.ncbi.nlm.nih.gov/35318324/
1.https://www.nature.com/articles/s41586-023-06127-z
I am a structural biologist working in pharmaceutical design and this type of thing could be wildly useful (if it works).
This guy shows a lot of how it's done:https://www.youtube.com/@thethoughtemporium
Basically you can design/edit/inject custom genes into things and see real results spending on the scale of $100-$1000.
Lab strains of things tend to be extremely sensitive and not human adapted. You shouldn't study and modify human-infecting organisms in your basement anyway. While you shouldn't ignore protective equipment and proper procedure... paranoia about infecting yourself with a lab leak isn't warranted.
JEPA is going to break the whole industry :D
▸ 展开全文
04-05 00:01 · AI,技术,HackerNews,大模型,AI
Show HN: sllm – Split a GPU node with other developers, unlimited tokens
Thank you for your support.
We've decided to move away from sllm. After working on the cohort model, we're choosing to step back rather than continue operating a product that couldn't reach the scale we needed.
To everyone who signed up, reserved a slot, or followed along: thank you. It meant a lot.
— The sllm team
FAQ
Will I be charged?
No. No cohort ever reached its activation threshold, so no subscriptions were billed. Any pre-authorized amounts have been voided and will drop off your statement within a few business days.
What happens to my account and data?
Because no cohort activated, there is no API usage or generated content on file — only your account details and reservation history. We'll delete all user data within 30 days. If you'd like an earlier deletion or an export, email us at the address below.
Is there a replacement you'd recommend?
For hosted open-weight models, Together, Fireworks, and Groq all offer pay-as-you-go access to Qwen, Llama, and similar models without the cohort wait.
▸ 展开全文
04-05 00:01 · AI,技术,HackerNews,大模型,AI
LLM Wiki – example of an "idea file"
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
The idea here is different. Instead of just retrieving from raw documents at query time, the LLM incrementally builds and maintains a persistent wiki — a structured, interlinked collection of markdown files that sits between you and the raw sources. When you add a new source, the LLM doesn't just index it for later retrieval. It reads it, extracts the key information, and integrates it into the existing wiki — updating entity pages, revising topic summaries, noting where new data contradicts old claims, strengthening or challenging the evolving synthesis. The knowledge is compiled once and then kept current, not re-derived on every query.
This is the key difference: the wiki is a persistent, compounding artifact. The cross-references are already there. The contradictions have already been flagged. The synthesis already reflects everything you've read. The wiki keeps getting richer with every source you add and every question you ask.
You never (or rarely) write the wiki yourself — the LLM writes and maintains all of it. You're in charge of sourcing, exploration, and asking the right questions. The LLM does all the grunt work — the summarizing, cross-referencing, filing, and bookkeeping that makes a knowledge base actually useful over time. In practice, I have the LLM agent open on one side and Obsidian open on the other. The LLM makes edits based on our conversation, and I browse the results in real time — following links, checking the graph view, reading the updated pages. Obsidian is the IDE; the LLM is the programmer; the wiki is the codebase.
This can apply to a lot of different contexts. A few examples:
- Personal: tracking your own goals, health, psychology, self-improvement — filing journal entries, articles, podcast notes, and building up a structured picture of yourself over time.
- Research: going deep on a topic over weeks or months — reading papers, articles, reports, and incrementally building a comprehensive wiki with an evolving thesis.
- Reading a book: filing each chapter as you go, building out pages for characters, themes, plot threads, and how they connect. By the end you have a rich companion wiki. Think of fan wikis like Tolkien Gateway — thousands of interlinked pages covering characters, places, events, languages, built by a community of volunteers over years. You could build something like that personally as you read, with the LLM doing all the cross-referencing and maintenance.
- Business/team: an internal wiki maintained by LLMs, fed by Slack threads, meeting transcripts, project documents, customer calls. Possibly with humans in the loop reviewing updates. The wiki stays current because the LLM does the maintenance that no one on the team wants to do.
- Competitive analysis, due diligence, trip planning, course notes, hobby deep-dives — anything where you're accumulating knowledge over time and want it organized rather than scattered.
There are three layers:
Raw sources — your curated collection of source documents. Articles, papers, images, data files. These are immutable — the LLM reads from them but never modifies them. This is your source of truth.
The wiki — a directory of LLM-generated markdown files. Summaries, entity pages, concept pages, comparisons, an overview, a synthesis. The LLM owns this layer entirely. It creates pages, updates them when new sources arrive, maintains cross-references, and keeps everything consistent. You read it; the LLM writes it.
The schema — a document (e.g. CLAUDE.md for Claude Code or AGENTS.md for Codex) that tells the LLM how the wiki is structured, what the conventions are, and what workflows to follow when ingesting sources, answering questions, or maintaining the wiki. This is the key configuration file — it's what makes the LLM a disciplined wiki maintainer rather than a generic chatbot. You and the LLM co-evolve this over time as you figure out what works for your domain.
Ingest. You drop a new source into the raw collection and tell the LLM to process it. An example flow: the LLM reads the source, discusses key takeaways with you, writes a summary page in the wiki, updates the index, updates relevant entity and concept pa
▸ 展开全文
04-04 00:02 · AI,技术,HackerNews,AI
Run Linux containers on Android, no root required
Run Linux containers on Android — no root required.
Podroid spins up a lightweight Alpine Linux VM on your phone using QEMU and gives you a fully working Podman container runtime with a built-in serial terminal.
- arm64 Android device
- Android 14+ (API 34)
- ~150 MB free storage
- Install the APK from Releases
- Open Podroid and tap Start Podman
- Wait for boot (~20 s) — progress is shown on screen and in the notification
- Tap Open Terminal
- Run containers:
podman run --rm alpine echo hello
podman run --rm -it alpine sh
podman run -d -p 8080:80 nginx
The terminal is powered by Termux's TerminalView
with full VT100/xterm emulation wired directly to the VM's serial console.
Extra keys bar (scrollable):
ESC
TAB
SYNC
CTRL
ALT
arrows
HOME
END
PGUP
PGDN
F1–F12
-
/
|
- CTRL / ALT are sticky toggles — tap once, then press a letter
- SYNC manually pushes the terminal dimensions to the VM
- Terminal size auto-syncs on keyboard open/close so TUI apps (vim, btop, htop) render correctly
- Bell character triggers haptic feedback
Forward ports from the VM to your Android device:
- Go to Settings
- Add a rule (e.g. TCP 8080 -> 80)
- Access the service at
localhost:8080
on your phone
Rules persist across restarts and can be added or removed while the VM is running.
Android App
├── Foreground Service (keeps VM alive)
├── PodroidQemu
│ ├── libqemu-system-aarch64.so (QEMU TCG, no KVM)
│ ├── Serial stdio ←→ TerminalEmulator
│ └── QMP socket (port forwarding, VM control)
└── Alpine Linux VM
├── initramfs (read-only base layer)
├── ext4 disk (persistent overlay)
├── getty on ttyAMA0 (job control)
└── Podman + crun + netavark + slirp4netns
Boot sequence: QEMU loads vmlinuz-virt
+ initrd.img
. A two-phase init (init-podroid
) mounts a persistent ext4 disk as an overlayfs upper layer over the initramfs. Packages you install and containers you pull are written to the overlay and survive reboots.
Terminal wiring: The app cannot fork host processes, so TerminalSession
is wired to QEMU's serial I/O via reflection — keyboard input goes to QEMU stdin, QEMU stdout feeds the terminal emulator. Terminal dimensions are synced to the VM via stty
so TUI apps see the correct size.
Networking: QEMU user-mode networking (SLIRP) puts the VM at 10.0.2.15
. Port forwarding uses QEMU's hostfwd
, managed at startup via CLI args and at runtime via QMP.
Requires Docker with multi-arch support:
./docker-build-initramfs.sh
./gradlew assembleDebug
adb install -r app/build/outputs/apk/debug/app-debug.apk
Dockerfile # Multi-stage initramfs builder (Alpine aarch64)
docker-build-initramfs.sh # One-command build script
init-podroid # Custom /init for the VM
app/src/main/
├── java/com/excp/podroid/
│ ├── engine/ # QEMU lifecycle, QMP client, VM state machine
│ ├── service/ # Foreground service with boot-stage notifications
│ ├── data/repository/ # Settings + port forward persistence
│ └── ui/screens/ # Home, Terminal, Settings (Jetpack Compose)
├── jniLibs/arm64-v8a/ # Pre-built QEMU + libslirp
└── assets/ # Kernel + initramfs (generated)
- QEMU — machine emulation
- Alpine Linux — VM base
- Podman — container runtime
- Termux — terminal emulator libraries
- Limbo PC Emulator — pioneered QEMU on Android
GNU General Public License v2.0
▸ 展开全文
04-04 00:02 · AI,技术,HackerNews,AI
Iran strikes leave Amazon availability zones "hard down" in Bahrain and Dubai
Iran Strikes Leave Amazon Availability Zones “Hard Down” in Bahrain and Dubai, Per Internal AWS Communication
Amazon tells its employees to deprioritize these regions as the Iran war deals meaningful damage to its infrastructure in the Gulf.
Iranian strikes have rendered two Amazon Web Services availability zones “hard down” in Dubai and Bahrain and the company expects them to be “unavailable for an extended period,” according to internal Amazon communication reviewed by Big Technology.
Within Amazon Web Services, the strikes have rendered so much damage that employees have been advised to deprioritize both regions.
“These two regions continue to be impaired, and services should not expect to be operating with normal levels of redundancy and resiliency,” an internal memo read. “We are actively working to free and reserve as much capacity as possible in the region for customers, and services should be scaled to the minimal footprint required to support customer migration.”
Reached for comment, an Amazon spokesperson pointed Big Technology to an Amazon blog post about the disruptions. “We continue to support affected customers, helping them to migrate to alternate AWS Regions, with a large number already successfully operating their applications from other parts of the world,” the post read. “As this situation evolves, and as we have advised before, we request those with workloads in the affected regions continue to migrate to other locations.”
With the war now nearing its sixth week, Iran has made Amazon infrastructure in the Gulf an economic target and is now eyeing its peers. Amazon’s Bahrain facilities have been hit multiple times, including a Wednesday strike that caused a fire. And its facilities in the UAE also sustained multiple hits. The IRGC is threatening multiple other U.S. tech giants, including Microsoft, Google, and Apple.
Amazons infrastructure in Bahrain and Dubai each have three ‘availability zones’ or clusters of compute. Both Bahrain and Dubai have a zones that are “hard down” and and “impaired but functioning.” per the internal communication.
“We do not have a timeline for when DXB and BAH will return to normal operations,” the internal post said.
This week on Big Technology Podcast: OpenAI President Greg Brockman: AI Self-Improvement, The Superapp Bet, Path To AGI, Scaling Compute
Greg Brockman is the President and co-founder of OpenAI. Brockman joins Big Technology to discuss OpenAI’s product strategy, the rise of its coming super app, and why he believes AI is entering a new takeoff phase. Tune in to hear Brockman explain OpenAI’s bet on the GPT reasoning model tree over video generation, what the “Spud” pre-training run means for upcoming models, and why he believes AGI is 70-80% achieved. We also cover the competitive landscape, the economics behind OpenAI’s $110 billion infrastructure bet, and public skepticism toward AI. Hit play for one of the most revealing conversations yet about where AI is headed and what it means for everyone.
You can listen on Apple Podcasts, Spotify, or your podcast app of choice
Thanks again for reading. Please share Big Technology if you like it!
My book Always Day One digs into the tech giants’ inner workings, focusing on automation and culture. I’d be thrilled if you’d give it a read. You can find it here.
Join Big Technology’s Private Discord Server!
Where we’ll talk about this story, the latest in AI, the week’s podcast, and plenty more. You can sign up via the link below:
▸ 展开全文
04-04 00:02 · AI,技术,HackerNews,AI
How to Write Unmaintainable Code (1999)
How To Write Unmaintainable Code
Last updated Thursday, 18-Nov-1999 20:27:28 PDT by Roedy
Green ©1997-1999 Canadian Mind Products.
This essay is also available in Spanish.
In the interests of creating employment opportunities in the Java programming
field, I am passing on these tips from the masters on how to write code
that is so difficult to maintain, that the people who come after you will
take years to make even the simplest changes. Further, if you follow all
these rules religiously, you will even guarantee yourself a lifetime
of employment, since no one but you has a hope in hell of maintaining the
code.
General Principles
To foil the maintenance programmer, you have to understand how he thinks.
He has your giant program. He has no time to read it all, much less understand
it. He wants to rapidly find the place to make his change, make it and
get out and have no unexpected side effects from the change.
He views your code through a tube taken from the centre of a roll of
toilet paper. He can only see a tiny piece of your program at a time. You
want to make sure he can never get the big picture from doing that. You
want to make it as hard as possible for him to find the code he is looking
for. But even more important, you want to make it as awkward as possible
for him to safely ignore anything.
Specific Techniques
-
Lie in the comments. You don't have to actively lie, just fail to keep
comments as up to date with the code.
-
Pepper the code with comments like /* add 1 to i */ however, never
document wooly stuff like the overall purpose of the package or method.
-
Make sure that every method does a little bit more (or less) than its name
suggests. As a simple example, a method named
isValid(x) should
as a side effect convert x to binary and store the result in a database.
-
Use acronyms to keep the code terse. Real men never define acronyms; they
understand them genetically.
-
In the interests of efficiency, avoid encapsulation. Callers of a method
need all the external clues they can get to remind them how the method
works inside.
-
If, for example, you were writing an airline reservation system, make sure
there are at least 25 places in the code that need to be modified if you
were to add another airline. Never document where they are. People who
come after you have no business modifying your code without thoroughly
understanding every line of it.
-
In the name of efficiency, use cut/paste/clone/modify. This works much
faster than using many small reusable modules.
-
Never never put a comment on a variable. Facts about how the variable
is used, its bounds, its legal values, its implied/displayed number of
decimal points, its units of measure, its display format, its data entry
rules (e.g. total fill, must enter), when its value can be trusted etc.
should be gleaned from the procedural code. If your boss forces you to
write comments, lard method bodies with them, but never comment a variable,
not even a temporary!
-
Try to pack as much as possible into a single line. This saves the overhead
of temporary variables, and makes source files shorter by eliminating new
line characters and white space. Tip: remove all white space around operators.
Good programmers can often hit the 255 character line length limit imposed
by some editors. The bonus of long lines is that programmers who cannot
read 6 point type must scroll to view them.
-
Cd wrttn wtht vwls s mch trsr. When using abbreviations inside variable
or method names, break the boredom with several variants for the same word,
and even spell it out longhand once in while. This helps defeat those lazy
bums who use text search to understand only some aspect of your program.
Consider variant spellings as a variant on the ploy, e.g. mixing International
colour,
with American color and dude-speak
kulerz. If you spell out
names in full, there is only one possible way to spell each name. These
are too easy for the maintenance programmer to remember. Because there
are so many different ways to abbreviate a word, with abbreviations, you
can have several different variables that all have the same apparent purpose.
As an added bonus, the maintenance programmer might not even notice they
are separate variables.
-
Never use an automated source code tidier to keep your code aligned. Lobby
to have them banned them from your company on the grounds they create false
deltas in PVCS (version control tracking) or that every programmer should
have his own indenting style held forever sacrosanct for any module he
wrote. Banning them is quite easy, even though they save the millions of
keystrokes doing manual alignment and days wasted misinterpreting poorly
aligned code. Just insist that everyone use the
same tidied format,
not just for storing in the common repository, but while they are editing.
This starts an RWAR and the boss, to keep the peace, will ban automated
tidying. Without automated tidying, you are now free to accidentally
misalign the code to give the optical illu
▸ 展开全文
04-04 00:02 · AI,技术,HackerNews,AI
We replaced RAG with a virtual filesystem for our AI documentation assistant
Dens Sumesh
Engineering
Share this article
RAG is great, until it isn't.
Our assistant could only retrieve chunks of text that matched a query. If the answer lived across multiple pages, or the user needed exact syntax that didn't land in a top-K result, it was stuck. We wanted it to explore docs the way you'd explore a codebase.
Agents are converging on filesystems as their primary interface because grep
, cat
, ls
, and find
are all an agent needs. If each doc page is a file and each section is a directory, the agent can search for exact strings, read full pages, and traverse the structure on its own. We just needed a filesystem that mirrored the live docs site.
The obvious way to do this is to just give the agent a real filesystem. Most harnesses solve this by spinning up an isolated sandbox and cloning the repo. We already use sandboxes for asynchronous background agents where latency is an afterthought, but for a frontend assistant where a user is staring at a loading spinner, the approach falls apart. Our p90 session creation time (including GitHub clone and other setup) was ~46 seconds.
Beyond latency, dedicated micro-VMs for reading static documentation introduced a serious infrastructure bill:
At 850,000 conversations a month, even a minimal setup (1 vCPU, 2 GiB RAM, 5-minute session lifetime) would put us north of $70,000 a year based on Daytona's per-second sandbox pricing ($0.0504/h per vCPU, $0.0162/h per GiB RAM). Longer session times double that. (This is based on a purely naive approach, a true production workflow would probably have warm pools and container sharing, but the point still stands)
We needed the filesystem workflow to be instant and cheap, which meant rethinking the filesystem itself.
The agent doesn't need a real filesystem; it just needs the illusion of one. Our documentation was already indexed, chunked, and stored in a Chroma database to power our search, so we built ChromaFs: a virtual filesystem that intercepts UNIX commands and translates them into queries against that same database. Session creation dropped from ~46 seconds to ~100 milliseconds, and since ChromaFs reuses infrastructure we already pay for, the marginal per-conversation compute cost is zero.
ChromaFs is built on just-bash by Vercel Labs (shoutout Malte!), a TypeScript reimplementation of bash that supports grep
, cat
, ls
, find
, and cd
. just-bash exposes a pluggable IFileSystem
interface, so it handles all the parsing, piping, and flag logic while ChromaFs translates every underlying filesystem call into a Chroma query.
ChromaFs needs to know what files exist before the agent runs a single command. We store the entire file tree as a gzipped JSON document (__path_tree__
) inside the Chroma collection:
{
"auth/oauth": { "isPublic": true, "groups": [] },
"auth/api-keys": { "isPublic": true, "groups": [] },
"internal/billing": { "isPublic": false, "groups": ["admin", "billing"] },
"api-reference/endpoints/users": { "isPublic": true, "groups": [] }
}
On init, the server fetches and decompresses this document into two in-memory structures: a Set<string>
of file paths and a Map<string, string[]>
mapping directories to children.
Once built, ls
, cd
, and find
resolve in local memory with no network calls. The tree is cached, so subsequent sessions for the same site skip the Chroma fetch entirely.
Notice the isPublic
and groups
fields in the path tree. Before building the file tree, ChromaFs prunes slugs using the current user's session token and applies a matching filter to all subsequent Chroma queries. If a user lacks access to a file, that file is excluded from the tree entirely, so the agent can't access or even reference a path that was pruned.
In a real sandbox, this level of per-user access control would require managing Linux user groups, chmod
permissions, or maintaining isolated container images per customer tier. In ChromaFs it's a few lines of filtering before buildFileTree
runs.
Pages in Chroma are split into chunks for embedding, so when the agent runs cat /auth/oauth.mdx
, ChromaFs fetches all chunks with a matching page
slug, sorts by chunk_index
, and joins them into the full page. Results are cached so repeated reads during grep workflows never hit the database twice.
Not every file needs to exist in Chroma. We register lazy file pointers that resolve on access for large OpenAPI specs stored in customers' S3 buckets. The agent sees v2.json
in ls /api-specs/
, but the content only fetches when it runs cat
.
Every write operation throws an EROFS
(Read-Only File System) error. The agent explores freely but can never mutate documentation, which makes the system stateless with no session cleanup and no risk of one agent corrupting another's view.
cat
and ls
are straightforward to virtualize, but grep -r
would be far too slow if it naively scanned every file over the network. We intercept just-bash
’s grep
, parse the flags with yargs-parser
, and translate them into a Chroma query ($contains
for fi
▸ 展开全文
04-04 00:02 · AI,技术,HackerNews,大模型,AI
Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
Received the following email from Anthropic:
Hi,
Starting April 4 at 12pm PT / 8pm BST, you’ll no longer be able to use your Claude subscription limits for third-party harnesses including OpenClaw. You can still use them with your Claude account, but they will require extra usage, a pay-as-you-go option billed separately from your subscription.
Your subscription still covers all Claude products, including Claude Code and Claude Cowork. To keep using third-party harnesses with your Claude login, turn on extra usage for your account. This will be enforced April 4 starting with OpenClaw, but this policy applies to all third-party harnesses and will be rolled out to more shortly (read more).
To make the transition easier, we’re offering a one-time credit for extra usage equal to your monthly subscription price. Redeem your credit by April 17. We’re also introducing discounts when you pre-purchase bundles of extra usage (up to 30%).
We’ve been working to manage demand across the board, but these tools put an outsized strain on our systems. Capacity is a resource we manage carefully and we need to prioritize our customers using our core products. You will receive another email from us tomorrow where you’ll have the ability to refund your subscription if you prefer.
▸ 展开全文
04-03 00:01 · AI,技术,HackerNews,AI
Significant raise of reports
Significant raise of reports
Significant raise of reports
Posted Mar 31, 2026 17:11 UTC (Tue) by wtarreau (subscriber, #51152)Parent article: Vulnerability Research Is Cooked (sockpuppet.org)
And we're now seeing on a daily basis something that never happened before: duplicate reports, or the same bug found by two different people using (possibly slightly) different tools.
It's a bit scary (and tiring), but at least compared to the previous era of AI slop, you feel like you're not working for nothing because bugs get fixed. Also it's interesting to keep thinking that these bugs are within reach from criminals so they deserve to get fixed.
I don't know how long this pace will last. I suspect that bugs are reported faster than they are written, so we could in fact be purging a long backlog (and I hope so).
Something I'm predicting is that at least it will change the approach to security fixes:
- embargoes will probably disappear, and for good: what's the point of hiding something that others can instantly find? I have not seen one in a while and that's good.
- people will finally understand that security bugs are bugs, and that the only sane way to stay safe is to periodically update, without focusing on "CVE-xxx"
- software that used to follow the "release-then-go-back-to-cave" model will have to change to start dealing with maintenance for real, or to just stop being proposed to the world as the ultimate-tool-for-this-and-that because every piece of software becomes a target.
Overall I think we're going to see a much higher quality of software, ironically around the same level than before 2000 when the net became usable by everyone to download fixes. When the software had to be pressed to CDs or written to millions of floppies, it had to survive an amazing quantity of tests that are mostly neglected nowadays since updates are easy to distribute. But before this happens, we have to experience a huge mess that might last for a few years to come! Interesting times...
▸ 展开全文
04-03 00:01 · AI,技术,HackerNews,AI
Good ideas do not need lots of lies in order to gain public acceptance (2008)
A subtle change has been made to the comments links, so they no longer pop up. Does this in any way help with the problem about comments not appearing on permalinked posts, readers?Update:seemingly notUpdate:Oh yeah!
Bitch : LabAaronovitch WatchBalkanalysisPerfect.co.ukMaxspeakBrad DelongThe Robert Vienneau blog
Political and philosophical heroes
Subcomandante MarcosWill RogersBoris VianThe English Svejk
RSS Feed:This seems to matter to a lot of people
If you liked this "Daniel Davies" website, you might be interested in
"Danux", the web developerThe martial artist (and fan ofextremelyannoying Flash intros) from BlackburnThe Welsh political journalistA Scouse computer programmer who collects Soviet cameras"Danimal", the heavy metal drummerCanada's finest recorder of radio jinglesMore of the same, at the GuardianA tailor's in Lampeter where Jimmy Carter once bought a hatAn advertising man who has written a novel about dogging (I think we sometimes get each other's email)An award-winning facilities manager in DubaiThe son of the guitarist from the KinksUpdate:he isapparently"balls-out motherfucking shit-dicked exxxstatic" to be included on a Kerrang magazine giveaway CD of Iron Maiden covers, which is nice."Fritz Gretel" from the Ramones film "Rock 'n' Roll High School"The former presenter of the leading politics talk radio show on the Isle of Man, now a business change manager in the Manx government secretary's officeAn aquarium curator in Sussex who keeps on scoring home runs like this (this is the first stable link I've found, but he is constantly kicking ass in acquarial terms)
If you didn't like this "Daniel Davies" website, then don't give up on the Daniel Davies industry completely!
An American "Christian Political Analyst" who has the same name as meA student at Patrick Henry Collegethese two might be the same guy ..."Scatter", the deceased Liberian gangsterA naked man stuck in a chimney in WiganA thug in BarrowThis blog has been going downhill since ...
August 2002September 2002October 2002November 2002December 2002January 2003February 2003March 2003April 2003May 2003June 2003July 2003August 2003September 2003November 2003December 2003March 2004April 2004May 2004May 2005June 2005July 2005August 2005September 2005October 2005November 2005December 2005January 2006February 2006March 2006April 2006May 2006June 2006July 2006August 2006September 2006October 2006November 2006December 2006January 2007February 2007March 2007April 2007May 2007June 2007July 2007August 2007September 2007October 2007November 2007December 2007January 2008February 2008March 2008April 2008May 2008June 2008July 2008August 2008September 2008October 2008November 2008December 2008January 2009February 2009March 2009April 2009May 2009June 2009July 2009August 2009September 2009October 2009November 2009December 2009January 2010February 2010March 2010April 2010May 2010June 2010July 2010August 2010September 2010October 2010November 2010December 2010January 2011February 2011March 2011April 2011May 2011June 2011July 2011August 2011September 2011October 2011November 2011December 2011January 2012February 2012March 2012April 2012May 2012June 2012July 2012August 2012September 2012October 2012December 2012February 2013April 2013June 2013July 2013August 2013March 2014April 2014August 2014October 2015March 2023
▸ 展开全文