@vinnl It seems cool, but I'm not sure it'd work. I thought about this because one of the problems I've noticed in virtual conferences is that after the main "talk", some people start talking but it's only one track. What's nice about physical conferences is that after the talk, groups of people form organically and you can enter/leave those group conversations easily. Maybe that wouldn't work in a virtual environment but it was just an idea I had :).
@Acaii@mastodon.social Is it this one? https://www.dw.com/en/coronavirus-russian-online-bar-shakes-up-self-isolation/a-52967919
#TIL that display:flex in the body breaks pagination when printing websites in Firefox :/ use display:block instead.
@panigrc I also thought of something similar after posting this :D
I'm still not sure which one I prefer though. This one may be easier to understand, but the performance is not as good. Of course, that depends on whether performance is important or not, the context of the project where this is being developed, etc.
I was vague on purpose to see how people react.
I've been searching for the Javascript equivalent of Laravel's tap helper and I couldn't find it, so I ended up doing it myself. Here's my version in Javascript & Typescript! https://gist.github.com/NoelDeMartin/16c4d390e7c310d0387761f9b561f102
#TIL that Github Actions logs expire, and I wasn't able to find when. I had been switching to them in all my repositories for convenience, but this is a blocker for me. Back to SemaphoreCI it is.
@pukkamustard so far I'm only tracking movies and I'm using schema.org. Eventually I would like to track tv shows, books, manga/comics, music, etc. But I can't say for sure, I prefer to have short-term goals and see how it evolves
@vinnl Hey thanks :) I'm using https://www.themoviedb.org/documentation/api
Here's a sneak peek of the #solid media tracker I'm working on! I've probably spent more time than I should implementing some animations, but I'm happy with the results! https://noeldemartin.com/tasks/implementing-a-media-tracker-using-solid#comment-6
I love styling with TailwindCSS and I've learned a lot about colors and design systems using it. Today I created a simple PWA to help building color palettes with it, check it out. https://noeldemartin.github.io/tailwindcss-colors-generator/
@vinnl Yes I agree :)
I wasn't too familiar with the Type Registry but I've been using it for a new app I'm developing and I'll probably use it going forward. In Solid Focus I'm specifically looking for `lifecycle:TaskGroup` containers in the root of the storage, and I use all the lifecycle vocab for relationships between tasks/containers.
@vinnl There is a couple of things I need to improve: Adding and reading from the Type Registry and giving "power users" more control over where to store them, like /public, /private, /inbox, etc. The last one is tricky, because I don't want to confuse users who don't know much about Solid, so I'm not doing anything about it for now.
@vinnl Yes sure :)
That's what workspaces are for, and why they are "special" lists. When users create a Workspace in the UI, that creates a new `ldp:Container` in the root of the storage that I got from `pim:storage` and I use the workspace name to create a slug. Inbox tasks are direct children of this workspace container, and you can create lists within which are also containers for tasks.
@vinnl Hi there :) If you read the description of the deck I have a brief explanation of the slides. This in particular is what you'd ask users in the "log in" screen, instead of logging into your application, you ask them where they want the data to be stored and ask for permissions. I actually use this package to achieve that: https://github.com/solid/solid-auth-client
Here you can find the slides from my talk at #BlockchainSpirit yesterday, thanks to everyone who was there! #Solid https://speakerdeck.com/noeldemartin/showcasing-an-app-that-uses-the-solid-protocol-for-decentralized-storage
⌛🧠🔥
Problem Solver. Software Architect. Entrepreneur.
Making Solid apps (solidproject.org), and pondering what to do next.