https://github.com/Fingel/gelly
I thought it would be pretty simple, but here I am almost 6 months later still adding features. The positive feedback has been nice, though! People seem to appreciate (like I do) that its fast and doesn't use Electron or some other cross platform toolkit. Learning a lot.
It's not vibe coded. Sad that I have to make that qualification these days, but here we are.
Vibe coding signifies a lack of control over one's own code and generally only if it's to generate ideas or throwaway. The negative connotation that goes with it is appropriate too.
In reality any project that takes 6 months means your have invested a lot of time thinking about the code, in which case LLMs become more useful for the things you care about e.g. maintainability, forcing LLMs to bend to your will, which is like saying: " I know this design is the best so just make this instead of whatever abstraction you think is better".
https://github.com/Fingel/gelly
I thought it would be pretty simple, but here I am almost 6 months later still adding features. The positive feedback has been nice, though! People seem to appreciate (like I do) that its fast and doesn't use Electron or some other cross platform toolkit. Learning a lot.
It's not vibe coded. Sad that I have to make that qualification these days, but here we are.
I've always noodled about this marketplace idea where an optimization algorithm could match your interests and a dollar amount you can afford to let you rent/buy artist's music. The optimization would maximize the purchase of the differently valued music(analogus to the weighted knapsack problem but this could have multiple solutions, knapsack is a nice way of thinking about it logically, in reality implementation may be completely different) based only on your interests, like history and dollars u have. I am wondering how might one apply a distributed systems approach without having music pirated and shotgunned all across the internet? Like how would you quickly match a person to all the available music metadata? How would you model for interest matching if the music library is spread out across multiple nodes.
I would imagine a lot of people are ok with paying 5-10$ a month instead of 15-20$ for music they like from a set of artists they like.
I would imagine a sort of hybrid qualities of volunteer efforts like wikipedia, new problems like advent of code and benchmarks like this. The goal? It would be to study the collective effort on the affects of usage to so many areas where AI is used.
[MedWatch](https://www.fda.gov/safety/medwatch-fda-safety-information-a...)
[VAERS](https://www.cdc.gov/vaccine-safety-systems/vaers/index.html)
[EudraVigilance](https://www.ema.europa.eu/en/human-regulatory-overview/resea...)
How does this shakedown work for companies/orgs that have large number of paying iOS DAUs?
What am I not getting here?
I'm no material scientist, but this seems pretty impressive to me that Apple's economy of scale can pull this off, and upgrade the device capabilities, for less than $30 USD.
Do they disclose who the manufacturers are and what standards do they adhere to when recovering cobalt from scrapped batteries?
One can easily implement a nationwide system like this. You can trust people in your own community. There are no central govt actors. In such a system no one has any knowledge of which service you are proving your identity/age for and the cryptographic approval can be done without any ids being exchanged. The input to the ombudsman is a hash you provide which he can sign with his key and send to a server, that can ask the ombudsman: "this thing you are signing is for age verification > 18, check persons ID and press confirm if that's the case". The ombudsman presses confirm after checking the id and you are done. Every city municipality can elect a local councilman/notaries to do this, for a small fees.