meh
1 Like
meh is correct
Going once, going twiceā¦
1 Like
I can manage requests if there is a GUI
And if it only takes a few seconds per request
2 Likes
Takes long in the gui.
@TripleU whaddya say
Sorry was busy before. Iād love to help
But instead of what @Shalom_Karr said I need that it should be doable from terminal.
Just kidding anything is fine but one condition Iām not committing forever.
Edit: actually I donāt know what the rules of kosher are. If you can clarify pm me
2 Likes
Can do all from the terminal. Thatās what I do.
Need to at least specify a slight commit timeframe. Not worth giving access otherwise.
Meaning? Like how often I can do it? (Iāll contact you privately soon)
1 Like
I can probably commit for a week or so But I am going to get busy again probably
I wish I could do longer then that
Waiting. Pmed you in telegram.
1 Like
Do what ya gotta do.
Did you ever add that channel?
https://music.youtube.com/channel/UCL0auemfwJ0_Hp835-F9yPQ
on a tcl flip 2 after installing the app the only thing you can do is click agree to the terms of service there is no next button
Lower your density.
but it would be nice if they can fix it
I doubt this is only myself.
And for other reasons itās not very practical to just say
And expect it to be normally possible for a human to do so. As well known, in many situations itās easier to rebuild from scratch then edit a unknown codebase. Obviously thatās not the case here but Iām bringing out the point - that at least myself (and I believe same goes to many others) would love to help. (Some more, some less) But just open sourcing (which is great) wonāt magically fix everything without more detailed ways how others can join/help.
Again I really appreciate all the work and donāt wanna see the project shrinkā¦
And as I said my offer still stands that if thereās anything I can help you can reach out here or privately and Iāll try my best
3 Likes
I donāt know if or why people think I know how to develop Android apps.
My process for understanding an android codebase is like this.
AI exploration and documentation of each part separately, checking up things when I feel itās wrong, and testing after minor changes.
Testing is successful, update my documentation and brain. Not successful, update my documentation and brain.
By doing this for a while across multiple projects, I keep understanding more about architecture and make better decisions.
I almost deleted this because I felt ashamed of my extensive AI usage. But then I realized, this is the greatest thing that has ever happened in tech. Iām a guy who was making posts like the one that said where can I learn everything about coding, not knowing where to start.
You learn by screwing things up and not making the same mistake again.
Off topic, but how do you think I know where to look when there is an issue with a phone? I probably bricked that one 50 times. I have quite a few phones that are actually bricked beyond repair.
You learn more about security. Architecture. Cleaner code. Debugging.
Disclaimer, do not just yolo and make a database where people store their sensitive data. AI is NOT ready for that.
But stop being cheap and buy a subscription for $20 a month. $20! You spend that on stupid things without even thinking about it. Explore.
Try.
Try.
Try.
Donāt be afraid to hit errors or canāt your head against the wall. Break things. Explore new topics. Be curious instead of asking others to do simple things for you.
Man, I went on a rant.
Iām not gonna lie, Iāve always been a technical guy, and Iām really good at learning new things, fast. That does give me an advantage.
That does not mean you canāt try. Just build something simple! Then make it bigger, and bigger, and bigger. Document everything. Blablablablabla
Hope this answers all your points.
12 Likes
Well said
1 Like