Another thing that I like is considering not what I can do to “change my life in a year” but “what can I do tomorrow to improve my life even a little bit right now?”
Instead of getting caught up on larger things that might take years to achieve, if I consider something I can change right now that will make tomorrow a better day, those changes will add up much more quickly and noticeably.
Even if I can’t think of something, that’s fine. I can accept that, and just move on to the next day. The important thing is to ask myself this every day, so that I can give myself the option of making that change and having that reflection.
So this usually happens if the user doesn't enter a valid domain when signing in (bad UX, need to fix that).
I don't know what would have caused it in this situation, but if you click out of the dialogs (there definitely might be quite a few...probably like 4 or 5) then go to Profile->Settings and remove the account, you should be able to sign back in.
Can you try that and get back? I don't actually know what would have caused that to happen though...I can see there isn't a host there though for the selected account, so I'm pretty sure something happened to the host.
So in your opinion would you rather see it be an OpenCollective or an in-app tip jar? There's ups and downs to both.
On one hand, using OpenCollective would have a 10% fee which is lower, but would have less "publicity" to it. On the other hand, the in-app tip jar would be more visible but would have a 15% fee on it (I'd have to make it recurring to even get that percentage, there's a 30% fee on non-recurring transactions IIRC).
I'm fine with either, or even both if that's something that would make more sense.
I’ll write up something on how this can be done. I also think we are setting up something web based where you can easily contribute the translations without needing to use GitHub or anything like that.
Yea I have made it so that the image will only fill 90% of the screen height at a zoom scale of one (if you zoom obviously it will fill the full thing).
Swiping is now just a matter of velocity. There’s no required distance to reach for it to close, just as long as the swipe itself is fast enough. (You also have to be at a zoom scale of one for this, since obviously you might have a high velocity swipe when in zoom).
The issues like what you were having should be pretty much fixed, but I’m going to keep tweaking this thing. It’s quite a bit of weird logic to get it right and there’s still some work to be done, but it’s a huge improvement over the current implementation.
There’s already a related project underway using that name for KBin and (eventually?) Lemmy.