O O O O O OO (OOO)
O O OO O OO O O OO OOO O O OO OO OOOO OOO OOOO O (O(OOO))
O OO O weon isekai goon OOO O O O OO OO OOOOO OOOOOO O OO)))
O OO OO O OO OO OO O OOO OOO OOOO OOO OOOO OOO OOOO((OOOOO))
O O OO OO O O (OOO))(OO)
_______----------. ___ _____ ___ _____ ___
--' `| .----. |---------| |---------| |----' `[2024]
|| |____| | |__
|--------- FEDDIT.CL ____ _________________ |-'
| | 2024 /----------------(____)/,---------------_||__
| |========/ / \ / _\_/_<|==(____) \ / _\_/__<|==[__]_\\_
---._---_./=|,-._,-\ o---{o}=======\>=[__]o---{o}=======\>=[__]----\=
___(O)_(O)___(O)_(O)___\__/_\__/_\__/_______\__/_\__/_\__/____(O)_(O)_\_
___
I’m not really sure what’s going on. There’s a 3-6 day delay expected with F-Droid. It looks like F-Droid is receiving updated releases from GitHub. Maybe give it a couple days.
Yeah. I fixed a lot of bugs this past two weeks that haven’t made it into F-Droid yet. As Blorp matures, I would expect this to be less of an issue. But for now, things are a little chaotic.
I try to write automated tests where I can, and I’m trying to make less jr developer type mistakes. But the stakes are lower than my day job, so admittedly I make some riskier decisions.
But I’ve matured a lot this past year. The other day I discovered a bug that I wanted to fix, then I stopped myself. I realized this was such an insignificant bug, and fixing it quickly would be much more likely to create a much bigger bug. Now I’m rambling lol.
Anyway, I would love to better utilize the Android and iOS beta tracks. That would take a few more dedicated testers on those tracks who are willing to submit feedback.
Also the ability to directly download images instead of having to share them to myself.
You have to precisely use a capture of my last gooner posts as an example? That’s despicable!
O O O O O OO (OOO) O O OO O OO O O OO OOO O O OO OO OOOO OOO OOOO O (O(OOO)) O OO O weon isekai goon OOO O O O OO OO OOOOO OOOOOO O OO))) O OO OO O OO OO OO O OOO OOO OOOO OOO OOOO OOO OOOO((OOOOO)) O O OO OO O O (OOO)) (OO) _______----------. ___ _____ ___ _____ ___ --' `| .----. |---------| |---------| |----' `[2024] || |____| | |__ |--------- FEDDIT.CL ____ _________________ |-' | | 2024 /----------------(____)/,---------------_||__ | |========/ / \ / _\_/_<|==(____) \ / _\_/__<|==[__]_\\_ ---._---_./=|,-._,-\ o---{o}=======\>=[__]o---{o}=======\>=[__]----\= ___(O)_(O)___(O)_(O)___\__/_\__/_\__/_______\__/_\__/_\__/____(O)_(O)_\_ ___Omg
2024??? More like 1824!!!
y not?
Yes! You’re not the first person to ask for that. I’ll try and get that into the next release.
Translate isn’t ready yet, but at some point, I could use some help writing translations. If you’re interested.
For sure!
Uuhhh, also, the version posted on f-droid seems outdated or buggy.
I’m not really sure what’s going on. There’s a 3-6 day delay expected with F-Droid. It looks like F-Droid is receiving updated releases from GitHub. Maybe give it a couple days.
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/26267
I originally downloaded it from there, but was buggy and couldn’t log in, the google app store version works fine.
Yeah. I fixed a lot of bugs this past two weeks that haven’t made it into F-Droid yet. As Blorp matures, I would expect this to be less of an issue. But for now, things are a little chaotic.
I try to write automated tests where I can, and I’m trying to make less jr developer type mistakes. But the stakes are lower than my day job, so admittedly I make some riskier decisions.
But I’ve matured a lot this past year. The other day I discovered a bug that I wanted to fix, then I stopped myself. I realized this was such an insignificant bug, and fixing it quickly would be much more likely to create a much bigger bug. Now I’m rambling lol.
Anyway, I would love to better utilize the Android and iOS beta tracks. That would take a few more dedicated testers on those tracks who are willing to submit feedback.
Anyways, along with boost, this has been the best app I have tested so far, props to you!