For #simpleanalytics I want to hide the user's IP address. I don't want to get the real one anyway. But having a HTTP handshake is I think not possible. Maybe a proxy? But does that work for a script in the browser? Any ideas?

If the user requests a resource from your server you need their IP address in order to respond to the request. So no, I don't think it's possible. You might be able to put a CDN like [Cloudflare](https://www.cloudflare.com) between you and the user, and perhaps you can configure the CDN such that it doesn't forward the user's IP address, but then they would still get the IP address. That's probably not what you want either. The next best thing might be to just scrub your server logs of IP addresses.

- A) charge users to access the list of products - B) charge makers to be featured on list/website - C) both

Can you share a link with more info? I vaguely remember something about a list of products made by indie makers. Is that it? In that case my question is what the point of the list is. The revenue model should flow from there. If the goal is to stimulate purchases for indie makers, then I'd focus on that first before worrying about the revenue model. If you can generate enough sales there will be plenty of options to monetize later on. However if you're just starting out with few sales I imagine it will be hard to get makers to implement an affiliate model (not worth the effort for just a few sales), nor are you able to charge a lot for advertisements (again, not worth the investment if there's only a few sales). Charging early is generally good advice, but only works when you've established you can provide value worth paying for. For e.g. SaaS products this generally easier than the type of product you're looking to create.

I wrote code that forks and queues up and stops child processes but the processes themselves use up quite a bit of CPU. Is there a library that's particularly helpful with building these types of async/cron-like Node services? Wasn't finding anything in my search. Should I consider offloading that to another server or is it just time to up the CPU of my virtual machine?

You should try using a queue eg. Bull queue. You can run the workers on the same server or somewhere else (it's backed by redis). Notre sure if it 100% fits your use case since as far as I understand you seem to want to wait for the job to complete before sending a response back or something? In which case you should wait on the output of the queued job (that's writes to a db or something)

I've noticed that the replies to big famous social media accounts do pretty well. Often the top reply racks up well over 300 likes and gets followers etc ... Whenever Kanye tweets I want to autoreply with the link to https://phonemekanyewest.com and maybe yeezy.dating just to help spread the word amongst ye fans. ive used twitter npm module b4 but can't work out how to autoreply!

Try something like var stream = T.stream('statuses/filter', { follow: Kanyes_screen_name }); stream.on('tweet', function (tweet) { console.log("reply here"); });

With #upnup you will be able to create a personal professional site very quickly. It is important for both the user and me if they share it with their friends because we both get more visibility. What's a good way to achieve this?

It's tricky to provide very concrete ideas without seeing the product, but here are some generic suggestions: **1. Make them understand the value of sharing** It might seem obvious to you, but people have a million things going on at any given time so you need to get them thinking about this. Instead of just saying something like "share your site with friends" tell them about the benefits of doing so. I don't have a whole lot of information about your product, but it seems like the benefit would be getting more leads? In that case you could use language such as _"show off your new site to your friends and get more leads"_. **2. Make it easy to share** Remove as many hurdles as necessary so it becomes really easy for people to share their site. For example add share buttons with pre-written texts, provide 1-click sharing if possible (e.g. if they oauth'ed their social account), etc. **3. Show them the benefits/results of sharing** You want to create a positive feedback loop where the user gets 'rewarded' for sharing their site. If they know it works, they will keep doing it. So for example you could show website analytics (clickthrough counts, etc).

Feel free to get emotional, philosophical, factual, anything! Situation is hypothetical so can be that the team launched before you or vice versa.

At first I laughed, then went "wtf", then felt better because we each had different goals in mind. It was in 2016 when Telegram launched Telegra.ph, and #writeas had already been out for almost 2 years. After I saw the launch, I actually posted Write.as to HN for the first time, and the next day it was surprisingly on the front page of PH. It didn't do as well as Telegra.ph, and I had to answer questions about how the two platforms were different now, but the PH launch sent my own product in a new (more upward) trajectory. Overall, once I got over that initial worry of having to compete (something I never worried about before), I focused again on my own goals and then kept going. It's good when many options exist in the marketplace, whether you're making the products or consuming them.

Meet the maker community

Meet the maker community