this was my initial reaction. It feels like we would rather merge the Mythos/Glasswing fixes before the model becomes widespread. The rumours/vibe are that there are security issues at are going to need responsibly patching before the 0-day exploits arrive. If this means implementing a broader AI contribution policy now, it seems practical.
The article doesn't say if the confidentiality labels were created with encryption. I've been using the latter (with Preview DLP) to prevent emails leaking out to _external_ integrations, which can't access the keys. With MS internal tooling, it's feasible that it access to the key, in which case that would be even worse. Does anyone know if this happened?
uno.uk have a policy of not censoring things unless they absolutely have to. they're supporters of the Open Rights Group, and they're the only residential isp I've found that give me a /29 ipv4 block on the standard order form.
they're a small outfit, been with them for years and on first name terms with the main support guy. great for the kind of nerds who prefer you to skip the flow chart if you and then the logs from your router and hint that you know what you're doing.
Agreed. I read the article and I was thinking "this sounds pretty bad", but after clicking through to the main site my experience was "there's no explanation of what this is, but it looks like it probably falls within the need for some form of regulation".
Are there services which offer a less... risky... service that are similarly affected here?
Those can be "discontinuation effects" rather than lack of treatment. I'm not saying they aren't doing good for you, but it's important to bear in mind that acute symptoms from missing a dose can be a different thing.
Agreed. I've been frustrated by the proliferation in AI with technical support. Sometimes it's can't answer a question but thinks it can, so we go round and round in circles.
A couple have had a low threshold for "this didn't solve my answer" and directed me to a human, but others are impossible to escape.
On the other hand, I've had more success with a problem actually getting resolved by a chatbot without speaking to someone more recently... But not a lot more. Ususally I think that because I skew technical and treat Support as a last resort, I've tried everything it wants to suggest.
I didn't have a great experience. Perhaps load issues, or the HN hug of death?
I found that the AI kept cutting me off, and not leaving time in the conversation to respond. It would cut off utternances before the end and then answer the questions it had asked to me as if it had asked them. I think it could have gone on talking indefinitely.
Perhaps its audio was feeding back, but macs are pretty good with that. I'll try it with headphones next time.
Experienced engineering leader looking for a new role. I've managed ICs and managers, have a coaching and people-first attitude but have also built and shipped MVPs which have been picked up by bigger teams.
I've spent the last 5 years at Overleaf, a collaborative online LaTeX editor, and before that for 20 years at Widgit, who make products for people who have trouble reading.
Overleaf builds modern collaborative authoring tools for scientists — like Google Docs for Science. We have over 13 million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language. It’s used by around 500,000 people each day and hosts over 100 million projects.
We are currently looking for full-stack engineers to help improve our group-collaboration features and improve our rich-text editor to better support non-LaTeX users.
We are also looking for a Principal Site-Reliability Engineer to help us achieve faster delivrey by helping us with scaling, observability and continuous delivery.
Some reasons you'd enjoy working with us:
- Most of our code is open-source, and we're big fans of free software.
- We are based on the “Shape Up” development process, using an 8-week cycle to ensure regular delivery of improvements to the product.
- You’ll be working alongside a cross-functional team, including designers, product managers and developers, to help Overleaf become the go-to place for scientific writing.
- Working hours can be flexible to your needs. Our core hours are 2pm–5pm UK time. Applicants must be based in the UK, EU, US or Canada.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely and this is part of our values: https://www.overleaf.com/about/values. We get everyone together (usually in London) a few times a year for valuable face to face time.
Does anyone know if it's possible to split this model across multiple (identical, sli) GPUs, to run a version bigger than fits in the RAM of a single GPU?
Overleaf builds modern collaborative authoring tools for scientists — like Google Docs for Science. We have over 11 million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language. It’s used by around 400,000 people each day and hosts over 100 million projects.
We are looking for a Product Manager to lead our discovery and development initiatives related to our product expansion, and beyond (APIs, integrations, etc).
- We are based on the “Shape Up” development process, using a 10-week cycle to ensure regular delivery of improvements to the product.
- You’ll be working alongside a cross-functional team, including designers, product managers and developers, to help Overleaf become the go-to place for scientific writing.
- Working hours can be flexible to your needs. Our core hours are 2pm–5pm UK time. Applicants must be based in the UK, EU, US or Canada.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely and this is part of our values: https://www.overleaf.com/about/values. We get everyone together (usually in London) a few times a year for valuable face to face time.
Overleaf builds modern collaborative authoring tools for scientists — like Google Docs for Science. We have over 11 million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language. It’s used by around 400,000 people each day and hosts over 100 million projects.
We are currently looking for frontend, backend and full-stack engineers to help improve our group-collaboration features and improve our rich-text editor to better support non-LaTeX users.
Some reasons you'd enjoy working with us:
- Most of our code is open-source, and we're big fans of free software.
- We are based on the “Shape Up” development process, using a 10-week cycle to ensure regular delivery of improvements to the product.
- You’ll be working alongside a cross-functional team, including designers, product managers and developers, to help Overleaf become the go-to place for scientific writing.
- Working hours can be flexible to your needs. Our core hours are 2pm–5pm UK time. Applicants must be based in the UK, EU, US or Canada.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely and this is part of our values (https://www.overleaf.com/about/values). We get everyone together (usually in the UK) a few times a year for valuable face to face time.
I have a mac and a Linux box. I tend to always use the Linux box for dev these days because I can't get around the Docker-for-mac performance issues.
We run a stack with a bunch of microservices, and there is just no graceful way to develop it on the mac. Everything on Linux is an order of magnitude faster.
I still like the mac for some things, but I would only ever use it as a secondary box in its current state.
Overleaf builds modern collaborative authoring tools for scientists — like Google Docs for Science. We have over nine million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language. It's used by around 400,000 people each day.
We're currently hiring for two roles:
DevOps Engineer: We're looking for a devops engineer to help us run and maintain our microservice infrastructure, debug live problems, improve security and adopt new technologies and best practices. You will be working primarily with Google Kubernetes Engine and Terraform, although some knowledge of JavaScript and node.js will help.
Engineering Manager: We are looking to hire an enthusiastic Software Engineering Manager with strong engineering experience to join our team. You'll be coaching and supporting engineers and helping them with their career development, as well as having input into our high-level planning processes. Alongside that you'll be doing code review (in JavaScript) and acting as tech-lead on individual projects.
Some reasons you'd enjoy working with us:
- Most of our code is open-source and we're big fans of Free Software.
- We use the "Shape Up" development process, using a 10-week cycle to ensure regular delivery of improvements to the product.
- You'll be working alongside a cross-functional team, including designers, product managers and developers, to help our users create their best work on Overleaf.
- Working hours can be flexible to your needs. Our core hours are 2pm–5pm UK time. Applicants must be based in the UK, EU, US or Canada.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely and this is part of our values: https://www.overleaf.com/about/values. Pandemic permitting, we get everyone together in London a few times a year for valuable face to face time.
Overleaf (https://www.overleaf.com) | Full-time | REMOTE (UK/EU/US/Canada) | Software Engineering Team Lead
Overleaf builds modern collaborative authoring tools for scientists — like Google Docs for Science. We have over eight million registered users from around the world. Our primary product is an online, real-time collaborative editor for papers, theses, technical reports and other documents written in the LaTeX markup language. It’s used by around 400,000 people each day.
We are looking to hire an enthusiastic Software Engineering Team Lead to join our team. You’ll be motivating, coaching and supporting engineers and helping them with their career development, as well as having input into our high-level planning processes. Alongside that you’ll be doing code review (in JavaScript) and acting as tech-lead on individual projects.
Some reasons you'd enjoy working with us:
- Most of our code is open-source and we're big fans of Free Software.
- We use the “Shape Up” development process, using a 10-week cycle to ensure regular delivery of improvements to the product.
- You’ll be working alongside a cross-functional team, including designers, product managers and developers, to help our users create their best work on Overleaf.
- Working hours can be flexible to your needs. Our core hours are 2pm–5pm UK time. Applicants must be based in the UK, EU, US or Canada.
- Remote is a first class citizen; even before the pandemic, all founders and employees worked remotely and this is part of our values[1]. When we can, we get everyone together in London a few times a year for valuable face to face time.
I hope nobody uses this for anything serious. I run my own domain and use <category>-<service>@<mydomain> to have a unique email for everything I sign up to.
I have no email address that this counts as anything other than "risky".
If this opts me out of marketing mail then that's probably a good thing, but I hope nobody puts a password-reset or security/billing notifications behind it.