Testing Plume from Firefox, now you can see the steps indieauth take against your site for the initial connection, there is also a welcome tab for onboarding (Inspired by Omnibear)

Improved Plume onboarding and fixed a few bugs https://rmdes.github.io/plume/ #micropub and just after publishing this new version, I found a new bug, there should be 1.5.1 very soon !!!

Test post from Omnibear #micropub extension

I’m refactoring my AP implementation first so that I can properly build C2S later on, for now I’ll keep the API layer, since it already covers a lot of ground but the refactoring will allow me to have a more robust implementation and I’m finding this https://www.stevebate.net/activitypub-client-api-a-way-forward/#flowz very inspiring

It really sucks to have a properly configured email server, running on your own domain — thanks, Cloudron — only to have Google, Microsoft, and the other giants systematically dump your messages into spam anyway.

And yet I now find myself sending important emails twice, or using another provider, just to make sure they actually reach the person on the other side.

Email was supposed to be an open, decentralized protocol. Instead, a handful of monopolies have effectively privatized deliverability: they decide whose mail is trustworthy, whose isn’t, and independent servers are guilty until proven innocent.

#Enshittification at scale: privatize the commons, segment it, then slowly make the open alternative unusable for everyone else.

Mark Zuckerberg’s manifesto rests on a single elegant idea: safety comes from distributing power so no one actor can impose their will. It’s a fine principle. It’s also the exact opposite of how he has run everything he has ever touched. Start with the structure of Meta itse...

C’est horrible à dire, mais peut-être que lorsque nous en aurons assez de voir la nature et nos maisons partir en fumée, nous prêterons davantage attention aux rapports « alarmistes » du GIEC — qui, au fond, n’avaient rien d’alarmiste. Mais surtout, peut-être mettrons-nous e...

A health check that reports “healthy” is not the same claim as “this loop is still running.” I spent a chunk of today’s session learning that distinction the hard way, on a bot whose only job is to relay earthquake alerts to Bluesky. The setup: a queue drain loop calls healt...

Damn, stumbled on a black hole of the past, really sorry to all the blogs that interacted with mine circa 2016 and that I never replied to, I was in a huge Justice battle IRL and my site at the time was not giving me as much control and view over what’s happening than it is today, some of these replies I’m seeing now for the first time.

There is also quite a few dead links that I never managed to recover from my server crash from around those years

Thanks for sharing RSC ! There is still a lot of work before I start to really enjoy using it as I envision but its been really fun to develop :)

Cross-browser Micropub client extension. Post to your IndieWeb blog from any page.

rmdes.github.io/plume/ - now with Draft support, right in your browser of choice !

I need to fix duplicate webmentions

• 1 is coming from legit webmention
• 2 is coming from fed.brid.gy

I need to think about how to fix this

really glad to hear that :)

Test from Chromium based browser, Plume Micropub extension

Testing Plume from Firefox

I have looked at your Micropub plugin and then debugged the issues with claude and I think I found the problem, nothing to do on your side, it was really a bug on my side : https://github.com/rmdes/plume/releases I submitted version 1.3.1 to the extension stores, both should be available soon, you can always “developer” load it via the github release page if you don’t want to wait, let me know how it goes :)

Do you have access to your Kirby server logs ? would be interesting to check what’s the error precisely, have you looked at the dev console log when you attempt to add your site to the extension settings ? this would allow to gather a bit more information I suppose, another way would be to create a user for me, so that I can connect using it and launch mcp playwright debug in the process to understand what’s happening

inspiring…

Cool idea !

Great work by the cloudron team as usual !

Major Update : a configurable RSS poster for #Bluesky - that supports multi accounts - in active development https://github.com/rmdes/bsky.rss

China isn’t simply a regime with a centrally planned technological machine.

It’s something stranger: a strategically directed state sitting on top of an extremely competitive manufacturing ecosystem.

China’s long-term strategy increasingly resembles ecosystem substitution:

Foreign technological ecosystem becomes a vulnerability → create an alternative ecosystem.

Replacing Microsoft Office with a Russian office suite is import substitution.

Creating an operating-system ecosystem, CPU architecture, compiler toolchain, domestic cloud stack, hardware supply chain, developer community and application ecosystem is technological sovereignty.

China is attempting the latter.

@srijan.ch@fed.brid.gy how’s your micropub endpoint?

Does your blog support micropub?

Hmm this is odd, do you have any information to help me debug this ?

Test post from Plume, micropub extension for Firefox/Chromium derived browsers

Wishing there was a fully supported ATgeo lexicon that most bluesky app views could understand…it would allow us to build location aware posts from location data (think disasters, quakes, flood etc)

Sometimes I’m wondering, what would be the cost of stopping supporting the Mastodon API layer and instead work towards proper implementation of client to servers opening the route for a universal mobile app for #fedify based AP implementation.

For indiekit I used Fedify to bring this very blog into the fediverse but then I wanted to be able to use Phanpy and other mobile app so I built a compatibility api layer that these mobile apps expect to find allowing me to use my own site with any Mastodon mobile app. It works but it’s buggy and I’m subject to API layers change and other future breakage I don’t want to deal with in the long run.

So now I’m wondering, do I drop this API layer and build a universal client?

People comes in all shapes and sizes but writing code into OPML outlines to then “generate” code files for a git repository is one that I will never understand.

No matter how much time I put into it.

It’s like using I a Word document to write Javascript or typescript?

The results is a OPML file literally containing Javascript code, each outline being a block of code.

When changes are made and saved it changes the timestamp of the outline publish time, so any diff against the OPML is full of noise, it’s literally the worst dev environment I have seen in my life.

There is certainly a historical reason for this that evade my grasp but imagine, having a dozen intertwined code projects ALL developed in such a way.

Good luck contributing or sending a PR to repository like that. It’s literally the perfect way to make sure collaboration is impossible.

Just migrated bsky.rss from feedsub to feedsmith, now bsky.rss support RSS, Atom, Jsonfeed, EDF and soon GeoRSS too, I’ll do another round of improvements so that it would be easier to parse and render weather Feeds but that’s for later.

Feedsmith has a bunch of other RSS extensions that I want to integrate, for example better source/author attribution, something I always wanted to bring for the RSS feeds that properly use these properties.