I just created an RSS feed of my /now page! I haven't been very active in my blog, but I've kept updating this, so subscribe if you want see what I'm up to! https://noeldemartin.com/now/rss.xml
Not only that, apparently Bluesky is not even living up to their own ideals (TLDR: Bluesky is not really decentralized... "yet"): https://beige.party/@possibledog/113367997579738126
And in case you're wondering, yes, the Bluesky team did know about Solid. Before announcing the AT protocol, they did an "ecosystem review" in which they studied all the existing solutions they would proceed to ignore: https://gitlab.com/bluesky-community1/decentralized-ecosystem/-/blob/master/README.md
(by the way, if you haven't seen the talk, here's the link: https://www.youtube.com/watch?v=F1sJW6nTP6E)
There are lots of nice recipes on the web. Bigger recipe sites often allow you to store your favorites in a cookbook. Unfortunately those are always restricted to recipes on that site.
Here comes #Solid to the rescue: With an app like #Umai you can store any recipe found on the web to a cookbook in your own Pod.
In the latest #PracticalSolid video, I am showing you how to do that!
https://tube.tchncs.de/w/x4mML2c4fnHE4xH7JMjCGG
Let me know what you think!
It's still a proof of concept, but let me know if you think this is cool or you have some questions :D.
I'm calling it "Vivant", and you can find this and other examples in this playground: https://noeldemartin.github.io/vivant/
Recently, I've been learning to make animations on the web. And I'm starting to understand why Framer Motion is one of the reasons for people to choose React over #Vue.
But I still want to use Vue! So I started working on a library that supports layout animations, like this one:
I started a video series about the practical use of #solid
I talked a lot about it's vision and the ideas behind it, and most people really like all the concepts, but struggle o use it in practice (for many good reasons)
I am showing what Solid can actually do today and in practice and share my experience using it as an early adopter and developer for many years now.
If this sounds interesting to you, follow @practical_solid to get all the updates
Inrupt recently open-sourced a Data Wallet, and I have some comments about it. If you care about #Solid, I think it's important that you're aware of what's going on. Join the discussion in the forum: https://forum.solidproject.org/t/inrupts-data-wallet/7836
Somewhat reluctantly, I'm going to start using Bluesky 😅. Twitter is getting worse by the day (almost nobody sees my Tweets anymore), and I've had this Mastodon account for ages, but it's too technical for some people. So I'll be using 3 apps that do basically the same thing 🤷.
In any case, as you may already know, I'm not super active. I'll continue cross-posting everywhere, but the best place to follow my work is still my website, which you can subscribe through RSS: https://noeldemartin.com/now
It's just a proof of concept; and I didn't implement any of the hairy stuff (authentication, authorization, content negotiation, etc). But with very little effort, it works with a couple of my apps. So it already covers 90% of the functionality I rely on as an app developer.
It's because of things like this that I always say that in reality, Solid is very easy to learn. If you grasp the basics, it's really not a lot more complicated than understanding REST apis.
During my sabbatical, I've decided to try making a Solid Server from scratch to see how complicated it would be... And turns out I got it working in a single day 🤯.
It's very experimental, but check it out if you're curious: https://github.com/NoelDeMartin/lss
⌛🧠🔥
Problem Solver. Software Architect. Entrepreneur.
Making Solid apps (solidproject.org), and pondering what to do next.