CSUA / csua-backend

A backend for the CSUA interblags.
MIT License
21 stars 20 forks source link

bunny1 for CSUA #22

Open robertquitt opened 6 years ago

robertquitt commented 6 years ago

bunny1 is a tool used internally at facebook, which basically defines powerful shortcuts in your browser search bar. I think CSUA could benefit from running its own.

This should be pretty simple to set up, and could be very powerful and useful.

www.bunny1.org

A simpler remake:

https://github.com/jackyang127/jack_bunny

Motivations:

http://www.ccheever.com/blog/?p=74

wylliec commented 6 years ago

I read through the entire blog post and I don't see how it would bring csua any value

tpankaj commented 6 years ago

I work at Facebook. bunny1 is pretty useful internally because it's a huge organization with a large number of pages internally, but I can't see how it would be useful for an organization as small as CSUA.

On Wed, Jun 13, 2018, 22:41 Caleb Wyllie notifications@github.com wrote:

I read through the entire blog post and I don't see how it would bring csua any value

β€” You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CSUA/csua-backend/issues/22#issuecomment-397177445, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzjndrosoP5WTAY_98mzTUFI0HrDw9cks5t8feUgaJpZM4UnSST .

robertquitt commented 6 years ago

There are a few features that I think would be useful to CSUA/Berkeley CS

Plus it's a neat little project, don't see why you gotta knock it😞

wylliec commented 6 years ago

If someone thinks this is an interesting project, then by all means they should try to set it up. But every project has a cost and I think that effort would be better spent on other interesting projects. Plus, even if someone set up a bunny server, it would require manual configuration of every potential client, which is enough to keep the vast majority of people from even trying it out.

toulouse commented 6 years ago

ancient former CSUA rootstaff here.

  1. Would make more sense if a bookmarklet were not trivial to set up. For full utility, sure, some manual configuration required. Also, last I checked, Firefox supports AddSearchProvider, but most people use Chrome so in that context it's a fair point that client setup is needed. If you create a landing page with guidance on setting it up, i.e. https://csua.berkeley.edu/bunny, and a list of useful commands, then it might be sticky enough to keep around.
  2. A docker image with bunny1 should be trivial to run as it is stateless and rather simple.
  3. It's arguably simpler than a dashboard of some sort, and the value is in quick mnemonics for common actions. If it doesn't provide value exceeding its overhead, then it should be shut down, but a minimum of value is virtually guaranteed and the overhead is likely to be near-zero.

In general, it's absolutely a good idea to manage allocation of effort, but going straight to an opportunity-cost judgment is often less valuable – to your career or to an organization – than "We gave it a shot, now let's shut this down and try something different" or "This was surprisingly useful and worth our time". It's frequently hard to tell how calibrated you are on opportunity cost.