4 ms·
These guys have been spamming issues in repos trying to promote this project and no disclosure whatsoever that they are associated with the project. https://gi
by KomoD 2mo ago
These guys have been spamming issues in repos trying to promote this project and no disclosure whatsoever that they are associated with the project.
https://github.com/search?q=%22cloudinabottle.toml%22&type=issues https://github.com/search?q=%22cloudinabottle.toml%22&type=i...
- edoceo 2mo agoIt's only 11 in the last 48h, on lesser known projects.
- satvikpendem 2mo ago11 in 48 hours is way too many and I'd call that spam.
- asdf88990 2mo agoDisclosure would be nice but 11-12 issues in entire GitHub is hardly spam.
- ball_of_lint 2mo agoLooks like the account in question is deleted now - do you have the original username?
- KomoD 2mo agoadl-collab
- zplizzi 2mo ago(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.
- KomoD 2mo agoThe user was called adl-collab, when it forked repos to add implementations it made them under a branch called "andrew". The biggest contributor to the project in the last 3mo is andrewlaack... and we can also just take a guess that "adl" in adl-collab is AnDrewLaak.
- zplizzi 2mo agoYeah, I'll make sure this doesn't continue. To be clear there were 11 total issues posted; this was a mistake, not some huge spamming campaign.
- ChrisKnott 2mo agoPossibly andrewlaack’s clanker run amok
- nicerice 2mo agoshouldn't we hold back with allegations while there's a non-0 chance this is just a user wishing their other services were supported too?
- Retr0id 2mo agoI 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.
- rtpg 2mo agoproject literally launched yesterday... come on
- deleted 2mo ago[deleted]
- pkulak 2mo agoHardly seems worth the pitchforks.
- deleted 2mo ago[deleted]
- jongjong 2mo agoIt'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.
- Groxx 2mo agoSpam 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)
- globular-toast 2mo agoThe 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.
- hamandcheese 2mo ago> Creating an issue first is pointless spamming akin to the classic "asking to ask" Many projects disagree with you on this one. It is quite common to have a policy that forbids PRs without an issue or discussion first.
- Sophira 2mo agoI've never actually seen this. Can you link an example?
- InsideOutSanta 2mo agoSome projects require opening an issue first.
- mrkeen 2mo agoIt's evidence of bad abstraction if you need everyone else to make changes and couple themselves directly to you. If for some reason your services can't speak an already common language, I think it's on you to add those shims into your own project.
- fy20 2mo agoI 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?
- crabmusket 2mo agoCo-op Cloud, which has similarities, creates separate repos for its "packaging recipes". https://docs.coopcloud.tech/maintainers/catalogue/ https://docs.coopcloud.tech/maintainers/catalogue/
- ErroneousBosh 2mo agoTell you what though, thank you for providing such a comprehensive list of cool projects to nerdsnipe me on a sunday morning!
- walrus01 2mo agoIt'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.
- grosswait 2mo agoOn the plus side, I learned about some interesting projects from that GitHub query.
- GrowUpHN 2mo ago[flagged]
- alexflint 2mo agoThis github search returns just 11 results, and the issues are more or less reasonable. Doesn't seem that egregious.