Adding `ktlint` now results in a big PR (changing many files), but I think it's a nice investment for the scalability of the project. What do you think, #[0] ?
59 is a nice number ☕️ https://github.com/nostr-protocol/nips
In the context of building software, think about constant and small iterations. This way, you can adapt quickly to the different needs along the way.
Good morning, team! Second week of March. There we go! 🤘
Amethyst 0.24.0: Here's my badge, officer.
This is read-only NIP-58. Notifications, Profile inserts, and ThreadView for badge awards are working. You can activate your Badges here: https://badges.page
Read-only support for Badges (NIP-58) by #[0]
Adds zooming on profile picture and banner by #[1]
Refactors ui/dal Filters by #[2]
Fixes showing the R.string.first id instead of text by #[3]
Fixes result order in the search screen by #[4]
Download: https://github.com/vitorpamplona/amethyst/releases/download/v0.24.0/app-release-v0.24.0.apk
I love contributing to this project 🍻
#[0]
You can submit another PR with an improved version as a follow up iteration. There are new releases every week (almost daily) 😄
Your code quality is directly proportional to how easy it is to write automated tests for it. As simple as that.
I would be happy to contribute by providing french translation.
Don't know how, someone can help me ?
Sure thing! It's pretty easy, you can use this PR as reference https://github.com/vitorpamplona/amethyst/pull/181/files
You need to create a file `app/src/main/res/values-fr/strings.xml` (you can start by copy-pasting the english version) and replace the EN with the FR translations in that new `values-fr/strings.xml` file. That's all 😃
If you cannot build it in one day, the problem is too complex. Break it down and/or find a smaller problem that you can solve in a day that helps you work towards the greater goal.
Reduce friction for good habits and increase friction for bad habits.
Reduce friction for good habits and increase friction for bad habits.
Yes! You cannot build the perfect and right software from the very beginning. However, you can collaboratively work toward better software on the daily basis.
Make the code work first. Then clean it up. The more you delay cleaning your code up, the more tech debt your project will accumulate.
With the right knowledge, environment, and support structure, everyone is capable of upgrading themselves.
Test-Driven Mentality is the key 🔑
L177 - Nostr ¿y ahora qué? junto a #[1]
#[2]
#[3]
y #[4]
En un podcast de mesa redonda con estos 4 magos de #Nostr 🧙♂️ tratamos:
- lo sucedido en los últimos 4 meses
- el efecto #[5]
y #[6]
- retos de 2023
Ya disponible
🟡 https://bit.ly/L177_NostrFountain
https://video.twimg.com/ext_tw_video/1622337249986715651/pu/vid/1280x720/s4cH8IT3fbcB9HCB.mp4
Qué genialidad. Gracias por el podcast! 🧠🤘
This is really useful, thank you!
Woho! I think I managed using the Alby app, thank you. The next level will be to learn how to do it with my own address, but for now it looks like some progress already! 😄