@martin Nice, I forgot to mention kill-the-newsletter, but I use it too :D.
Didn't know about openrss.org :)
@martin That's great :) I've been using RSS for ages and I think it's great.
A couple of tips, if a website doesn't have an RSS feed you can use something like FetchRSS.com to generate it yourself. And you can also subscribe to any github repo/subfolder with the following url: `github.com/{user}/{repository}/commits/{branch}/{path-to-file-or-folder?}.atom`
For example: https://github.com/moodle/moodle/commits/main/local/upgrade.txt.atom
In this talk, @aveltens nails THE most important point of Solid. We don't need a killer app, we need an ecosystem of apps that work together!
Owning your data is cool and all, but these experiences show the true power of Solid.
One of the best things you can do to improve the stability of your apps is writing tests, and Cypress is the best tool for the job!
To help you with that, I just released a plugin that makes testing Solid Apps super easy. I hope you find it useful :).
@rosano @jessmartin What do you mean with "interop-pilled"? Does it mean being convinced that it is important? Or learning about it? Or both?
Maybe you should add Cambria to the list :) https://www.inkandswitch.com/cambria/
@nickform Thank you :)
The framework is still a work in progress, and I don't even have written any documentation yet so I don't think it would be easy for others to use. But eventually I'd like to do it, and one of the core ideas is that all the "best practices" such as how should a Solid Login behave come baked in with the framework :).
I just finished migrating my first Solid App to the framework I'm working on, AerogelJS!
If you're curious to see how you build an app with the framework, check out the source code.
Is it easy to understand? Let me know what you think I could improve!
Today I published a blog post talking about what my ideal world of software looks like. I call it Skeuomorphic Software, check it out!
I recommended this CSS course last year, and now it's 50% off! https://css-for-js.dev/
There's so much content that after a year of starting it I'm still not done :O (I dedicate 1 hour/week). And I still enjoy it like the first day.
If you're curious, you can read about my experience thus far: https://noeldemartin.com/tasks/learning-css
> Even when you #OwnYourData 100%, many might find little agency in being able to 'edit properties on JSON objects'. What level of handedness would be meaningful to them?
(with @jessmartin)
https://utopia.rosano.ca/interoperable-collaborative-apps-with-jess-martin
If you're curious about the different approaches to make Solid Apps, @megoth just launched a website comparing some of them. It's also a great resource if you know nothing about Solid and want to learn some basics :). Check it out!
I feel like our industry is increasingly treating accessibility, performance, and security as box-ticking exercises:
- Get WCAG compliance
- Get green on Core Web Vitals
- Update all your vulnerable dependencies
Maybe this is better than the status quo (since we're so bad at these things), but I worry it removes a lot of the thought and artistry from the job. If all your energy is spent on box-ticking, there's no time for anything else. And management thinks it's "done" when the box is ticked.
@thisismissem Well it's not super nice because the UI is blocked longer than it should, which is a problem I'm aware of. But it's a trade-off I'm willing to live with for now.
Thanks for your feedback, I'll keep it in mind when I work further on this :).
@thisismissem Hm I see what you mean, but I think that's not an issue in my case. There is no "restoring session" state because the $solid service is not ready until the session has been restored (or failed restoring). So by the time the app has booted, you're either "logged in" or "logged out". Services have this concept of "booted", and until they are fully booted the app doesn't even render anything on the screen.
@thisismissem Hm I'm not sure I understand what you mean, but the authentication information is exposed through the $solid service. You can check if you're logged in with $solid.loggedIn, for example. And by default it initializes logged out, but you can configure it to auto reconnect on start up.
I guess you could say it is a state machine with the following states:
- Logged out
- Logging in
- Logged in
Maybe I could improve that and make it more explicit, is that what you mean?
@thisismissem Hey thanks :D.
It does use Inrupt's library for authentication, although it can be configured to use something else (Inrupt's library is the one used by default).
What do you mean that it doesn't correctly expose the state, can you elaborate?
I just posted a video showing what you can do with the framework I'm working on, Aerogel. Check it out! https://www.youtube.com/watch?v=JXyCH_S9efk
Just saw that my apps Media Kraken and Umai were featured in Tim Berners-Lee's recent keynote at the WeAreDevelopers World Congress :D. Thanks Tim!
βπ§ π₯
Problem Solver. Software Architect. Entrepreneur.
Making Solid apps (solidproject.org), and pondering what to do next.