
IT Technical Innovator @SangerInstitute (words my own not official) Scientist, Software Dev, and PhD student of awkward cancer genome regions. M7POM/2#0THV
Cambridge, England
Joined June 2009
- Tweets8.6K
- Following426
- Followers497
- Likes7.5K
Martin Pollard retweeted
Postdoc position opening in my group! Research projects: pangenomes for diverse organisms, genome evolution, biocomputing, language models. Please reach out if interested!
Martin Pollard retweeted
Release 1.22 of HTSlib, SAMtools, and BCFtools is now available from GitHub. See htslib.org/download/ for links to tarballs and release notes.
Martin Pollard retweeted
BWA-0.7.19 released with a fix to the internal HD-line bug introduced in 0.7.18
Martin Pollard retweeted
Engineers-turned-PMs keep making the same fatal mistake in stakeholder meetings:
They think logic will save them.
After mentoring a few folks, I've noticed a pattern no one talks about:
Martin Pollard retweeted
“My wife complains that open office will never print on Tuesdays”
A bizarre sentence; which kicked off one of the most interesting bug hunts in Ubuntu’s history.
It all starts with some goofy pattern matching.
Martin Pollard retweeted
uhh, anaconda just sent a message to our HPC admins that we're in violation their ToS and we now need to pay for a license or remove all their software from our system?
Martin Pollard retweeted
Hi @networkrail @NetworkRailEC
Yesterday evening your Leeds Station @ChangingPlaceUK was double-locked with a non-RADAR key.
No information was provided as to how to gain access.
No "out of order" sign either.
Just locked.
Why? – at Wetherby, England
Martin Pollard retweeted
So Oxford Nanopore is now available for acquisition? Nobody going to buy it?
Martin Pollard retweeted
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated.
This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses.
The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines".
The 2024 version is 800-63-4.
Here: pages.nist.gov/800-63-4/
The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org.
The previous update was in2020.
The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead:
1. After a breach/compromise
2. User request
2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords.
This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this.
Most frameworks, however, have moved away from arbitrary password resets and complexity rules.
**We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them.
Using complexity rules gets you the user psychology of:
Password1
Password2
and so on
Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies.
I'm so excited for the new changes!
Ok I'm off my soapbox.
Share the love! Thank you!
Martin Pollard retweeted
I have to tell a client that the ship carrying her countertops is being held up by pirates and it is too early for this right now
Martin Pollard retweeted
Replying to @pronounced_kyle
All laws which cannot be engraved on a basalt stele ought to be declared illegitimate
Martin Pollard retweeted
Release 1.19.1 of HTSlib, and SAMtools is now available from GitHub. This fixes a regression in 1.19 that caused written CRAM files to be much bigger than necessary, along with other bugs. See htslib.org/download/ for links to tarballs and release notes.
Martin Pollard retweeted
The #gnomAD team is proud to announce the release of gnomAD v4! The v4 dataset includes 730,947 exomes & 76,215 genomes, which is ~5x larger than the v2 & v3 releases combined, & includes nearly 120K indivs of non-European genetic ancestry broad.io/gnomad_v4 #ASHG23 (1/11)
Martin Pollard retweeted
Anti-COVID drug Molnupiravir accelerates viral evolution go.nature.com/3SfGJwp
Martin Pollard retweeted
one of these is the leaked official, original source code of Pokemon Emerald and one of these is a decompile made by hobbyists trying to reverse engineer what the game is doing
and you know I wouldn't be posting this if they were not, apparently, switched at birth.
Martin Pollard retweeted
Is Britain getting a bad deal? @Ben_A_Hopkinson and I looked at 242 infrastructure projects across 14 different countries.
Our conclusion? It costs more to build new tram systems, railways, and roads in Britain than almost anywhere else in the world. 🧵
samdumitriu.com/p/britains-i…
Martin Pollard retweeted
Getting rid of homopolymers basecalling errors by combining duplex reads with synthetically incorporated nucleotide analogs #NanoporeConf
Martin Pollard retweeted
Register your interest to join the early access programme for High Duplex flow cells: register.nanoporetech.com/hi…
ONT new duplex cells 85% duplex reads @ approx Q32. Pretty much read length independent. This is a game changer and lights a fire under other sequencing companies. #nanoporeconf #lc23
Martin Pollard retweeted
Superheavy’s grid fins are a key part of the vehicle’s recovery hardware, but the perpetually extended state looks quite different compared to Falcon 9. Let’s take a look at how these grid fins work and why they can stay extended at all times. (1/10)
📸 @RGVaerialphotos



























