Contact us to opt out. If you want to exclude your Customer Data from Slack global models, you can opt out. To opt out, please have your Org or Workspace Owners or Primary Owner contact our Customer Experience team at feedback@slack.com with your Workspace/Org URL and the subject line “Slack Global model opt-out request.” We will process your request and respond once the opt out has been completed.
That includes a period before inside the quotes which would suggest a period inside the subject line.
There's some shenanigans going on here, of course. The section I was looking at says...
To opt out, please have your org, workspace owners or primary owner contact our Customer Experience team at feedback@slack.com with your workspace/org URL and the subject line ‘Slack global model opt-out request’.
I don't think this is shenanigans, just inconsistent use of English rules. I'd be floored if a judge ruled the period was pertinent here; there's no linguistic value or meaning to it (i.e. the meaning of the message is the same with or without it).
I'd be very surprised to hear that Slack was allowed to propose a free-form communication method, impose rigid rules on it, and then deny anyone who fails to meet those rigid rules. If Slack was worried about having to read all of these emails, they should have made a PDF form or just put it on a toggle in the Workspace settings. This is a self-inflicted problem.
For reference, I got an email back saying I was opted out and a bunch of justifications about why it's okay what they did and zero mention of the legality of opting people in by default.
To xena's point, we're not currently enforcing the limits :) We've been very cautious about that since, as I mentioned in a comment elsewhere, the limits have always been an experiment.
We're definitely considering it. We introduced the limits a while back as an experiment. In most cases, I believe the current limits don't make a lot of sense. Fundamentally, we were hoping to encourage the deployment of Tailscale to end devices (partially to increase users' security, partially to get a better idea of how widely Tailscale is actually being used). Unfortunately, the limits introduce the kinds of headaches that you're describing (and for IoT it can be a showstopper). The net effect across all users could be to actually discourage people from having fun and tinkering with Tailscale, which is the last thing we want.
Would you mind describing some of the other use cases you have for subnet routers? Do you have other mini k8s clusters you want to use them for? Other things? I'd love to learn more.
> Fundamentally, we were hoping to encourage the deployment of Tailscale to end devices (partially to increase users' security, partially to get a better idea of how widely Tailscale is actually being used).
that makes sense, I also got the feeling that's the recommended way to run tailscale, and it's nice to be able to address services directly by their dns name
> Would you mind describing some of the other use cases you have for subnet routers? Do you have other mini k8s clusters you want to use them for? Other things? I'd love to learn more.
Yes that's mainly it. I am probably an edge case because I have mini k8s clusters for different things. I have 2 main networks: My network at home, then my main k8s for my personal cloud stuff, those 2 are pretty constant (but want to spin up a separate IoT network soon that may or may not need a router). Then depending on what I work on, I might spin up other k8s clusters
(I'm one of those odballs that really enjoys working with k8s for personal stuff)
I think for me it's mainly to have piece of mind to not run into limitations later on, after I'm already locked in and need to rip-out tailscale to replace with ZeroTier
I think most people who are using the limit of the free account should really be paying. I am extremely happy paying for Tailscale, pandering to freeloaders is nice and fun but I really don't think it hurts anyone to charge for what the service is worth.
It’s a deep hole for a company to dig itself out of, not to mention changing the habits of people to explicitly document things elsewhere.
It would be neat if Slack reported stats on searches so that, for example, a company could better understand what key conversations should be moved into proper documents…but this is likely against Slack’s interests.
I wouldn't say mistimed so much as "we were excited to get the post up". Node sharing is indeed in invite-only beta, though we're planning on opening that up very soon. Apologies for any frustration/confusion.
I was on the "silicon level debugging" team, which took test cases like this and boiled them down to x86, then through the CMS to p95 assembler, then down to the circuit and device level to figure out the speed paths. There were definitely some crazy issues we found. Honestly, I couldn't have done that job without relying on 80%+ of my undergrad courses (Computer Engineering @ Waterloo).
The issue I remember the most clearly was one that an engineer Simon Barrett discovered: a specific sequence of MMX instructions would cross-talk (and cause the occasional bit to flip) on two perpendicular busses in the pipeline when run at a specific voltage/frequency. It sounds simple enough, but imagine trying to figure that one out.
I worked at Transmeta for a short time (about a year) after my undergrad. I loved it. However, there was always a running joke that the stock ticker symbol should have been “HYPE”. It was sad to see things implode the way they did.
(Co-founder here). It's coming, I promise. I'm as excited as you are. We wanted to iron out the kinks on mobile (i.e. iOS) before duplicating them on another platform. Thankfully, we're past that point now.
(Co-founder here). If you're referring to the free tier, it only supports a single email address at the moment. What some people have been doing is to create a fake Gmail address and sharing that with their family/friends to use as a common login.
We've been exploring the idea for a free (or significantly discounted) "family" plan (or even something like that for small teams). Please stay tuned over the coming weeks for some updates to our pricing and tiers.
(Tailscale co-founder here). I certainly appreciate the feedback and suggestions. We've had pricing inquiries from individuals all the way to enterprise. Finding the right set of features at the right price is something we're going to spend a lot of time exploring (for instance, some larger companies don't care too much about ACLs, but some smaller ones really, really do). Right now, all I can say for certain is that our pricing page will change and that we're open to discussion.
I'd love to hear more of your thoughts on where you think we can add value and what it might be worth to you. If you're up for it, please email me at dfcarney@tailscale.com Regardless, thanks again for the input.
Subject: Slack Global Model opt-out request.
Body:
<my workspace>.slack.com
Please opt the above Slack Workspace out of training of Slack Global Models.