These are chat archives for dcsan/gitterbot

1st
Aug 2015
dc
@dcsan
Aug 01 2015 08:01
@abhisekp we should discuss the bot here
as it has the github issues update at the right
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:05
@dscan Please comment the source code files with the hints at the top specifying the purpose of the codes in that particular file. That'll help both you and any collaborators to get started easily.
dc
@dcsan
Aug 01 2015 08:05
sure.
I'll write up a readme with what are the general things
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:06
@dcsan does the bot recognizes edits? E.g. if someone types help and then edits and prepends it with @camperbot.
dc
@dcsan
Aug 01 2015 08:06
no. thats a gitter api limit
maybe they send a "patched" event, id have to check
well, they do send it, but i'm ignoring it.
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:08
may be you add it later. :)
dc
@dcsan
Aug 01 2015 08:08
yeah
i think its lower priority
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:31
Please add a .gitingnore and remove the .idea directory from git repo.
dc
@dcsan
Aug 01 2015 08:31
i did that
git pull
so the thing with different environments is kind of complicated
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:32
it's still in the repo
dc
@dcsan
Aug 01 2015 08:32
rly/
done
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:47
help
This message was deleted
Abhisek Pattnaik
@abhisekp
Aug 01 2015 08:54
Does the bot use fuzzy search on find and wiki commands? Doesn't seem so. It should.
bot must delete it's command result messages after 5 mins to reduce the clutter.
dc
@dcsan
Aug 01 2015 09:02
it shoudl yeah, there is a ticket for that
dcsan/gitterbot#7
actually full text but didn't write up fuzzy search yet
ok i'm off to sleep
let me know any problems you have
Abhisek Pattnaik
@abhisekp
Aug 01 2015 09:06
@dcsan and what about deletion of the message?
dc
@dcsan
Aug 01 2015 09:06
not sure how we woudl do that
you mean delete from gitter?
dont think you can
Abhisek Pattnaik
@abhisekp
Aug 01 2015 09:06
This message was deleted
dc
@dcsan
Aug 01 2015 09:06
so maybe much of that would be better in smaller chats
yeah, its not so great looking
you can push "" emptry string
and it will delete
but i think there's a time limit and it still leaves an ugly space
Abhisek Pattnaik
@abhisekp
Aug 01 2015 09:07
it would reduce the clutter created by the chatbot
dc
@dcsan
Aug 01 2015 09:07
yeah for busy chats i agree
its gonna be too much as is
but for 1:1 about a bonfire it shoudl be ok
lets see how it goes!
Abhisek Pattnaik
@abhisekp
Aug 01 2015 09:08
may be for later.
add it in issue.
dc
@dcsan
Aug 01 2015 09:09
btw if you add wiki pages they dont show up in realtime
Abhisek Pattnaik
@abhisekp
Aug 01 2015 09:10
how often the bot scans the wiki to add it in wiki list?
dc
@dcsan
Aug 01 2015 09:12
only when i run it atm
theres a ticket to automate or cron that...
theres a shellscript
bin/wiki-update.sh
need to cron or something
OR add a git commit hook on github itself
to call the app each time there's an edit
Abhisek Pattnaik
@abhisekp
Aug 01 2015 11:45
dc
@dcsan
Aug 01 2015 19:39
help
update
Berkeley Martinez
@BerkeleyTrue
Aug 01 2015 19:43
@abhisekp nice work!
dc
@dcsan
Aug 01 2015 19:46
update
CamperBot
@camperbot
Aug 01 2015 19:46
updating wiki...
done
dc
@dcsan
Aug 01 2015 19:47
@abhisekp I added a command to update the wiki from the cmd line now
Berkeley Martinez
@BerkeleyTrue
Aug 01 2015 19:48
You should make those commands only commandable by certain people. Like maybe the core team
To prevent abuse
dc
@dcsan
Aug 01 2015 19:48
yes..
well, i was going to have a cron to pull the wiki every minute or so
if the wiki gets defaced, we'll just have to revert it
update just reflects the wiki on chat
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:18
@dcsan, @BerkeleyTrue is right. You shouldn't give out the permission to update to everyone or add the gollum event listener and update the wiki cache for old wiki updaters, but not for new users. For new users, the update cmd must be run by a core user.
dc
@dcsan
Aug 01 2015 20:19
the update /edit on the wiki itself is already open
people need a github account but anyone can edit
that's how the wiki is setup...
someone could deface it but theyd need to get a github account to do it, and then we just revert.
help css
CamperBot
@camperbot
Aug 01 2015 20:19

