[–] [S] 1 point 1 month ago

Personally, I needed a couple of very specific features that none of the options I found offered. It turns out there was one that did what I needed (which I was linked to later), but it was much too complicated for me to put on my parents' devices, so I made my own mini-app... it just ballooned into a lot more when I got a lot of users making feature requests.

As for why a lot of people are making these, I am guessing it's a combo of:

  • LLMs making "vibe-coding" accessible (to be clear, this app is coded by hand with some use of AI for troubleshooting mostly).
  • the fact that people are using VPNs to avoid the onslaught of identity-verification laws that are cropping up everywhere means many are switching from VPN-based filtering to Private DNS.

But that's just a guess.

As for why I kept at this instead of switching to one of the existing solutions; the main reason is that they either have bad or overly complex UX, or do a lot more than necessary. This feels like the best compromise between features and usability. That's all.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 month ago

    I was solving my own problem, Android blocked a few calls per week and I am getting 30+ every single day (from 30 different numbers.. with new ones coming every single day). At first I was blocking them using built-in block and thought it will slow down at some point but even with 1000+ blocked numbers, new ones kept coming

    The most annoying problem was that my phone and watch were buzzing for every call (so every 20-30 min).. until I sat down to build a blocker that treats everyone guilty :D

    Thank you very much for the wishes! I solved my own problem but also got traction on Play Store without any marketing so I'm glad it's helping others too :)

  • source
  • parent
  • context
  • [–] 6 points 1 month ago (1 child)

    Without the source code, it's hard to trust such an application especially when Android already does some of it, and there are applications on F-droid that do the rest. Good luck anyway.

  • source
  • [–] 0 points 1 month ago

    Oh please spare me the self justifying bullshit. You use the coding slop tool to make the slop code, it doesn't make you some amazing developer. If it's still around in a year it might be worth looking at. These sorts of things have a habit of self destructing, it's why so many people avoid them. My car wasn't made on the stolen data of humanity. I do my best to limit the use of LLM garbage, disabled the AI shit features on my phone. I use decent Operating Systems that have AI policies written with community consultation, I do what I can to shield myself from the cognito hazard. Just because heaps of people have herpes doesn't mean we all have to embrace it you fucking sheep. The sooner this fucking AI bubble bursts the sooner people like you will stop throwing these projects into the world like unwanted puppies on Christmas Day destined for the pound a week after the novelty wears off. Now I am done with you, have your LLM write all the vaguely condescending dude bro comments in response to me you want, I can't be bothered reading them.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago (2 children)

    Here you go then, feature suggestion: Disclose the use of LLMs to develop the project loudly and enthusiastically without evangelism. People who want to take a punt can, people who want to avoid it can, everyone is happy. If someone wants to let you know your project is the programming equivalent of a sweatshop, built on exploitation of other peoples hard work and contributing nothing but misery to the world, then having your LLM write a response won't convince them otherwise.

  • source
  • parent
  • context
  • [–] 0 points 1 month ago (4 children)

    That's the way you want to code that's your call. There is no ethical LLM, without exception they are all the result of a corporations theft, cheating and lies. We keep on finding proof that they have a negative impact on cognition and capability and that they shift the "cost" of projects. Used to be that to get a project off the ground the first step was to identify the problem you were tackling and then build out a minimum viable product, hopefully you would attract external talent to critique and or contribute.

    These days, vibe code the fuck out of it and slap it on github that afternoon. Of course without that period to grow internally the whole project is on shakey foundations, and a lot of things that should have died off in the early stages get released to the public before anyone realises they will never catch up on the technical debt.

    Look all of this is a long winded way of saying chuck your slop code disclaim out front. The people who want to engage with it will, the people who want to wait a year to see if the project explodes, implodes, or withers on the vine can do so. Also the people who choose not to actively engage with the corporate theft machine can just move along without feeling a compulsion to look at the code and comment on how the project is slop.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 month ago

    Absolutely, the Android community has been a lot more vocal about this. I actually had it on an old roadmap back when the iOS client was created, but I have not really caught up on it since the feature list was not 'finished' until last month. But hearing that this many people want that transparency, I would gladly bump it and will work on it as soon as the bugs are ironed out and Android is fully out. I admire people who are cautious, I work with security as my day job myself and would act the exact same way.

  • source
  • parent
  • context
  • [–] 4 points 1 month ago (3 children)

    This is almost unbelievable. Already trying the app out and it's great. How's this work from a legal perspective getting access to the music, I assume this isn't free nor maintaining the app. How are we getting this for free? Thanks

  • source
  • view more: ‹ prev next ›