What Should the *Win Channel Be Renamed?

posted by lucky760 1 decade 1 year 7 months 4 weeks ago • 977 views
  (4 votes)
  (26 votes)
  (1 vote)
show votes

A total of 31 votes have been cast on this poll.


As @ant pointed out, there's a conflict with the new(ish) *Win channel and the previously-existing *Wings channel.

Because the former is a sub-string of the latter, when the latter is invoked in a comment, the former is also detected. This is the expected behavior because we allow you to invoke using creative text around invocations.

The funny thing is the system is designed to prevent this by disallowing users to create a channel that is a sub-string of another and by ensuring an admin approves of the channel. In this case, @seltar initially created it with subdomain Wins, and I ignorantly "fixed" it by removing the s, thus creating the conflict.

In short, the channel's subdomain/invocation has to change. Vote above on the option you think would be the best alternative.

21 Comments

BoneRemake says...

* accomplish, acquire, annex, approach, attain, bag*, bring in, catch, collect, come away with, derive, earn, effect, gain, get, harvest, have, make, net, pick up, procure, rack up, reach, realize, receive, score, secure


** OHHHH SNAP !

at the time of posting I didnt realize it was such a narrow poll. My suggestions from the thesaurus are wasted. kinda did that one ass backwards eh.

lucky760 says...

By design, the software parses a comment for all recognized invocations, regardless of what text might follow.

This is how we support creativity in your invocations, for example, allowing for "What we have here is *failure to communicate," instead of requiring the exact "fail" keyword to standalone like, "What we have here is *fail ure to communicate."

This is why invoking *Wings triggers the *Win invocation and what I mean by saying it's a feature. What you're asking is that we either require that only the exact term is allowed as a valid invocation (which no one wants) or that I modify some of our core siftbot software to change the way it parses comments so it can look-ahead and compare every matched invocation and any or all the alpha-numerics that follow to see if there's possibly some other invocation that could also be matched and if so then ignore all shorter matched invocations.

I'm not going to expend the effort to completely rewrite that code into something much more complex and slower to execute just to support functionality that we never intended to allow in the first place.

probie says...

>> ^lucky760:

I'm not going to expend the effort to completely rewrite that code into something much more complex and slower to execute just to support functionality that we never intended to allow in the first place.



Amen to that. Now could you please go explain that to Microsoft, Apple, Google, and 99% of the other developers out there?

Send this Article to a Friend



Separate multiple emails with a comma (,); limit 5 recipients






Your email has been sent successfully!

Manage this Video in Your Playlists

Beggar's Canyon