@jeroenpraat Thanks! I'm close to pushing the MVP to github, still need to finish ActivityPub support and some other small things. I have picked a name, will be announcing that soon!
@dansup be careful how you brand this, so you don't get sued! But I'm so happy that someone is putting in effort to something like this!
@maloki I appreciate the concern, the name doesnt have "insta" or "gram" in it and I will differentiate the UI so its not an exact copy.
@pea I'll be pushing the code soon if you want to work together. I'm using laravel, its like rails but faster.
@pea No worries, if you are using activitpub our instances should have no problem interop wise. If not, I'm willing to support whatever federated protocol you are using.
@pea No, I was not planning on consuming activitystream objects without an image, anyone can subscribe but this is an image first service.
@pea Thats a good point, but consider how popular instagram is. I'm sure people would subscribe to a major brand on a federated instance just like they would on instagram. Now the brands can control and own their own instance. I think the problems we solve will help pave the way for this.
@pea @dansup I don't think it's in poor taste. I think that's how it's supposed to work. It's much better to filter out 95% of posts than to create special properties on top of the standard... Also people on your platform will likely not follow people who post 95% text content, they will most likely either naturally follow other users of your platform, or those from Mastodon/Pleroma who post a lot of pictures that fit with your platform, so don't worry too much about that imo
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!