But you still need the user accounts. Which must be created and are verified by email. Then you have to generate tokens for them to call the api endpoint to add the star. I’m not saying it isn’t doable, but it would be non-negligible and GitHub is going to squash you back at some point creating all those accounts from one source.
How would the raspberry help? It is accounts needed.
That’s why there will be many more Luigi’s before anything improves.
Do you really use it or are you just adding an alternative to the conversation? It is an interesting concept (commutation) but not likely to supplant git.
Only kind of. That’s a backronym.
Well I don’t use obsidian as all. But as a matter of opening and linking notes, I use this tool because I like it, and it allows me to reference two separate vaults without issue.
I don’t disagree. I’m just saying the distribution of workload has an impact on what looks a good idea or too hard.
Because it changes the risk benefit profile of the choice. Imagine that your backend is 70k hours of work and your interface is 1k hours. Managing two interfaces isn’t going to seem like nearly as big an ask so other variables may get a higher weight. Of course those numbers are contrived for the sake of explanation, but if you still don’t think there are any circumstances in which others may value the benefits of native applications over cross platform applications, that’s fine. My point is simply that it may not seem like the trouble of managing two frontends is as insurmountable as you may think.
But I have a hard time believing you don’t think it is possible that there are any situations where one might reasonably believe it worth it.
Sure. Bitwarden provides its own backend. So that backend represents some portion of their code base. In the case of Voyager, Lemmy provides the backend. So that backend isn’t a portion of your code. So Voyager is 100% frontend. Bitwarden is < 100% frontend.
Recognizing you as a PWA developer; and a damn fine one, I get your take. But surely you are aware there are limitations to using PWA’s or other cross platform libraries. Sometimes maintaining multiple UI’s is the right choice. Especially if very little of your code is actually the front end. For you, Voyager is pretty much 100% front end, so that’s 100% of your code. But for Bitwarden, the interface is a much smaller proportion.
While the subjective assessment that quote handling in yaml is worse than bash is understandable, it is really just two of many many cases where quotes complicate things. And for a pretty good reason. They are used to isolate strings in many languages, even prose. They, therefore, always get special handling in lexical analysis. Understanding which languages use single quotes, double quotes, backticks, heredocs, etc and when to use them is really just part of the game or the struggle I guess.
That sounds like a skill issue. Something isn’t bad because you don’t understand it. Suggesting quoting is an issue for yaml is beyond the pale; it happens to be an issue everywhere.
A wholly different organization; non-profit actually. And it is open source. Those are pretty big advantages over WhatsApp. I’m pro xmpp, but Signal is an improvement over WhatsApp.
If a provided service is good and made accessible reasonably, I’ll use it and happily pay. As soon as it is intentionally obtuse or consumer hostile, say no more; I take to the seas.
But in all cases, I prefer FOSS first. It is generally better, more secure, has more vibrant communities, and represents a dying breed of freedom that we all need.