jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Started working on bringing ActivityPub Polls to NodeBB 
First step is adding in separate handling of the Question object. Right now NodeBB treats it as a "Note-like" and renders it like a post
50% of the way there... will need to link it to nodebb-plugin-poll...
One complication... the plugin ties votes to users. This data isn't reflected over-the-wire in AP, only the aggregate voter counts are shared
[...]
In a few days — perhaps in about a week — you’ll hear how all these Mastodon sites were hacked.
Why?
Because they didn’t update.
Some of you are running copies of Mastodon from two years ago or more, and you’ll still wonder why. 🤦
Hollo announces: Hollo 0.9.0 is out. https://hollo.social/@hollo/019e451e-f368-70e2-b993-77d01a14a677 #hollo #fediverse #ActivityPub
#Wanderer is a very nice project, but it is currently too raw to use. The last two releases just broke everything, and even a clean setup doesn't help. I'll follow the repository, but shut down my instance for now.
https://github.com/open-wanderer/wanderer
#SelfHosted #SelfHosting #SelfHost #homelab #ActivityPub #hiking
My Hollo instance has been updated to 0.9.1 if you wanna take a peek. It's shaking off the early UI look and feel for something more professional.
A lot of extra configurations that I didn't have time to review or enable, but some of it looks interesting, like more efficient handling of remote media.
- https://github.com/mastodon/mastodon/releases/tag/v4.5.10
- https://hollo.social/@fedify/019e4675-05bc-7725-bcf4-aa51d6af70a0
- https://shrimp.meow.company/notes/amhmis327j0wve4w
- https://shrimp.meow.company/notes/amhmiqtsbwgmt158
- https://activitypub.software/TransFem-org/Sharkey/-/releases/2025.4.7
- https://hubzilla.org/item/53f3509f-d63d-494c-a431-ac84df9c6a57
- https://w.on-t.work/activitypub/may-2026-vulnerability
>Fix Linked-Data Signature bypass through JSON-LD graph restructuring features
JSON-LD adds nothing to Fediverse except bugs and security vulnerabilities.
Of course, there is an alternative to Linked Data signatures that doesn't require Linked Data, much simpler and more secure:
Here is my work-in-progress FEP for using JSON Resume with ActivityPub:
FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD
https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md
I prefer to write for clarity, so it still needs work.
#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158
@hollo releases a new major version update, 0.90. Too many changes to hit in a single post! Skimming, the most notable to users will be the switch from Pico CSS (my weekend hobbyist fave) to Uno CSS. At least in screenshots, the new UI is taking on a polished look.
Planning to upgrade, but need to review this a bit more before flipping the switch.
My personal desire would be to create a format from scratch (because you are in control, you get something bespoke to your needs, and it is personally satisfying), but —
I think there is probably an advantage to using something (such as JSON resume) that already has wide adoption.
I guess that makes me inclined towards the latter.
...
So, if I go that way, I would have to decide: plain JSON or JSON-LD.
#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume
I may have written a JSON-LD schema for JSON Resume.
It is defined in terms of ActivityPub.
For example:
'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.
...
Now the question is — where do I put it?
Do I create a pull-request to the JSON Resume resume-schema repo?
Do I create a FEP?
Do I put it somewhere else?
#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume
Loops Playlists will soon federate!
They will likely only be compatible with other Loops servers as we're using a new type of OrderedCollection.
How to Host Your Own #Mastodon Server on a #VPS (5 Minute Quick-Start Guide)
This article provides a guide for how to host your own Mastodon server on a VPS.
Running your own Mastodon server on a VPS is an excellent way to enjoy an efficient and secure Mastodon experience.
What is Mastodon?
Mastodon is a #decentralized social media platform that enables users to post ...
Continued 👉 https://blog.radwebhosting.com/how-to-host-your-own-mastodon-server-on-a-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #selfhosting #activitypub #installguide #rubygems #selfhosted #rubyonrails
Evan Prodromou says: For the #ActivityPubAPI, we need a profile of OAuth to use for accessing the actor's data. https://cosocial.ca/@evan/116591693871988651 #ActivityPub
Völlig klar: Das Posting der Verbindung landet nun auch im Stream meines GoK.
Aber wie ist es, wenn eine Verbindung des Fediverse-Kanals, z.B. ein Mastodon-Nutzer auf das Posting antwortet? Sehe ich diesen Kommentar, obwohl mein GoK ja gar kein AP kann? Und kann ich, falls dieser AP-Kommentar in meinem Stream antwortet, selbst auch auf diesen Kommentar antworten? Und schließlich: Wenn das auch geht, wer sieht dann meinen Kommentar auf die AP-Antwort?
Nun, die Frage konnte ich auch nicht aus der Hüfte raus beantworten. Mir ist das noch nicht untergekommen, weil meine einzigen GoK halt ausschließlich nicht-öffentliche Foren-Kanäle sind und dort solche Ereignisse nicht vorkommen.
Also habe ich mit einem eigens erstellten Kanal Grid-Only, der ein GoK ist, ein entsprechendes Experiment durchgeführt. Und es ließ sich folgendes Verhalten feststellen:
Ist ein GoK mit einem Hubzilla-Kanal verbunden, welcher auch AP aktiviert hat (Fediverse-Kanal), erscheinen selbstverständlich Posting des Fediverse-Kanals auch im Stream des GoK.
Kommentiert nun ein fremder Account eines Fediverse-Dienstes dieses Posting, dann erscheint der Kommentar auch im Thread zum Ausgangsposting beim GoK. Der Inhaber des GoK kann also AP-Beiträge sehen, obwohl er gar kein AP unterstützt.
Der GoK kann sogar die im Thread nun angezeigte Antwort des AP-Accounts selbst kommentieren.
Dieser Kommentar erscheint -- logisch -- im Thread im Stream des GoK und -- ebenfalls logisch -- auch im Stream des Fediverse-Kanals (also des Verfassers des Ausgangs-Postings) als Antwort auf den AP-Kommentar.
Aber: Die Antwort des GoK auf den AP-Kommentar erscheint NICHT in der Timeline des AP-Accounts.
Also auf den Punkt gebracht:
Grid-only-Hubzilla-Kanäle finden in ihrem Stream durchaus auch Inhalte, die von ActivityPub-Diensten stammen, sofern eine ihrer Hubzilla-Verbindungen AP erlaubt und selbst einen Kommentar von einem AP-Dienst empfängt.
Solche Antworten aus dem Fediverse sind für den GoK nicht nur im Stream sichtbar, sie können durch den GoK sogar kommentiert werden. Diesen Kommentar eines bekommt aber nur der verbundene Hubzilla-Kanal zu Gesicht, nicht aber der AP-Account, dessen Antwort im Thread kommentiert wurde. Kommentare des GoK auf das Ausgangsposting sind hingegen auch für den AP-Account sichtbar. Also: Kommentare eines GoK sieht der AP-Account, Antworten eines GoK auf Kommentare eines AP-Accounts sieht der AP-Account nicht.
Alle Klarheiten beseitigt? 😁
---
Member of the Hubzilla Association
Location: Nagybaracska
RE: https://mastodon.social/@reiver/116597879302607072
More on a resume / CV on the Fediverse on Social Web.
Another option could be to use something like "JSON resume":
https://github.com/jsonresume/resume-schema/blob/master/job-schema.json
It seems to be popular.
It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.
#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume
RE: https://mastodon.social/@reiver/116597841178183282
There is also the other question of — would the resume / CV be JSON-LD.
On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.
On the other hand, I don't think anyone is going to write JSON-LD (especially HTML embedded in a JSON string value) by hand. But, I do think some people will want to write their resume by hand.
It feels like user-experience is fighting with JSON-LD based machine-legibility.
RE: https://mastodon.social/@reiver/116597841178183282
There is also the other question of — would the resume / CV be JSON-LD.
On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.
On the other hand, I don't think anyone is going to write JSON-LD (especially HTML embedded in a JSON string value) by hand. But, I do think some people will want to write their resume by hand.
It feels like user-experience is fighting with JSON-LD based machine-legibility.
https://github.com/macports/macports-ports/pull/32773
GitHub Continuous Integration checks passed!
It's up to someone else with commit access to merge it.
Thanks to you and la_ninpre, trondd555, sergiodj, kpm, zen, pmjv and anyone else I may have missed for the improvements in this release!
My apologies for taking so long to get around to submitting a PR. I check repology.org multiple times a day, most days, but for some reason only saw snac needed attention a few hours ago! This may inspire me to rejigger MacPorts' livecheck stuff for local/sanity check/resilience/not putting all my eggs into one basket/etc.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces
For the #ActivityPubAPI, we need a profile of OAuth to use for accessing the actor's data. There's a suggested flow here:
There's an example client here:
https://swicg.github.io/activitypub-api/examples/oauth/index.html
It tries discovery via RFC 8414 or getting the endpoints straight from the actor.
It then provisions a client ID using CIMD, FEP d8c2, or DCR (in that order).
It then tries to do an authorization code flow.
I'm interested in seeing it tested with more ActivityPub API servers.
Remote Inbox Architecture
1/
This, the Remote Inbox Architecture, is an architecture for a Fediverse back-end server that I think could be useful.
Here is how it works — there are (at least) 2 servers involved: (1) the main back-end server, and (2) a remote inbox server.
The actor file on main back-end server "points" the inbox to the remote server.
It separates the user's content front the front-end related functionality
...
Remote Inbox Architecture
2/
The Remote Inbox server deals with incoming activities, objects, etc, from other users..
The front-end can get the inbox (and other feeds') data from the Remote Inbox server.
(You'd probably want to store cached data from the Fediverse elsewhere from these two servers, as I've said before. But, that is a separate thread.)
I'm getting closer to something showable on my side project, a recipe and baking app, #federated with #ActivityPub, https://cookifed.dev.
I'm not ready to accept new users yet, but @dmathieu@cuisine.social is the first ever #cookifed federated account!
I've been working on improving Loops federation in preparation to reuse it and it's powerful builder/handler/validation pattern for Pixelfed!
This will solve many federation issues in Pixelfed, like missing comment threading, mentions, blocks and unblocks and much more.
Then I will abstract it into a reusable Laravel package, so any laravel project can easily add federation support in minutes
I also submitted a NLnet grant application for this 🤞
@publicspaces will have a pre-conference unconference on June 4th.
This unconference is an open invitation to discuss & forge relationships between people involved with the #OpenSocialWeb. From app builder & protocol architects to advocates, sysadmins, moderators, community organisers & more. Let's forge bonds across cultures, protocols & apps!
Admission free, registration required:
https://tickets.publicspaces.net/publicspaces/pubconf2026/
#ActivityPub #Fediverse #ATProto #Matrix #OpenSource #PublicSpaces #PubConf2026
Hear me out, if we can integrate these 4, in a seamless frictionless integrated experience for both, companies and users, we could have a nice alternative to #LinkedIn that is actually not crap.
Any interest?
Week in Fediverse 2026-05-15
Servers
- PieFed v1.6.23
- Hollo v0.8.3
- Ktistec v3.3.8
- Wafrn v2026.05.01
- snac v2.92
- Mitra v5.3.0
- Iceshrimp v2026.4.2
- Hollo v0.8.4
- Vernissage v1.37.0
- Bonfire v1.0.3
- Hometown v1.2.1
- tootik v0.22.1
- NeoDB v0.14.2
- NodeBB v4.11.3
- PieFed v1.6.23
- Wanderer v0.19.0
- Aktor: A headless, Mastodon-compatible ActivityPub server
Clients
- FediLab v3.40.0
- tooi v0.25.0
- Holos v1.5.6
- Phanpy changelog
- lemmy-tray: Read lemmy posts in system tray
Tools and Plugins
- FediFetcher v7.1.18
- slurp v1.1.1
For developers
Articles
- There Are a Million Fediverses. Some of Them Are Louder than Others
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019e0915-d395-7e60-aad7-f2f1a354264a
We just released Bonfire Social 1.0.3 🔥
Blog post with all the details: bonfirenetworks.org/posts/bo...
It comes with dozens of bug fixes and UX improvements, plus:
#CalmEmpowerment: a new design pattern that starts with a few sensible defaults, offers a middle layer of common adjustments, and reveals the full options only when you need them. Boundaries and post permissions got this treatment first, more to follow...
Modular community rules: a first step in bringing research and co-design with students and researchers at @hci@micro.blogs.princeton.edu into Bonfire, so governance becomes something communities can better define and share, and that others can fork and adapt.
Does anyone have recommendations for a Mastodon fork that doesn't require visitors to enable JavaScript to view basic content? The JavaScript dependency is a security risk and user hostile. Visitors should not be required to enable JavaScript when simply visiting a Mastodon server. Plus, the recommendation to use a native app doesn't even work for all Mastodon/ActivityPub instances.
Also, the requirement for JavaScript makes the Mastodon development team seem incompetent. They can't even make a basic web site that doesn't require JavaScript. I could do that when I was in middle school.
>To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform.
So #Vine is coming back, this time as #DiVine!
Does anyone know anyone who can get me an invite code? I want in!
The App is coming back with no #AI allowed, and will allow people to own their own content.
For the geeks: it's built on the #OpenSocial protocol #Nostr, and apparently they're experimenting with integrating the #ATProtocol, future integration with #ActivityPub, the protocol behind #Mastodon and #Flipboard.
https://www.youtube.com/watch?v=zUGnNIh60-0
#Holos is a new social network working with #ActivityPub. This is not an app where you can connect your Mastodon, Pixelfed or PeerTube account.
There is no web version and no API because the ActivityPub server runs on the device itself. That's the whole challenge behind this project.
If there is more engagement, I plan to build a desktop version and even sync between different devices.
The official account for all announcements is @HolosSocial
There are a LOT of Fediverse projects out there!
If you're a techy person interested in self-hosting Fediverse platforms, you might like to check out the "Delightful Fediverse" list which tries to feature every Fediverse project available:
🌱 https://codeberg.org/fediverse/delightful-fediverse-experience
(It's worth noting the meaning of the emoji next to project names, as the status of different projects varies.)
Changed default: for newly created instances, disable_inbox_collection is set to true (see snac(8) for more information). The reason is because it seems to be used for harrasing people.
Changed default: for newly created instances, disable_history is set to true (see snac(8) for more information). The reason is because archived history files don't reflect reality after posts are deleted or modified (they always have been an ugly kludge).
Changed default: in previous versions, posts with a scope of unlisted were shown in public pages and RSS feeds. Now, they are no longer shown. If you want to get back to previous behaviour, use a new toggle in the User Settings section (see snac(1) for more information).
New admin configuration option: if the purge_static value is set to true in server.json, each user's static directory is explored and those files there that are no longer attached to any post or referenced anywhere are deleted. See snac(8) for more information about those cases where you may not want to enable this option.
Allow serving files from subdirectories of the static/ subdirectory (contributed by la_ninpre).
Minor tweak to webfinger code to handle Hubzilla's peculiarities.
Fixed a search case where URLs to GotoSocial statuses were misidentified as accounts.
Accounts that follow you are now marked with a thumb-up emoji, because followers are adorable people.
Fixed some account export errors.
Fixed an incorrect hash in post links.
Show an account's location link in the people page, if they have one.
Mastodon API: Fixed hashtags loosing the link after editing a post, minor tweak in access token processing (contributed by trondd555).
Drop usage of PATH_MAX (contributed by sergiodj).
New Polish translation (contributed by kpm).
Updated German and Czech translations (contributed by zen and pmjv).
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.

This post is about work happening on WordPress.com, specifically the Reader, the long-running subscription-and-reading surface that’s been part of WordPress.com since 2008. It’s a sibling effort to the ActivityPub plugin, not a feature of it. We think it matters to plugin readers anyway, because the two pieces are converging, and the converging point is what we’ll be working on next.
Two weeks ago, Automattic kicked off something internally called Radical Speed Month, a four-week sprint where small teams ship fast on focused projects. We (@jeremy and @pfefferle) took the chance to spend it on something that’s been sitting at the edge of the Fediverse-and-WordPress conversation for a while: making the WordPress.com Reader speak Fediverse.
Today is roughly the halfway mark, and the picture is clearer than we expected. Here’s what shipped, what’s in flight, and what’s still ahead.
The Reader on WordPress.com has held a single, useful role for over a decade: it’s where your subscriptions live. Blogs, podcasts, RSS feeds. What it hasn’t done, yet, is read the open social web. Your Mastodon timeline lives in another app. Your Bluesky timeline lives in a third. The Fediverse is out there, and the Reader stays over here.
The Radical Speed Month bet: ship three protocol adapters in four weeks, and prove the Reader can become a universal aggregator. RSS / Google Reader API (so any reader app can use WordPress.com as a sync backend), ActivityPub (so Mastodon, Pixelfed, and friends show up natively), and ATProto / Bluesky (because that’s where a real chunk of the social-web conversation has gone). One Reader, every protocol you care about.
If you’ve been following the ActivityPub plugin for a while, you already know one half of this story, your blog speaking out to the Fediverse. The other half is reading in, and that’s where this month’s work concentrates.
Any Google Reader-compatible app can now point at WordPress.com and use it as a sync backend. That includes Reeder, NetNewsWire, ReadKit, lire, Unread, Fiery Feeds, Feed Me, and Read You. The auth onboarding is short, and your subscriptions, read state, and stars sync across whichever app you actually like. We’re working on a setup guide that walks through the steps for the most common apps; it should land soon.
This wasn’t directly Fediverse work, but it’s part of the same idea: the Reader as a backend, not a destination. If your reading habit lives in a different app, that’s fine. Your subscriptions still live on WordPress.com.
The Bluesky / ATProto adapter has moved further than the original plan suggested.

You can:
The remaining piece on the Bluesky side is quote-posting and deleting your own posts, which we’re shipping together. After that, Bluesky is a complete first-class tab in the Reader.
Mastodon followed the same pattern: connect, verify, then a steady cadence of small additions like timeline, in-app threads, author profile and feed (with Posts / Replies / Media filter tabs), and tag and hashtag feeds. All of those are live for Mastodon today.

What’s still coming on the Mastodon side is the equivalent of the Bluesky interaction work (favourite, boost, reply, quote) built on the same shape that worked for Bluesky. Expect those to land in the second half of this month.
If you read 8.1.0 — By the Numbers, you’ll have noticed a small line in the announcement: the plugin now exposes an ActivityPub API. It’s experimental, behind a feature flag, and lets third-party apps create, edit, and delete posts on your blog the way they would post to a Mastodon account.
That work isn’t an accident. It’s one half of a bridge, and Radical Speed Month is the other half.
The Mastodon-in-Reader work that shipped this month is user-level: you connect your Mastodon account once, and the Reader can sync your Mastodon timeline regardless of where your blog lives. That’s a useful starting point, but it’s not the only path forward. The model we’ve been working toward for a year is blog-level: each ActivityPub-enabled WordPress blog as its own social identity inside the Reader, with the plugin providing the actor and the ActivityPub API providing the connection.
That work is on the schedule for the second half of the month. The radical-speed pace gave us proof first: timelines, threads, profiles, and interactions can all run through one shared pattern, with two networks already validating it. With the pattern in place and the plugin’s ActivityPub API ready to talk to, the blog-level path slots into the same architecture, letting your plugin-enabled blog appear as an ActivityPub identity in the Reader sidebar, with its inbox, its outbox, and its real ActivityPub follow graph. And because the API is part of the ActivityPub standard, the same path works for any Reader or client that speaks it, not just WordPress.com.
A short list of what we’re chasing for the second half of the month and just past it:
A month feels short to ship three protocols’ worth of reading, profiles, and interactions. It’s worth saying out loud: this didn’t happen because we worked unsustainable hours. It happened because we sat with the design for months, picked a shape that lets each protocol reuse the same plumbing, and broke the work into pieces small enough that any one was reviewable in a day or two. “Radical speed” turned out to mean: a backlog of careful design, drained quickly.
If you run an ActivityPub-enabled WordPress blog, whether on WordPress.com or self-hosted, the practical takeaway is small for now and meaningful soon. The plugin’s ActivityPub API in 8.1.0 is the foundation for your blog showing up as a real social identity inside any Reader or app that speaks the same protocol. The WordPress.com Reader is the first concrete target, but the universality matters: any client that implements the standard can talk to your plugin-enabled blog the same way.
Already, the work this month means there’s now a Reader on WordPress.com that knows how to read the Fediverse alongside RSS and Bluesky. That’s a meaningful thing to have built, and the bridge from your plugin-enabled blog to that Reader is what the second half of the month is about.
We’ll keep posting updates as the month closes out. If you have thoughts on what blog-level ActivityPub in the Reader should look like, what protocols you’d want next, or how the plugin’s ActivityPub API should evolve to make this seamless, leave a comment on the plugin’s GitHub repository or reply on the Fediverse. We read every message.
Following the recommendations I got, I set up a #NodeBB forum to discuss the projects #Fedilab, #Holos, #CastLab and #Fedle.
Each category federates over #ActivityPub, so you can follow it directly from your Fediverse account: @fedilab, @holos, @castlab, @fedle.
More details: https://forum.fedilab.app/post/2
Week in Fediverse 2026-05-08
Servers
- Vernissage v1.35.0
- Pleroma v2.10.2
- Funkwhale v2.0.2
- Betula v1.7.0
- Hollo v0.8.2
- Akkoma v2026.05
- Ktistec v3.3.7
- NodeBB v4.11.0
- Misskey v2026.5.1
- Ties v0.2.1
- PieFed v1.6.21
- Lemmy Development Update April 2026
Clients
- Nicolium v0.2.1
- Fedilab v3.39.0
- Pachli v3.6.1
- Mastodon for Android v2.12.0
- Coho v1.0
- PixelDroid v1.0.beta42
- Blorp v1.13.0
- Mitra Mini v0.4.0
- Holos v1.5.5
Tools and Plugins
For developers
Articles
- Join the fediverse! zine
- A Bridge to Somewhere: How to Link Your Mastodon, Bluesky, or Other Federated Accounts
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019de52a-a351-7ee2-a48b-7306090edfe6
Hashtag following also allow URLs to RSS feeds of ActivityPub objects (like e.g. https://mastodon.social/tags/ThankYouTuesday).
Users can now configure a webhook to receive an HTTP POST for every notification. This can be useful for implementing bots that react to activities, like autorepliers, chatbots or interactive textual games (see snac(1) for more information).
The number of pending follow confirmations is shown next to the "people" link.
Faster performance metrics (contributed by dandelions).
Improved lowercasing in hashtags (contributed by postscriptum).
A search-by-url tweak for implementations that return 200 for invalid webfinger queries (e.g. piefed).
Mastodon API: added follow confirmation endpoints, fixed collisions in attachment file names.
Fixed potential crashes in attachment uploads.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Notifications are now shown in a more compact way (i.e. all reactions are shown just above your post, instead of repeating the post ad nauseam for every reaction).
New command-line option unmute to, well, no-longer-mute an actor.
The private timeline now includes an approximate mark between new posts and "already seen" ones.
Fixed a spurious 404 error in the instance root URL for some configurations.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song The Answers to the Questions by #Christabell and #DavidLynch.