What is GramAddict?

[philip-ulrich]

Introduction

The original insomniac project has gone closed source and paid. Along with that, a new feature as well as some old ones have been locked behind a paywall. Some might say this is the natural progression of software - and you may be right in some cases. The main issue was that people like myself were actively contributing to the project and 1) Now cannot 2) Would be profited off of with no benefit to ourselves. IMO, the more FOSS software the better and I originally contributed thinking this would remain open source like it was. This project is an attempt to fork this into a new and actual FOSS project that developers can continue to contribute to.

Funding

All great projects eventually grow to where they require multiple people owning it or a source of funding. When you start open source and let people contribute, typically people who already did contribute, who tried to contribute, or who were planning on contribute feel slighted when the project goes closed source. As long as I am alive and kicking, this fork of the original will NEVER go closed source. If we ever determine that we need funding - it will be voluntary and/or done in a way that the source is still available and the people developing the project will still be able to work and hack on the source... even to the point of unlocking features otherwise "locked" behind the paywall. To be clear though, I would like to avoid any type of funding aside from voluntary donations.

What's next

It sounds like there are others that are in the boat for forking, so let's come together and discuss this. Maybe we start up our own discord server to help facilitate the discussion. Probably best to stick to this GH issue for now. I'd like another experienced Python developer to co-own this project with me (in terms of GH ownership) and we'd put it in it's own proper org so it's not under any one persons name. We also need to do all the TODO below plus more. Let me know if you are interested in being a co-owner of the GH repository or if you plan to contribute below.

TODO

• Rebase to v2
• Give it a new name! Because we can't live off of the old one.
• Find contributors! If you're reading this, that means you!
• reuse whatever bugfixes that were made since then - if they are even in the source now
• update the README.md file
• Implement a contributing guidelines and a proper ci/cd process so everyone keeps their sanity.
• Figure out distribution - admittedly going to pip was a good move. Encrypting the source files not so much.
• Other stuff... like the new features and bugfixes. 😃

[philip-ulrich]

FWIW, sorry this is so long.

TL;DR: Just wanted to make sure we knew the direction of this project from the get-go. Including the fact that this fork will always and forever be open source.

[arthurspa]

Hey @philip-ulrich , was thinking of doing the same. Since you've done already I will continue contributing here instead.
Count me in for co-owning it as well. If you're interested, it would be good to online meet and discuss more about the next steps.
Thanks for putting effort into it.

[philip-ulrich]

For sure. I don’t know if you saw the convo in discord, but he’s now saying “why can’t we be friends, why you gotta fork?” Which has a pretty obvious answer if you think about it. Given that we will likely be adding some of the same (and better stuff) than what he’s adding in the premium version.

He also mentioned that he’s willing to accept people into his dev team and split Patreon profits; but again - it’s not about the money. You don’t start open source projects expecting to rake in cash. I’m mean it’s not like he’s a bad guy, but I don’t think he understands why so many people are frustrated with his changes.

For the record, part of what I want to do with this is create an electron app that will let you easily manage bots, the console logs, and show you stats. Maybe while you aren’t actively botting likes, have the bot (optionally) run in the background and get some of the info needed for stats (like rate of return for follow backs). Stuff like that. For the RPi owners out there, we could have a headless version that uses the same HTML but the RPi hosts it for remote access.

Yeah, let’s def meet up. If you are on discord we can chat there or otherwise I’ll shoot you an email when I get off work. I’m the-philociraptor#1337 on discord.

[mastrolube]

Hello everyone! I was doing my version with some improvements then I saw that on discord. I can't be more agree with you! Consider that the hashtag function has been developed mostly by a user and the merge has been delayed because he wanted to make it paid! That was very sad..

About me:
I've developed some applications in autolisp for autocad and a lot of scripts in powershell.
I was pretty new to github but now I've studied a lot and have understand how it works (at least I hope!).
I am studying C# (novice) and python so I am very interesting in this project!

Ps. For insomiac I've found and fixed some bugs and in my version I've randomized the click (it was always in the middle), develop the interact to likers of a post (need some tune) and the function to turn off and on the screen when needed.

[philip-ulrich]

Rebased to v2.2.8 + a few random commits that happened prior to v3.0.0. - readded/updated MIT License.

Broke off the objective to move other code from PRs and bugfixes to another item. Reordered items in terms of priority.

@arthurspa @mastrolube For now, if it's a safe change (something already running in another future version) feel free to merge to master. If it's a new bugfix/feature, make a new branch and PR it. We need to get a stable version of this with new stuff (hashtags) rather quickly. We are not looking to change directory structure at this time.

[Tkd-Alex]

If need help, I'm here :)

[philip-ulrich]

The last thing in the todo list on this issue is distribution. After discussion this with folks at work, https://python-poetry.org/ seems like a viable solution. If we ever try to get this added to pip, poetry will still work. TL;DR: it manages a virtualenv for you and activates it with a simple command - which is pretty sexy. 😎

[arthurspa]

The last thing in the todo list on this issue is distribution. After discussion this with folks at work, https://python-poetry.org/ seems like a viable solution. If we ever try to get this added to pip, poetry will still work. TL;DR: it manages a virtualenv for you and activates it with a simple command - which is pretty sexy. 😎

I read a bit about it and it sounds a good solution for distribution.

[philip-ulrich]

Cool. We won't be changing anything this release - I don't think - but next release we can put in a PR for it.

[philip-ulrich]

Poetry sucks - just using pypi. Will add virtualenv instructions and maybe scripts.

[philip-ulrich]

Closing this since all the todos are done. Leaving pinned for now for context.