Creating the Firefox extension was surprisingly "easy". Let's see if we can bring it online.
#gooti
Hehe. In both cases you describe I would agree with you.
Will most likely go via the options page.
Interesting thought.
I would say it depends on the situation and your strategy.
Example:
In a not yet developed market environment that you yourself will not be able to develop alone, sharing "insights" might draw competitors that help develop the market. And in the end, everyone might benefit.
Modal dialogs in browser extension popups suck (in Chrome and Firefox).
A popup is immediately closed/hidden once the modal dialog opens and its connection to the popup is severed.
I need to think of another way to upload data to the extension.
#gooti
Second attempt.
#gooti

The Chrome extension hopefully will be available soon. Let's see how long it takes Google to review and (hopefully) approve it.
#gooti
After reevaluating my current approach, I have decided to aim for a broader solution.
This means that #gooti should - and hopefully will - consist of a #Chrome extension, a #Firefox extension and (on top of Chrome and Firefox sync) its own sync service for those who want to use it.
That sounds like the right approach to me, even if it's much more complex in the end.
I can even think of integrating "bring your own sync server". But one step at a time.
Chrome extension will be the first step.
#gooti

Pop!_OS is really running smooth.
"Gooti" sounds nice.
#gooti
Writing a Chrome extension really isn't that hard (if you have other examples to look at).
True. I can ignore legacy media. However, I cannot ignore the reality that this media creates (even when it is completely build on lies).
After upgrading TUXEDO OS and thereby breaking my installation, I am switching to another linux distribution (again).
I have Pop!_OS on another dev machine but will give Zorin OS a try now.
I don't think that relay developers are dead inside.
I am Sam Hayes