Blog
All posts including articles and notes. (2585 total)
-
Permalink
could be interesting to check Crowdsec to mitigate against this kind of automated traffic.
-
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
-
Huh 👀 Music Mouse rebirth/reimagined?
-
Finally got my #fedify rel=me link working properly from the view of other Mastodon/Fediverse clients
-
Oh My God :)) Now You can interact with my posts from your fediverse instance, by setting your instance in your browser
localstorage, once this is set, click the Fediverse icon and you’ll see my post through your own mastodon/pleroma instance ! -
Updated indiekit AP implementation to Fedify 2.0 !
-
Crafted this nice ActivityPub profile page for my Fedify/indiekit AP implementation, this is obviously for browsers, AP server receive an AP representation of my profile Screenshot below is Fedify 2.0 built in debugger
-
Caches GET/HEAD responses for ActivityPub endpoints (actor profiles, featured posts, notes, webfinger, nodeinfo) so hundreds of simultaneous fetches from federated instances are served from nginx instead of hitting Node.js.
Uses proxy_cache_lock to prevent thundering herd and proxy_cache_use_stale to serve during backend overload. POST /inbox and admin pages bypass the cache.
-
My indiekit blog now support comments authentication using RelMeAuth or IndieAuth, it also supports webmentions if you’re part of the #indieweb dance !
-
Cool stuff, a Thread reader for the fediverse : https://ap-thread-reader.fly.dev/
-
PermalinkSo now I have an #ActivityPub server, using the ActivityPub protocol as a layer on top of my existing indieweb/indiekit server
-
This post is made from my indiekit #fedify spec implementation turning my indiekit blog into an effective AP instance on the fediverse
- first I thought, why not reuse Microsub reader to consume AP content coming from the fediverse ? I tested it, customizing a bit the view to better handle AP activity (boost, star, quote, reply) but using a dedicated Microsub Channel as a Fediverse input for the AP fedify server turned out to be odd, an AP post is not an RSS item from a blog, and the firehose of posts, reply, quote, boost is too much to handle in a Microsub Channel, I resolved to build a proper reader for AP content
stefanbohacek.com
manton.org
brennan.day
hollo.social
github.com
blog.jetbrains.com