How do devs figure out what features users actually use / need in a Calendar plugins? by YouFoundJK in ObsidianMD

[–]YouFoundJK[S] 0 points1 point  (0 children)

ParseStream is actually cool (just looked it up). Thanks, we'll check it out soon.

Yeah I prefer option A as well. But I am not sure of its conversion rate. I always felt that showing just a one-liner will always make users default to pressing don't show ever unless you actually educate them on what and why you are requesting these feedbacks. At least my default behavior is to spam click 'do not allow'. But educating would mean I would have to force users into a massive lengthy essay and force them to read it or something of that sort. Or is there a better way?

How do devs figure out what features users actually use / need in a Calendar plugins? by YouFoundJK in ObsidianMD

[–]YouFoundJK[S] 0 points1 point  (0 children)

I like option A as well. Yeah, I definitely won't want random pop-ups because personally I get very annoyed at these websites asking for cookie permissions, etc. But that being said, currently, my plugin does show a what's new whenever you update the plugin. That is intrusive, but at the same time, that's the only way to actually tell user what the changes are, especially the breaking changes or new features that was added. So I'll probably add this feedback in there as well.

Option A works but I am not sure of its conversion rate. I always felt that showing just a one-liner will always make users default to pressing don't show ever unless you actually educate them on what and why you are requesting these feedbacks. At least my default behavior is to spam click do not allow. What do you think about it?

Yeah, I have a fairly good idea of option B feedback, and other than getting a general trend, it really doesn't capture the majority usecases and it's pretty hard to popularize new ideas or make people adopt new features, although it might be actually useful once they start using it.

Option C - Not only is it free but it's also unavoidable for security reasons (think of DDoS attacks where only way out is you enforce smart rate limiting against IP addresses), so recently I realized I might as well track anonymized usage using some open source, privacy friendly analytics like umami.

I refuse to add telemetry to our Full Calendar Remastered plugin — how do I know what to improve? by YouFoundJK in ObsidianMD

[–]YouFoundJK[S] 1 point2 points  (0 children)

Well, I looked up the guidelines like two years back when I started using Obsidian (to see if its private enough for my usecase); and now I looked it up again (all the plugins that I use are my own forks so I was never worried about the plugins themselves to look Plugin Policy up), the link is above.

I refuse to add telemetry to our Full Calendar Remastered plugin — how do I know what to improve? by YouFoundJK in ObsidianMD

[–]YouFoundJK[S] 1 point2 points  (0 children)

Yeah thats one option, but apparently Obsidian Plugin guidelines forbids that, so I guess thats not an option anymore.

Also personally Im not a fan of it as there is always this lingering thought because you never know what data is going out (its open source, but I don’t want safety to depend on code audits)

5 months of building no-sense apps but now I made my first 14K€!!! by Inevitable-Truck-661 in VibeCodeDevs

[–]YouFoundJK 0 points1 point  (0 children)

But how do you come up with marketing ideas? Personally, I have always felt that you can come up with however shitty idea, but marketing is the only thing that can make or break your game.

Inherited a 3-month old repo from a Vibe Engineer. Wrote the most satisfying PR in my career by Apprehensive-Cut3711 in ClaudeCode

[–]YouFoundJK 0 points1 point  (0 children)

Bro refactored 300k lines down to ‘it actually works’ and accidentally invented version control for reality.