Notes
Short thoughts, updates, and quick posts. (1581 total)
-
Really liking the flexibility I built into my indiekit + eleventy deployment where I can create content in different ways :
- markdown files
- micropub create post endpoint store data in MongoDB
- static html serving like demo
-
One of the best hack I did to my Eleventy theme with Alpine is to store my session in the browser localStorage and then display to authed users a FAB, with contextual web actions on any part of the site :
- create a new posts, bookmark, article etc…
- edit the current post
this allow me to search anything via the frontend to edit, it works on mobile or desktop and its a life-saver !
-
I can now configure my h-card from the indiekit backend :)
-
Curious to see if #Fedify will support Quotes soon…
-
The first time you click a Fediverse button on my site, you’ll be asked to enter your home instance — in other words, your own Fediverse server. This can be a self-hosted instance or a platform like Mastodon, Pleroma, and others.
Once that’s set, clicking on an “Also on” syndicated post link will open the corresponding URL directly inside your own Mastodon instance. From there, you’ll see it as a native Mastodon post, which means you can reply, boost, or favourite it just like any other post in your timeline.
The same logic applies to the “Fediverse” sidebar widget. It reads the instance you previously saved in your browser’s localStorage and uses it to trigger a remote follow request directly from your own Mastodon account.
-
One of the downside of self-hosting one’s own ActivityPub server is the loss of Brid.gy backfilling social reactions to one’s content.
This is why I developed this indiekit plugin, it basically translate ActivityPub activity on one’s content into JF2 format so that this page can aggregate all the interactions with my content in one place. It also provide an API so that I can display a webmention widget in the frontend that Eleventy + AlpineJS can use to display new interactions live on the frontend.
-
Added a bunch of colors to my blog, per post types, I’m far from the frontend design I dream about but the important is, its getting better and its home made ! https://rmendes.net/blog/
-
Finally fixed my green check rel=me link !
-
juste un peu marre de voir du Epstein partout pendant que l’invisibilité de ses victimes continue. de quoi les systèmes de Justice ont besoin pour arrêter Robert Spatz alors même qu’il fait appel d’une énième décision de Justice, suite à sa condamnation de 2022, tout en étant vautré dans la récidive?
-
Storing this here for future exploration in the context of indiekit/ATproto integration
-
Signed this petition, Stop Google from limiting APK file usage
-
Android will become a locked-down platform in 184 Days if you don’t make your voice Heard.
-
The uncomfortable truth is that I rarely think about UI/UX until I’m forced to use it and realize there’s no way around it. Nothing pushes you to improve something quite like experiencing its flaws every single day. When you depend on a tool and its interface constantly gets in your way, the motivation to fix it becomes very real.
I’ve always been more drawn to backend infrastructure than frontend development. That’s where I feel most comfortable. But it’s precisely when you’re stuck using a clumsy or poorly designed interface that you start caring about the user perspective. Frustration becomes fuel.
I’ll probably need to spend more time reading through the codebases of projects like Elk or Phanpy to better understand alternative ActivityPub UI patterns and design choices.
There’s a lot to learn from how others approach the same problems. My current self-hosted ActivityPub reader works, technically.
But from a UI perspective, it’s still rough around the edges and that’s something I want to throw some energy & focus to improve.
-
It took me more than a month of intense paced AI assisted development to get where I wanted to be, but https://rmendes.net/changelog/ this blog/AP has all the #indieweb spec backed in + AP + simulation of brid.gy to backfill reactions back to my posts !
-
Having implemented Fedify to power the ActivityPub implementation for Indiekit, I’m confronted to an issue I never had to think about : how do you consume AP content in a way that makes you want to have a timeline to scroll when you can’t use any of the available Mobile Apps out there ?
-
One more bug solved
- Quick reply (quick reply test) — in_reply_to_id: “116115945039999145” threaded under the original post
- From rick@rmendes.net via the self-hosted AP serverThe replyTarget fix resolved the threading issue. To recap the full fix chain across v2.0.2–2.0.5:
2.0.2–2.0.3: Added to/cc addressing on Note object 2.0.4: HTTPS Note ID (not urn:uuid:), to/cc on Create wrapper 2.0.5: inReplyTo → replyTarget (Fedify 2.0 constructor parameter rename) -
286 times : the amount of times I iterated/reviewed on different parts of the indiekit fork codebase triggering a build & deploy to move forward several new features, among them Microsub & ActivityPub https://rmendes.net/changelog/
-
Fixed: IndieAuth login broken for third-party apps
After adding security headers (Content-Security-Policy) to harden the site, logging in with IndiePass and other IndieAuth clients silently failed — tapping “authorize” did nothing.
The culprit was form-action ‘self’ in the CSP, which blocked Browsers from following the consent form’s redirect to the client’s callback URL (e.g., indiepass.app/android-callback).
Changed to form-action ‘self’ https: to allow IndieAuth redirects to any HTTPS callback. Affects all third-party IndieAuth clients (Micropub editors, Microsub readers, etc.), not just IndiePass.
-
Alright, testing #IndiePass #Indiekit #Fedify 2.0 if you see this post on the Fediverse or Bluesky it means syndication works and my blog is my own AP server.
public profile : https://rmendes.net/activitypub/users/rick
indieweb.social