- Joined
- Nov 6, 2010
- Messages
- 1,560
- Reaction score
- 393
I thought I might post a community definition of "spoonfeeding" in the hopes of making an impact on the community's idea of what sharing is. I don't want to appear high-and-mighty/all-knowing at all, but I do want to standardize the phrase so that we can actually have a reference for when sharing is and is not to be expected. This definition is non-binding, and I don't want it to be thrown in people's faces if they don't want to comply. This is just my idea of how we should behave towards one another in this section in order to progress.
When you can be "selfish"
When it's your own work.
If you've worked hard on an emulator and/or CMS, I don't think anyone should be obligated to share the entire product if they worked hard on it. Why is this? You have a compelling interest in keeping it, they don't have one in having it.
Take Habboon, for example. Sledmore has worked on the emulator there and has brought it pretty much up to speed to Habbo. Certainly, the community would benefit from its release, but the fact that it's unique to a select few hotels (I think just Habboon) makes the emulator an essential feature to that hotel's individuality.
Furthermore, if I asked Habboon for its catalog then that, too, would be asking for spoonfeeding. It's very possible for me to make my own, and I can even replicate the catalog.
When are you being unnecessarily selfish?
When not sharing an essential feature.
Continuing my point about the compelling interest, essential features present such an interest. One essential feature would be the database not included in an emulator release..
*ahem*
Why is this a compelling interest? Building the database by browsing through the code, or adding columns and tables as errors appear is stupid work. You have to guess the type, the ideal length, and not every emulator is well-written enough to give you proper notice and information.
Furthermore, there's no reason to not share it! This isn't a unique feature to your hotel, and you don't stand to gain anything by keeping it to yourself if you've constructed one. In fact, even if someone did end up doing this stupidly-tedious work, the end result would be exactly the same as your finished product.
Really, the problematic aspect of this is in the fact that you just generally don't feel like sharing. You have a right to keep it to yourself, but your exercise thereof should be expected to get frowned upon (as it should be, if essential enough).
Please give me feedback and elaboration on this. Again, if you do happen to agree, don't go on a hunt to attack people for their actions. Ultimately, it's their work and their choice to do as they please with their work, but I'd encourage the entire community to be more open to sharing. Don't be a penis about your work!
When you can be "selfish"
When it's your own work.
If you've worked hard on an emulator and/or CMS, I don't think anyone should be obligated to share the entire product if they worked hard on it. Why is this? You have a compelling interest in keeping it, they don't have one in having it.
Take Habboon, for example. Sledmore has worked on the emulator there and has brought it pretty much up to speed to Habbo. Certainly, the community would benefit from its release, but the fact that it's unique to a select few hotels (I think just Habboon) makes the emulator an essential feature to that hotel's individuality.
Furthermore, if I asked Habboon for its catalog then that, too, would be asking for spoonfeeding. It's very possible for me to make my own, and I can even replicate the catalog.
When are you being unnecessarily selfish?
When not sharing an essential feature.
Continuing my point about the compelling interest, essential features present such an interest. One essential feature would be the database not included in an emulator release..
*ahem*
Why is this a compelling interest? Building the database by browsing through the code, or adding columns and tables as errors appear is stupid work. You have to guess the type, the ideal length, and not every emulator is well-written enough to give you proper notice and information.
Furthermore, there's no reason to not share it! This isn't a unique feature to your hotel, and you don't stand to gain anything by keeping it to yourself if you've constructed one. In fact, even if someone did end up doing this stupidly-tedious work, the end result would be exactly the same as your finished product.
Really, the problematic aspect of this is in the fact that you just generally don't feel like sharing. You have a right to keep it to yourself, but your exercise thereof should be expected to get frowned upon (as it should be, if essential enough).
Please give me feedback and elaboration on this. Again, if you do happen to agree, don't go on a hunt to attack people for their actions. Ultimately, it's their work and their choice to do as they please with their work, but I'd encourage the entire community to be more open to sharing. Don't be a penis about your work!
Last edited:
