@gruber @paul @Gargron
Yes, the per IP limit is a major issue if multiple people are hitting the server from the same IP (think university students!)

Even gets worse if your app is server side then all your requests come from the same IP.
If Mastodon wants to have a lot of innovation, there needs to be a better anti-spam solution than per IP limits.
I understand why it exists for unauthenticated requests, but authenticated requests should be on per token basis not IP

@atomicpoet @Gargron
Actually at tweepsmap, we are all moving to our own instance shortly
I see Mastodon more like an email server, I think all companies will head that way.

Perhaps a managed hosting solution will be more mature and do multi-tenant setups, so companies can have turnkey installs like Google Apps, or Office 365, but for now we will stick with managing our own

@whatthecj
I had team members create an instance for the company, so learned few things

The biggest problem is seeing replies by others. Your instance will only see replies from "known accounts", and if you have a small instance it will have small amount of known accounts, so you miss out.

Relays help solve much (if not all of) this problem.

Few other cons:
2. Cost
3. Maintenance
4. Setup was a pain even for devs!

@atomicpoet
to be honest, a lot of these things can be solved with changes to infrastructure and architecture.

I tried to offer @Gargron help few times but got no response, I think he is just bombarded with notifications so he misses a lot of offers for help