(author here) I'm checking with my team to confirm these came from us, but if so I apologize for this - posts like these should come from a real account with proper disclosure, but also these sorts of requests feel premature for a project like ours that doesn't yet have a sizeable user base.
You are also characterizing another project that was open-sourced (sandstorm) and is under active development as "long abandoned". Open source is difficult and requires a fair amount of cheerleading to engage users and make them part of the community. As a result it's hard to see your project in a positive light.
"Long abandoned" is a fair characterization of Sandstorm.
There is a loyal community of enthusiasts trying to keep it alive, but realistically not a lot of progress has been made. (Though, AI has helped them make more progress lately.)
But the original creator of Sandstorm (me) did indeed abandon it long ago (sorry).
There is no need to apologize for building a fantastic tool that was ahead of its time.
But "abandoned" in this contexts makes it sound like it's dead. Even if it's factually correct that the original (very busy) author stepped away and it is literally/factually true that you "abandoned it", it is also fairly misleading.
I disfavor maligning open source projects based on a misleading framing.
No, sandstorm was deprecated years ago. I was building a platform that was similar to/inspired by sandstorm, and I closely followed it until its creator deprecated it. They now work for Cloudflare and released the 'WorkOS' project a couple weeks ago through them/for them.
Looking at the issues, do I understand it correctly that you have some way to install directly from repositories if they contain a `cloudinabottle.toml` file?
If yes, regardless of who made the issues, that seems like terrible architecture/design there...
I used to work for this company many years ago, and it's highly unlikely they're running a (centrally organized) spamming campaign of any type. Zack's a good guy and I'm sure he'll get it taken care of promptly.
Yes, but first of all, people make those decisions. And second, unlike those people, you don't need to have dissonant answers, and don't need to lie to yourself.
I don't think this approach is bad. The issues are asking if the project will accept contributions to add support, not demanding the maintainers add it.
Let's assume that they didn't have these container restrictions and could just use an ordinary docker-compose.yml, they'd still probably want to use something like OAuth2.0 for centralised login which a lot of these services won't have.
What would be better, making a massive PR to add support for it, or opening an issue to discuss it with the maintainer first?
It's 11 issues total and by one person, and the project says here in the thread the issue is being addressed. Please put down the metaphorical pitchforks and torches.
I checked, it's an Imbue employee (or someone impersonating one, which seems a bit far fetched). I could could cite my sources but it feels like doxxing / drawing too much attention to the mistake of an individual. My read is that it was a separate github account that they let an agent control.
The person doing this doesn't understand how pull requests work. The issues all say "I have a version in my fork". Open a pull request then! That's the whole point of forks on GitHub. Creating an issue first is pointless spamming akin to the classic "asking to ask". Just seems completely out of touch with open source to me.
It's not spam if it's the first time I heard of it and it's useful. It shows they care about their project. This makes me want to try it out even more.
Meta and Google can spam their unsolicited ads to a billion users but regular people aren't allowed to promote their own projects on niche forums? This is bs. You're the problem here. Self-promoting your harmful values. You're the spammer.
Spam is, rather definitionally, undesired marketing.
If they don't desire it, it's spam for them. And they rather clearly do not desire it.
(You could also go with the stronger "unrequested marketing" definition, which makes this even more "definitely spam". CAN-SPAM rules define it this way, so that seems fair too)
https://github.com/search?q=%22cloudinabottle.toml%22&type=i...