search

fullphat / snarl

When { stuff_happens(); tell_me() }
http://snarl.fullphat.net
57 stars 2 forks source link

> This conversation has been locked and limited to collaborators #83

Closed kekukui closed 4 years ago

kekukui commented 4 years ago

"This conversation has been locked and limited to collaborators." https://github.com/fullphat/snarl/issues/82

If providing useful information constitutes "collaboration", then locking the conversation prevents me from becoming a collaborator.

# circular reasoning, see "Catch 22"
# equivalent of "10 goto 10"

So now because the topic is locked, I have to create a new issue here, instead of responding to the topic directly:

"I've had to cut back on spending (Snarl generates me no income) so domain names were the first to go."

But you already have a working domain name, fullphat.net. So even if you dont want to host the Snarl pages on that server, there is still no need for the broken link on this page, when Github has free web hosting: http://fullphat.net/snarl5/

So just use something like: fullphat.github.io instead of getsnarl.info

https://pages.github.com/ https://gist.github.com/deanrather/6d63e9dcdf823957b171

fullphat commented 4 years ago

Thanks for the mansplanation! 😂

It's a shame you took the effort to post a new issue, but omitted to chuck some coin my way, which is what the subtle hint in the post was about. ☺️

And "Catch 22" means "damned if you do or if you don't" while "10 GOTO 10" is just an infinite loop, so yeah: totally different.

kekukui commented 4 years ago

Well I'm glad I could entertain you. But I am not in a position to contribute money to every project that I would like to support, so where time and ability permits I contribute to projects by testing, trapping bugs, writing documentation, user interface design, publicity, paralegal work, end user support, et cetera. If I was actually using Snarl in a commercial application, I would pay for it.

I just thought that issue should not have been closed because we need a place to discuss things related to the application which are not technically bug reports, since you do not have a forum. For example, I was under the impression that Snarl used the same API as Growl, but this does not appear to be the case. So it's really a question about the design (not a bug report or feature request) and that's why I did not want to open a new issue.

I would suggest you address this in the FAQ -- but if it's already mentioned and I somehow overlooked it, I guess I have just been working too hard. I honestly did not need any of the extra features which you have added, so if Snarl is not a 100% compatible drop-in replacement for Growl, I will just use Growl. I really like the photography and paintings on your web site, but Github is probably not the best place to discuss the visual arts. 👽

fullphat commented 4 years ago

@kekukui this thread is now closed. Your reply seems to cover a number of issues (FAQ, API, drop-in replacement for Growl) - please raise separate tickets here for each of them so we can respond accordingly.

kekukui commented 4 years ago

Okay, no problem... whatever you prefer. If you don't understand my reasoning, I just want to say that I have contributed to other projects where the administrators will reprimand people for opening issues and making posts that are not bug reports or feature requests. So I am not trying to annoy you, I am just pointing out that the things which you are asking me to do are precisely the things which I have seen other project administrators on GitHub get angry about.