home.social

#writethedocs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #writethedocs, aggregated by home.social.

fetched live
  1. about.readthedocs.com/blog/202

    'In mid-to-late June 2026, Read the Docs experienced the largest and most sophisticated distributed denial-of-service (DDoS) attack in our history. At its peak, our infrastructure was hit with over 5.5 million requests per minute, about 100 times our normal baseline traffic.'

    Nearly 120 terabyte of data was transferred.

    I really wonder *why* someone would attack Read the Docs, especially when all of their docs are made available for AI scrapers.

    about.readthedocs.com/blog/202

    Paranoid theory: AI companies attack what works (technical writing) so that AI can take over. ;-)

    Seriously though, the recent attack seems to me to be sophisticated and meant to bring financial chaos to Write the Docs.

    #TechnicalWriting #WriteTheDocs #DDoS

  2. about.readthedocs.com/blog/202

    'In mid-to-late June 2026, Read the Docs experienced the largest and most sophisticated distributed denial-of-service (DDoS) attack in our history. At its peak, our infrastructure was hit with over 5.5 million requests per minute, about 100 times our normal baseline traffic.'

    Nearly 120 terabyte of data was transferred.

    I really wonder *why* someone would attack Read the Docs, especially when all of their docs are made available for AI scrapers.

    about.readthedocs.com/blog/202

    Paranoid theory: AI companies attack what works (technical writing) so that AI can take over. ;-)

    Seriously though, the recent attack seems to me to be sophisticated and meant to bring financial chaos to Write the Docs.

    #TechnicalWriting #WriteTheDocs #DDoS

  3. about.readthedocs.com/blog/202

    'In mid-to-late June 2026, Read the Docs experienced the largest and most sophisticated distributed denial-of-service (DDoS) attack in our history. At its peak, our infrastructure was hit with over 5.5 million requests per minute, about 100 times our normal baseline traffic.'

    Nearly 120 terabyte of data was transferred.

    I really wonder *why* someone would attack Read the Docs, especially when all of their docs are made available for AI scrapers.

    about.readthedocs.com/blog/202

    Paranoid theory: AI companies attack what works (technical writing) so that AI can take over. ;-)

    Seriously though, the recent attack seems to me to be sophisticated and meant to bring financial chaos to Write the Docs.

    #TechnicalWriting #WriteTheDocs #DDoS

  4. about.readthedocs.com/blog/202

    'In mid-to-late June 2026, Read the Docs experienced the largest and most sophisticated distributed denial-of-service (DDoS) attack in our history. At its peak, our infrastructure was hit with over 5.5 million requests per minute, about 100 times our normal baseline traffic.'

    Nearly 120 terabyte of data was transferred.

    I really wonder *why* someone would attack Read the Docs, especially when all of their docs are made available for AI scrapers.

    about.readthedocs.com/blog/202

    Paranoid theory: AI companies attack what works (technical writing) so that AI can take over. ;-)

    Seriously though, the recent attack seems to me to be sophisticated and meant to bring financial chaos to Write the Docs.

    #TechnicalWriting #WriteTheDocs #DDoS

  5. about.readthedocs.com/blog/202

    'In mid-to-late June 2026, Read the Docs experienced the largest and most sophisticated distributed denial-of-service (DDoS) attack in our history. At its peak, our infrastructure was hit with over 5.5 million requests per minute, about 100 times our normal baseline traffic.'

    Nearly 120 terabyte of data was transferred.

    I really wonder *why* someone would attack Read the Docs, especially when all of their docs are made available for AI scrapers.

    about.readthedocs.com/blog/202

    Paranoid theory: AI companies attack what works (technical writing) so that AI can take over. ;-)

    Seriously though, the recent attack seems to me to be sophisticated and meant to bring financial chaos to Write the Docs.

    #TechnicalWriting #WriteTheDocs #DDoS

  6. Farewell Write the Docs Berlin 2026. It was a pleasure, as always.

    I hosted my first unconference session today on how to enable docs for better usage by AI without increasing the maintenance burden. Thanks for all the contributions. You were very encouraging.

    Thanks to organization team, the speakers, volunteers, and you the attendees.

    #writethedocs #writethedocsberlin2026

  7. Farewell Write the Docs Berlin 2026. It was a pleasure, as always.

    I hosted my first unconference session today on how to enable docs for better usage by AI without increasing the maintenance burden. Thanks for all the contributions. You were very encouraging.

    Thanks to organization team, the speakers, volunteers, and you the attendees.

    #writethedocs #writethedocsberlin2026

  8. Farewell Write the Docs Berlin 2026. It was a pleasure, as always.

    I hosted my first unconference session today on how to enable docs for better usage by AI without increasing the maintenance burden. Thanks for all the contributions. You were very encouraging.

    Thanks to organization team, the speakers, volunteers, and you the attendees.

    #writethedocs #writethedocsberlin2026

  9. Farewell Write the Docs Berlin 2026. It was a pleasure, as always.

    I hosted my first unconference session today on how to enable docs for better usage by AI without increasing the maintenance burden. Thanks for all the contributions. You were very encouraging.

    Thanks to organization team, the speakers, volunteers, and you the attendees.

    #writethedocs #writethedocsberlin2026

  10. Second day of Write the Docs Berlin 2026 is ongoing. It continues yesterday's spirit of feeling welcomed, engaged, full of learning, and sharing challenges and experiences.

    So far I liked most the talk "Good Enough at Scale: Documentation Infrastructure Under Capacity Constraints" from Elena Baskakova. It was very informative with a lot of knowledge. Thank you so much.
    writethedocs.org/conf/berlin/2

    #writethedocs #writethedocsberlin2026 #technicalwriting

  11. Second day of Write the Docs Berlin 2026 is ongoing. It continues yesterday's spirit of feeling welcomed, engaged, full of learning, and sharing challenges and experiences.

    So far I liked most the talk "Good Enough at Scale: Documentation Infrastructure Under Capacity Constraints" from Elena Baskakova. It was very informative with a lot of knowledge. Thank you so much.
    writethedocs.org/conf/berlin/2

    #writethedocs #writethedocsberlin2026 #technicalwriting

  12. Second day of Write the Docs Berlin 2026 is ongoing. It continues yesterday's spirit of feeling welcomed, engaged, full of learning, and sharing challenges and experiences.

    So far I liked most the talk "Good Enough at Scale: Documentation Infrastructure Under Capacity Constraints" from Elena Baskakova. It was very informative with a lot of knowledge. Thank you so much.
    writethedocs.org/conf/berlin/2

    #writethedocs #writethedocsberlin2026 #technicalwriting

  13. Second day of Write the Docs Berlin 2026 is ongoing. It continues yesterday's spirit of feeling welcomed, engaged, full of learning, and sharing challenges and experiences.

    So far I liked most the talk "Good Enough at Scale: Documentation Infrastructure Under Capacity Constraints" from Elena Baskakova. It was very informative with a lot of knowledge. Thank you so much.
    writethedocs.org/conf/berlin/2

    #writethedocs #writethedocsberlin2026 #technicalwriting

  14. First day at Write the Docs 2026 Berlin was amazing. I enjoyed the unconference with its huge topic variety. Of course, AI was one topic and it's so different how teams or even organizations position themselves when it comes to documentation. I liked the open and honest exchange about concerns, challenges and ideas.

    Next up, the evening social event.

    #writethedocs #writethedocsberlin #writethedocsberlin2026 #technicalwriting

  15. First day at Write the Docs 2026 Berlin was amazing. I enjoyed the unconference with its huge topic variety. Of course, AI was one topic and it's so different how teams or even organizations position themselves when it comes to documentation. I liked the open and honest exchange about concerns, challenges and ideas.

    Next up, the evening social event.

    #writethedocs #writethedocsberlin #writethedocsberlin2026 #technicalwriting

  16. First day at Write the Docs 2026 Berlin was amazing. I enjoyed the unconference with its huge topic variety. Of course, AI was one topic and it's so different how teams or even organizations position themselves when it comes to documentation. I liked the open and honest exchange about concerns, challenges and ideas.

    Next up, the evening social event.

    #writethedocs #writethedocsberlin #writethedocsberlin2026 #technicalwriting

  17. I'm on my way to Write the Docs Berlin 2026 and looking forward to inspiring talks, an engaging unconference, and meeting a lot of interesting people around technical writing. See you tomorrow.

    #writethedocsberlin #writethedocs #technicalwriting

  18. I'm on my way to Write the Docs Berlin 2026 and looking forward to inspiring talks, an engaging unconference, and meeting a lot of interesting people around technical writing. See you tomorrow.

    #writethedocsberlin #writethedocs #technicalwriting

  19. I'm on my way to Write the Docs Berlin 2026 and looking forward to inspiring talks, an engaging unconference, and meeting a lot of interesting people around technical writing. See you tomorrow.

    #writethedocsberlin #writethedocs #technicalwriting

  20. going to my first #writethedocs conf tomorrow in Berlin, and have larned of the lovely Pac-Man rule. This should be standard at every social work event! ericholscher.com/blog/2017/aug

  21. going to my first #writethedocs conf tomorrow in Berlin, and have larned of the lovely Pac-Man rule. This should be standard at every social work event! ericholscher.com/blog/2017/aug

  22. going to my first #writethedocs conf tomorrow in Berlin, and have larned of the lovely Pac-Man rule. This should be standard at every social work event! ericholscher.com/blog/2017/aug

  23. going to my first #writethedocs conf tomorrow in Berlin, and have larned of the lovely Pac-Man rule. This should be standard at every social work event! ericholscher.com/blog/2017/aug

  24. going to my first #writethedocs conf tomorrow in Berlin, and have larned of the lovely Pac-Man rule. This should be standard at every social work event! ericholscher.com/blog/2017/aug

  25. RE: fosstodon.org/@openhomefoundat

    On the Warszawa-Berlin express once more 🚅
    Going to #WriteTheDocs Berlin, to meet local friends, and also Open Home Foundation colleagues IRL for the first time

  26. RE: fosstodon.org/@openhomefoundat

    On the Warszawa-Berlin express once more 🚅
    Going to #WriteTheDocs Berlin, to meet local friends, and also Open Home Foundation colleagues IRL for the first time

  27. RE: fosstodon.org/@openhomefoundat

    On the Warszawa-Berlin express once more 🚅
    Going to Berlin, to meet local friends, and also Open Home Foundation colleagues IRL for the first time

  28. RE: fosstodon.org/@openhomefoundat

    On the Warszawa-Berlin express once more 🚅
    Going to #WriteTheDocs Berlin, to meet local friends, and also Open Home Foundation colleagues IRL for the first time

  29. RE: fosstodon.org/@openhomefoundat

    On the Warszawa-Berlin express once more 🚅
    Going to #WriteTheDocs Berlin, to meet local friends, and also Open Home Foundation colleagues IRL for the first time

  30. So you know how it's important to be brief when writing?

    Its because we're here for a good tome not a long tome...

    #writethedocs

  31. So you know how it's important to be brief when writing?

    Its because we're here for a good tome not a long tome...

    #writethedocs

  32. So you know how it's important to be brief when writing?

    Its because we're here for a good tome not a long tome...

    #writethedocs

  33. So you know how it's important to be brief when writing?

    Its because we're here for a good tome not a long tome...

    #writethedocs

  34. So you know how it's important to be brief when writing?

    Its because we're here for a good tome not a long tome...

    #writethedocs

  35. Technical writer job is open:
    * based in Auckland
    * Hybrid - 2 days a week in CBD office
    * Suitable for intermediate level technical writer.

    apply.workable.com/vista-group

    I have no connection to the company. I am simply spreading the news for tech writers who may be seeking a new job.

    #TechnicalWriters #WriteTheDocs #NewZealand #FediHire_nz

  36. Technical writer job is open:
    * based in Auckland
    * Hybrid - 2 days a week in CBD office
    * Suitable for intermediate level technical writer.

    apply.workable.com/vista-group

    I have no connection to the company. I am simply spreading the news for tech writers who may be seeking a new job.

    #TechnicalWriters #WriteTheDocs #NewZealand #FediHire_nz

  37. Technical writer job is open:
    * based in Auckland
    * Hybrid - 2 days a week in CBD office
    * Suitable for intermediate level technical writer.

    apply.workable.com/vista-group

    I have no connection to the company. I am simply spreading the news for tech writers who may be seeking a new job.

    #TechnicalWriters #WriteTheDocs #NewZealand #FediHire_nz

  38. Technical writer job is open:
    * based in Auckland
    * Hybrid - 2 days a week in CBD office
    * Suitable for intermediate level technical writer.

    apply.workable.com/vista-group

    I have no connection to the company. I am simply spreading the news for tech writers who may be seeking a new job.

    #TechnicalWriters #WriteTheDocs #NewZealand #FediHire_nz

  39. Technical writer job is open:
    * based in Auckland
    * Hybrid - 2 days a week in CBD office
    * Suitable for intermediate level technical writer.

    apply.workable.com/vista-group

    I have no connection to the company. I am simply spreading the news for tech writers who may be seeking a new job.

    #TechnicalWriters #WriteTheDocs #NewZealand #FediHire_nz

  40. First-time speakers are warmly encouraged, especially if you’ve done useful docs work but haven’t spoken about it publicly before.

    Submit a proposal even if you’re still shaping the talk. We’d be happy to see the idea early.

    #IndiaFOSS #WriteTheDocs #TechnicalWriting

  41. First-time speakers are warmly encouraged, especially if you’ve done useful docs work but haven’t spoken about it publicly before.

    Submit a proposal even if you’re still shaping the talk. We’d be happy to see the idea early.

    #IndiaFOSS #WriteTheDocs #TechnicalWriting

  42. First-time speakers are warmly encouraged, especially if you’ve done useful docs work but haven’t spoken about it publicly before.

    Submit a proposal even if you’re still shaping the talk. We’d be happy to see the idea early.

    #IndiaFOSS #WriteTheDocs #TechnicalWriting

  43. First-time speakers are warmly encouraged, especially if you’ve done useful docs work but haven’t spoken about it publicly before.

    Submit a proposal even if you’re still shaping the talk. We’d be happy to see the idea early.

    #IndiaFOSS #WriteTheDocs #TechnicalWriting

  44. First-time speakers are warmly encouraged, especially if you’ve done useful docs work but haven’t spoken about it publicly before.

    Submit a proposal even if you’re still shaping the talk. We’d be happy to see the idea early.

    #IndiaFOSS #WriteTheDocs #TechnicalWriting

  45. It's the first of the month and you know what that means: time to document something with a README file github.com/ddbeck/readme-check #WriteTheDocs

  46. It's the first of the month and you know what that means: time to document something with a README file github.com/ddbeck/readme-check #WriteTheDocs

  47. It's the first of the month and you know what that means: time to document something with a README file github.com/ddbeck/readme-check #WriteTheDocs

  48. It's the first of the month and you know what that means: time to document something with a README file github.com/ddbeck/readme-check #WriteTheDocs

  49. It's the first of the month and you know what that means: time to document something with a README file github.com/ddbeck/readme-check #WriteTheDocs

  50. Serious open source docs work has a cost. I wrote down every way that I know of that gets docs authors and maintainers paid. ddbeck.com/where-does-the-mone #WriteTheDocs

  51. Serious open source docs work has a cost. I wrote down every way that I know of that gets docs authors and maintainers paid. ddbeck.com/where-does-the-mone #WriteTheDocs

  52. Serious open source docs work has a cost. I wrote down every way that I know of that gets docs authors and maintainers paid. ddbeck.com/where-does-the-mone #WriteTheDocs

  53. Serious open source docs work has a cost. I wrote down every way that I know of that gets docs authors and maintainers paid. ddbeck.com/where-does-the-mone #WriteTheDocs

  54. Serious open source docs work has a cost. I wrote down every way that I know of that gets docs authors and maintainers paid. ddbeck.com/where-does-the-mone #WriteTheDocs

  55. Join us for a discussion about docs tooling and related topics at #PyconUS today at 4pm, room S3. #writethedocs

  56. Join us for a discussion about docs tooling and related topics at today at 4pm, room S3.