👋 Hello @qwe234@twtxt.net, welcome to twtxt.net, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
👋 Hello @qwe123@twtxt.net, welcome to twtxt.net, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
👋 Hello @yujungcheng@twtxt.net, welcome to twtxt.net, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
Right now i’ve done planning my work on it and will be working on the app in the weekends (my only free time).
I’ll be publishing my updates through the #pwa tag, you can check that up to see what going on and feel free to give your opinions / ideas, I’ll try to make everyone happy!
(#yo2bebq) @prologic@twtxt.net Nice option, I have tried it before but didn’t understand from the description what it does, now it’s a huge difference, I’ll stick with the Flat.
(#qkqefka) @ullarah@txt.quisquiliae.com I check twtxt just now but it seems the way to go, the js code in the article feels a bit excessive to me.
A simple class added to the post that have more than X lines should be enough.
And by just nullifying the max-height with none or initial should do the job, or even better having a read-more class that add the max-heightand show the button, it would be even cleaner.
Hello everyone, I’m back with another update for the #pwa!
I finally planned out how the app will be built.
First I’ll clean the project structure to be standalone and not as a theme, then I will work on every part separately, trying to be contained to let everyone try it out fast.
For the API I’ll be using this as a reference, @prologic@twtxt.net help me if there’s anything missing there apart from what we already said (bookmark, etc.)
The first part will be the Discover view with no auth.
I’m always been a fan of tiny and minimal tools, usually a quick glance is enough for me to understand if something is in my style.
Before replying to you I actually checked the source code of pass as a reference and was welcomed with walls of text that felt pretty unappealing to me.
(#ubj45tq) @novaburst@twt.nfld.uk You call it an actually boring password manager yet It’s really inspiring on how much you can strip down and still have something so versatile that you’ll actually use as an alternative over pass. 😲
Seems like the SSL certificate for tilde.team expired. Maybe twters following my feed from Gemini will have some problems with that. But this should be fixed, soon! ☺️
(#53wqhjq) @prologic@twtxt.net Yeah, I saw gopass and the android client too but I don’t like the fact that I have to take around a gpg key, I prefer having something deterministic of easily replicable even without the original at hand.
(#53wqhjq) @novaburst@twt.nfld.uk Did you fork it from pass or is something completely different? I was thinking of building one myself for a while now.
I don’t even keep my own passwords written anywhere, I just need to remember the username, that’s why I thought of using a stateless approach AND a password manager for the others accounts.
(#puslfoq) @novaburst@twt.nfld.uk I too have to keep track of lot on accounts, I use an org-mode file to know where I have which account.
I even have to keep track of other people’s accounts too, luckily only for storage purpose, since they can’t understand the importance of remembering their own passwords, I can count to over 140 in total. 😭
(#xd6wama) @prologic@twtxt.net Having everything under one endpoint is better for other integration too I think.
I’m missing endpoints because I didn’t see them under the spec page, I should check the repo then, I’m also missing the response structure, but I can directly look it up later when working on the API.