g3rv4

8 ms·

61.
by g3rv4 8y ago
oh, yeah... that's something I want to look into
62.
by g3rv4 8y ago
We use bonfire, which is the same tool the community at Stack Overflow uses to interact.
63.
by g3rv4 8y ago
I don't know and I also don't want to figure it out :)
64.
by g3rv4 8y ago
Because... I have lots of things to work on, lots of things I want to build, lots of people I want to talk with. None of them involve talking with a lawyer in a different country over something that's really not that important in my li
65.
by g3rv4 8y ago
<3
66.
by g3rv4 8y ago
yup
67.
by g3rv4 8y ago
I guess... I'm sorry? and I'll try to do better next time, I promise.
68.
by g3rv4 8y ago
this was a bunch of Tampermonkey scripts... but I don't want to ignore their cease and desist. I... just don't do it. changing the name is not an issue... however, if I have to take it down, that's moot.
69.
by g3rv4 8y ago
they don't want people injecting javascript on their website. That's all there's to it. I'm not sending anything anywhere. I'm not storing anything. I'm not profiting from it.
70.
by g3rv4 8y ago
lol... it rings a bell
71.
by g3rv4 8y ago
There are two problems with this approach: 1. I don't want to get involved in that, even if I'm based in Uruguay and they'd have a hard time suing me. 2. What they could do is put resources to detect the extension and block i
72.
by g3rv4 8y ago
now that they got all that money, I wouldn't be surprised if they killed the web app and moved away from Electron to do native apps that are harder to be messed with.
73.
by g3rv4 8y ago
I wish it was so easy... I don't get to decide what tools my company uses unfortunately
74.
by g3rv4 8y ago
probably... I certainly didn't want to hide anything
75.
by g3rv4 8y ago
no, it can't be stopped technically. But I know I don't want to mess with them.
76.
Bye bye BetterSlack(g3rv4.com)
839 points by g3rv4 8y ago|383 comments
77.
by g3rv4 8y ago
yeah, I'll keep on using it myself (and I would have built it just for that). It's a shame they won't let me share it / take ideas / implement a way for US to control our experience.
78.
BetterSlack will be shutting down - thanks legal team!(twitter.com)
10 points by g3rv4 8y ago|2 comments
79.
by g3rv4 8y ago
yeah! if you have a library that does it, you could inspect when a message is created and call the library when the message is rendered. PRs are welcome :)
80.
by g3rv4 8y ago
somebody on Slack is already aware of the possibility: https://twitter.com/SlackHQ/status/1033279901888065536
81.
by g3rv4 8y ago
I guess that if they consider it a vulnerability, they're going to do the check on the server side... I really hope they don't though. If they do, I'll fix it on the extension (so only people with the extension would see the
82.
by g3rv4 8y ago
oh, an attacker could do [ https://nicely-looking-url.com](https://shady-site.com) . I see your point. however, anybody with a bit of javascript knowledge can do it. I guess we need to keep educating people about the imp
83.
by g3rv4 8y ago
oh, pop-out threads would be nice. I share your frustration :( and that's what compelled me to take a first stab at solving some issues.
84.
by g3rv4 8y ago
nice! yeah, the problem with dynamically loading the script is that an attacker could inject anything... and they could easily steal your slack token. But that sounds like an amazing thing for me to use locally :)
85.
by g3rv4 8y ago
I'd love to give zulip a try
86.
by g3rv4 8y ago
why use it at all? you may not be the one who chooses what tool your team uses for communication.
87.
by g3rv4 8y ago
what would you like it to happen? the extension may be able to filter the ones sent in the last N hours and adjust the number of unread... but that wouldn't solve the problem of missing things you should read.
88.
Show HN: BetterSlack – A Chrome extension to make Slack better(g3rv4.com)
80 points by g3rv4 8y ago|71 comments
89.
by g3rv4 8y ago
wow, this looks really really really good
90.
Show HN: A bot to see somebody else's timeline(voir.social)
2 points by g3rv4 10y ago|0 comments

More ›