I think we will see in the future algorithmic feeds addiction rehab, algorithmic feeds self-exclusion lists (like for casinos) and even algorithmic feeds ban, which would probably be a net positive for humanity.
276 karma · joined October 6, 2016
https://github.com/255kb
I think we will see in the future algorithmic feeds addiction rehab, algorithmic feeds self-exclusion lists (like for casinos) and even algorithmic feeds ban, which would probably be a net positive for humanity.
And it was doing exactly what is described here, using a reimplementation of mongodb, in the frontend: minimongo.
Remote: Yes
Willing to relocate: No
Technologies: Angular, React, Nestjs, Node.js, JS/TS, Electron, Java, Google Cloud/Firebase, SEO
Résumé/CV: https://www.linkedin.com/in/guillaumemonnet/
Email: guillaume[at]1kb.software
While bootstrapping http://mockoon.com I'm freelancing to keep the lights on. I'm good with building MVPs, challenge a crowded roadmap, cloud cost killing, email deliverability, desktop apps distribution, and tons of other things. If you need help to ship fast and cut through the noise, let's talk!
It’s probably due to a few famous projects being massively successful (think Vue.js), but I believe it’s directly tied to the project's size (audience), the maintainers' activities (conferences, etc.), and the type of audience. This last point is important—individuals are more likely to donate, while companies often need months of convincing, and it usually doesn't work, or they expect their logo everywhere with analytics (CTR, etc.) to justify it, which is basically advertising.
I have a sizeable seven-year-old open-source project (Mockoon) and, over its lifetime, I’ve received low four figures in donations, which is awesome, but far from enough to make a living from it.
Now, I’m creating a cloud version of the software, which has started generating revenue. It’s a lot of work, but leveraging the open-source success and sell something seems like a safer path.
I never tried to add magix links, but I added Google Sign in to my SaaS several month ago, and since then, it accounts for more than 90% of new sign-ups (users are devs, so rather tech savvy and privacy aware). I'm now convinced that no other method is a priority (I still have email/password of course).
Just so you know, there is an app called Traffic Parrot (https://trafficparrot.com/). They operate on the same market, so they may not like the name you chose.
Fast forward months, it's a non issue despite having paying customers. Not only I grossly exagerated the invidual user's resources consumption, but I also grossly exagerated the need for top notch k8s auto-scaling this and that. Turns out you can go a long way with something simpler...
I was already aware of it when being a noob dev 10 years ago, and could easily write a rule to enforce auth + ownership in the rules. No way, seasoned devs can miss that.
The only platform where I can have more meaningful interactions for my company is LinkedIn. I can easily react to a post, gain some followers, or make connections. However, every time I scroll through the feed, I'm baffled by the amount of garbage posted there: all these fake stories about how a pigeon taught someone a lesson on finding product-market fit...
So, personally, I'm done with any of these platforms, but for a company, I would say LinkedIn still has some merit. Maybe also because it's an all in one: connect with people, post company's updates, recruit, create events, etc. As for alternatives, I know none.
Scrum gives them tools to understand if there is progress or not: Is the burndown chart nicely on a downward trend? Are tickets closed? Is the sprint "green" or not? I won't blame them. They are clueless. But I hate it!
Booklet: https://imgur.com/a/6mUVpXm
Edit: another question: do you advertise on your website the possibility to use Azure billing?
There are many steps involved: - identifying the relevant markets, probably something like office applications market and chat applications market. - whether the company has a dominant position on one (likely MS being dominant on the office apps market) - checking if a specific action could be considered as a abuse of dominant position, restricting the competition. Here it would be MS bundling the app, giving them an unfair advantage on the chat apps market.
They would likely be to assess the real damages to the market, whether or not competitors were able to do business or not, etc.
It's not all black or white, like any legal subject.