:pencil: css

Cascading Style Sheets [(CSS)] (https://developer.mozilla.org/en-US/docs/Web/CSS) is a style sheet language used for describing the look and formatting of a document written in a markup language.

tags: css, stylesheets

:pencil: read more about css on the FCC Wiki

every edit is in the history
and easy to diff
so not sure why we would just hold back the chatroom content
update
CamperBot
@camperbot
Aug 01 2015 20:20
updating wiki...
data: Updating ea4d1c8..709a29d
Fast-forward
data: camperbot.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
done code: 0
dc
@dcsan
Aug 01 2015 20:21
its mostly just for people editing who don't want to wait on the cron task update
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:21
@dcsan yeah! But the wiki cache of the bot should only update by verified users who are either core member of FCC or have previous verified updates.
dc
@dcsan
Aug 01 2015 20:21
lets see if its actually a problem first
if it is, we'll have to fix it upstream on the wiki
ie put a system in place for pull requests there
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:22
there are rogue updates like i did to the regex wiki that shouldn't show up in chat
dc
@dcsan
Aug 01 2015 20:22
it will seriously reduce the instant feedback and fun of adding to the wiki tho
it maybe that in the main chat, we'll only allow a subset of "whitelisted" items or something
not sure. i'd rather work on features we need now and know this maybe a problem in future
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:23
yep!
dc
@dcsan
Aug 01 2015 20:23
than spend time on it
eventually when FCC is big enough, there will be trolls that show up
but hopefully we'll have enough non-trolls to revert crappy changes by then
for example a system where when an edit is made, a brief DIFF of changes gets sent to one "wiki maintainers" room
and people can revert if it looks like spam
id prefer default to be let it through, and fix it later,
than make everything take time to get through
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:25
yeah! that would be one strategy. :)
dc
@dcsan
Aug 01 2015 20:26
hey, you're the one who asked for the update command :thought_balloon:
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:28
@dcsan but I hadn't thought of it's repercussions till @BerkeleyTrue mentioned it and I experienced it while I updated the regex wiki with the broken links. :(
dc
@dcsan
Aug 01 2015 20:28
yeah but this way you can fix and see your changes right away

OODA ooda

explain ooda
CamperBot
@camperbot
Aug 01 2015 20:29
no wiki entry for: ooda
why not :pencil: create one?
you could also try typing find ooda
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:29
everything has it's divine and evil sides.
dc
@dcsan
Aug 01 2015 20:30
update
CamperBot
@camperbot
Aug 01 2015 20:30
updating wiki...
data: camperbot.md | 12 +++++-------
ooda.md | 3 +++
2 files changed, 8 insertions(+), 7 deletions(-)
create mode 100644 ooda.md
done code: 0
data: Updating 709a29d..2156428
Fast-forward
dc
@dcsan
Aug 01 2015 20:30
explain ooda
CamperBot
@camperbot
Aug 01 2015 20:30

:pencil: ooda

The OODA Loop is about how fast you can iterate. Often called out in Lean Startup circles.

OODA
:pencil: read more about ooda on the FCC Wiki

Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:30
nice
dc
@dcsan
Aug 01 2015 20:30
boom goes the dynamite :bomb:
Abhisek Pattnaik
@abhisekp
Aug 01 2015 20:30
:fire:
Berkeley Martinez
@BerkeleyTrue
Aug 01 2015 20:30
Maybe just add some sort of rate limiting.
dc
@dcsan
Aug 01 2015 20:31
for edits per user?
or the update cmd itself?
maybe yeah, as it uses some resources
Berkeley Martinez
@BerkeleyTrue
Aug 01 2015 21:12
update command
Abhisek Pattnaik
@abhisekp
Aug 01 2015 21:19
you mean to update the update command? :P
dc
@dcsan
Aug 01 2015 21:20
update sdasdf
doesnt work
update wiki
CamperBot
@camperbot
Aug 01 2015 21:20
updating wiki...
data: Updating 392dae4..43e52b4
Fast-forward
done code: 0
dc
@dcsan
Aug 01 2015 21:20
does
CamperBot
@camperbot
Aug 01 2015 23:52

welcome @dcsan