[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-2NN34yxpvfFAMLZWvXSdnhVe0dAM9Vf7-cn0GjGVaBo":3,"sanity-pRuDdzc2x3VS6gKJXD9mw86k_6gcA8r7-YPgbb4A58M":351},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":326},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"50f4509c-4f55-4f11-8adc-5556e821ea77","2026-06-30T07:40:00.000Z",{"_type":10,"current":11},"slug","why-intent-prediction-needs-more-than-an-llm",null,"Why intent prediction needs more than an LLM",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":59,"comments":296,"dateUrl":297,"excerpt":257,"image":298,"legacyBody":300,"product":12,"publishedAt":303,"slug":304,"sponsored":12,"tags":306,"title":325,"visible":296},"2023-05-25T09:36:59Z","wp-post-3773","dgl3SCUzppW3U2LvCoS7wy","blogPost","2023-07-13T14:54:34Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":54,"name":55,"role":56,"slug":57},"2023-05-23T16:27:18Z","wp-author-114","07ZbrKPSUrjrV4wQ6fam8u","blogAuthor","2023-08-29T11:49:01Z",{"_type":53},"image","former","Jeff Atwood","Co-founder",{"current":58},"jeffatwood",[60,94,103,111,123,131,150,163,174,185,204,223,251,259,264,277],{"_key":61,"_type":62,"children":63,"markDefs":87,"style":93},"51bea94eebeb","block",[64,69,74,78,83],{"_key":65,"_type":66,"marks":67,"text":68},"51bea94eebeb0","span",[],"Since the Stack Exchange API went into ",{"_key":70,"_type":66,"marks":71,"text":73},"51bea94eebeb1",[72],"3b6d47ab70b8","public beta",{"_key":75,"_type":66,"marks":76,"text":77},"51bea94eebeb2",[],", and we started ",{"_key":79,"_type":66,"marks":80,"text":82},"51bea94eebeb3",[81],"70939ac3c25b","our totally awesome API contest",{"_key":84,"_type":66,"marks":85,"text":86},"51bea94eebeb4",[],", we've run into a bit of self-inflicted confusion:",[88,91],{"_key":72,"_type":89,"href":90,"reference":12},"link","http:\u002F\u002Fblog.stackoverflow.com\u002F2010\u002F05\u002Fstack-exchange-api-public-beta-starts\u002F",{"_key":81,"_type":89,"href":92,"reference":12},"http:\u002F\u002Fblog.stackoverflow.com\u002F2010\u002F05\u002Fstack-exchange-api-contest\u002F","normal",{"_key":95,"_type":62,"children":96,"markDefs":101,"style":102},"2788186820cd",[97],{"_key":98,"_type":66,"marks":99,"text":100},"2788186820cd0",[],"How can I use the Stack Overflow | Server Fault | Super User name and logo in my application?",[],"blockquote",{"_key":104,"_type":62,"children":105,"markDefs":110,"style":93},"d606a1d4a14e",[106],{"_key":107,"_type":66,"marks":108,"text":109},"d606a1d4a14e0",[],"While we had a general \"we know proper usage when we see it\" idea about this, we didn't have a document describing the specific do's and don'ts. But now we do!",[],{"_key":112,"_type":62,"children":113,"markDefs":119,"style":122},"34e95c58ed34",[114],{"_key":115,"_type":66,"marks":116,"text":118},"34e95c58ed340",[117],"7a385099ece6","Guidelines for the Use of the Stack Exchange Trademarks",[120],{"_key":117,"_type":89,"href":121,"reference":12},"http:\u002F\u002Fstackoverflow.com\u002Flegal\u002Ftrademark-guidance","h2",{"_key":124,"_type":62,"children":125,"markDefs":130,"style":93},"41f9013e60e7",[126],{"_key":127,"_type":66,"marks":128,"text":129},"41f9013e60e70",[],"(also available by clicking the legal link in the footer of any network site page)",[],{"_key":132,"_type":62,"children":133,"markDefs":147,"style":93},"4d3a0e16917d",[134,138,143],{"_key":135,"_type":66,"marks":136,"text":137},"4d3a0e16917d0",[],"While this is the most urgently needed info we didn't have, we also took the opportunity to improve a few other legal documents for the ",{"_key":139,"_type":66,"marks":140,"text":142},"4d3a0e16917d1",[141],"eac17d767f71","brave new world of Stack Exchange 2.0",{"_key":144,"_type":66,"marks":145,"text":146},"4d3a0e16917d2",[],":",[148],{"_key":141,"_type":89,"href":149,"reference":12},"http:\u002F\u002Fblog.stackoverflow.com\u002F2010\u002F04\u002Fchanges-to-stack-exchange\u002F",{"_key":151,"_type":62,"children":152,"level":158,"listItem":159,"markDefs":160,"style":93},"8a0dce016b55",[153],{"_key":154,"_type":66,"marks":155,"text":157},"8a0dce016b550",[156],"ca2639173cd1","Terms of Service",1,"bullet",[161],{"_key":156,"_type":89,"href":162,"reference":12},"http:\u002F\u002Fmeta.stackoverflow.com\u002Flegal\u002Fterms-of-service",{"_key":164,"_type":62,"children":165,"level":158,"listItem":159,"markDefs":171,"style":93},"465c39d1af7d",[166],{"_key":167,"_type":66,"marks":168,"text":170},"465c39d1af7d0",[169],"f905ea6dd4f4","Privacy Policy",[172],{"_key":169,"_type":89,"href":173,"reference":12},"http:\u002F\u002Fmeta.stackoverflow.com\u002Flegal\u002Fprivacy-policy",{"_key":175,"_type":62,"children":176,"level":158,"listItem":159,"markDefs":182,"style":93},"afaad71e6e08",[177],{"_key":178,"_type":66,"marks":179,"text":181},"afaad71e6e080",[180],"66d06d18f4c8","Content Policy",[183],{"_key":180,"_type":89,"href":184,"reference":12},"http:\u002F\u002Fmeta.stackoverflow.com\u002Flegal\u002Fcontent-policy",{"_key":186,"_type":62,"children":187,"markDefs":201,"style":93},"b92794c76e2e",[188,192,197],{"_key":189,"_type":66,"marks":190,"text":191},"b92794c76e2e0",[],"We tried our best to avoid ",{"_key":193,"_type":66,"marks":194,"text":196},"b92794c76e2e1",[195],"51b9a5f6f98b","legalese",{"_key":198,"_type":66,"marks":199,"text":200},"b92794c76e2e2",[]," in these documents:",[202],{"_key":195,"_type":89,"href":203,"reference":12},"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FLegal_writing#Legalese",{"_key":205,"_type":62,"children":206,"markDefs":220,"style":102},"d3239eeeb895",[207,211,216],{"_key":208,"_type":66,"marks":209,"text":210},"d3239eeeb8950",[],"Legalese is an English term first used in 1914 for legal writing that is designed to be difficult for laymen to read and understand, the implication being that this abstruseness is deliberate for excluding the legally untrained and to justify high fees. Legalese, as a term, has been adopted in other languages. Legalese is characterized by long sentences, many modifying clauses, complex vocabulary, high abstraction, and insensitivity to the layman's need to understand the document's gist. Legalese arises most commonly in legal drafting, yet appears in both types of legal analysis. Today, the ",{"_key":212,"_type":66,"marks":213,"text":215},"d3239eeeb8951",[214],"1cff7a41d68e","Plain Language Movement",{"_key":217,"_type":66,"marks":218,"text":219},"d3239eeeb8952",[]," in legal writing is progressing and experts are busy trying to demystify legalese.",[221],{"_key":214,"_type":89,"href":222,"reference":12},"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPlain_Language_Movement",{"_key":224,"_type":62,"children":225,"markDefs":248,"style":93},"618a2318c3ef",[226,230,235,239,244],{"_key":227,"_type":66,"marks":228,"text":229},"618a2318c3ef0",[],"If you're unfamiliar, the ",{"_key":231,"_type":66,"marks":232,"text":234},"618a2318c3ef1",[233],"34d8deedec17","legalese hall of shame",{"_key":236,"_type":66,"marks":237,"text":238},"618a2318c3ef2",[]," is a great reminder of what we're striving to ",{"_key":240,"_type":66,"marks":241,"text":243},"618a2318c3ef3",[242],"em","avoid",{"_key":245,"_type":66,"marks":246,"text":247},"618a2318c3ef4",[]," here.",[249],{"_key":233,"_type":89,"href":250,"reference":12},"http:\u002F\u002Fwww.partyofthefirstpart.com\u002FhallOfShame.html",{"_key":252,"_type":62,"children":253,"markDefs":258,"style":93},"b4fa0a728ad9",[254],{"_key":255,"_type":66,"marks":256,"text":257},"b4fa0a728ad90",[],"",[],{"_key":260,"_type":53,"alt":12,"asset":261,"markDefs":12},"1063a4a06747",{"_ref":262,"_type":263},"image-cae90faf3ffa14849ae0687c573f4b2259b92f5a-428x450-jpg","reference",{"_key":265,"_type":62,"children":266,"markDefs":276,"style":93},"b2c454796f4c",[267,271],{"_key":268,"_type":66,"marks":269,"text":270},"b2c454796f4c0",[],"Please review these documents and let us know if they are reasonably clear, and answer your main questions, particularly concerning ",{"_key":272,"_type":66,"marks":273,"text":275},"b2c454796f4c1",[274],"strong","usage of our logos, domains, and names in your own applications.",[],{"_key":278,"_type":62,"children":279,"markDefs":293,"style":93},"6c279c1545ad",[280,284,289],{"_key":281,"_type":66,"marks":282,"text":283},"6c279c1545ad0",[],"While you can always comment here on the blog as usual, I ",{"_key":285,"_type":66,"marks":286,"text":288},"6c279c1545ad1",[287],"509907606845","opened a meta topic",{"_key":290,"_type":66,"marks":291,"text":292},"6c279c1545ad2",[]," if you have any specific, actionable feedback you'd like us to follow up on.",[294],{"_key":287,"_type":89,"href":295,"reference":12},"http:\u002F\u002Fmeta.stackoverflow.com\u002Fquestions\u002F52894\u002Fnew-legal-jibba-jabba-for-your-reading-pleasure",true,"2010\u002F06\u002F08",{"_type":53,"asset":299},{"_ref":262,"_type":263},{"code":301,"language":302},"\u003Cp>Since the Stack Exchange API went into \u003Ca href=\"http:\u002F\u002Fblog.stackoverflow.com\u002F2010\u002F05\u002Fstack-exchange-api-public-beta-starts\u002F\">public beta\u003C\u002Fa>, and we started \u003Ca href=\"http:\u002F\u002Fblog.stackoverflow.com\u002F2010\u002F05\u002Fstack-exchange-api-contest\u002F\">our totally awesome API contest\u003C\u002Fa>, we've run into a bit of self-inflicted confusion:\u003C\u002Fp>\n\u003Cblockquote>\n  \u003Ch2>How can I use the Stack Overflow | Server Fault | Super User name and logo in my application?\u003C\u002Fh2>\n\u003C\u002Fblockquote>\n\u003Cp>While we had a general \"we know proper usage when we see it\" idea about this, we didn't have a document describing the specific do's and don'ts. But now we do!\u003C\u002Fp>\n\u003Ch2>\u003Ca href=\"http:\u002F\u002Fstackoverflow.com\u002Flegal\u002Ftrademark-guidance\">Guidelines for the Use of the Stack Exchange Trademarks\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>(also available by clicking the legal link in the footer of any network site page)\u003C\u002Fp>\n\u003Cp>While this is the most urgently needed info we didn't have, we also took the opportunity to improve a few other legal documents for the \u003Ca href=\"http:\u002F\u002Fblog.stackoverflow.com\u002F2010\u002F04\u002Fchanges-to-stack-exchange\u002F\">brave new world of Stack Exchange 2.0\u003C\u002Fa>:\u003C\u002Fp>\n\u003Cul>\u003Cli>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fmeta.stackoverflow.com\u002Flegal\u002Fterms-of-service\">Terms of Service\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fmeta.stackoverflow.com\u002Flegal\u002Fprivacy-policy\">Privacy Policy\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fmeta.stackoverflow.com\u002Flegal\u002Fcontent-policy\">Content Policy\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\u003Cp>We tried our best to avoid \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FLegal_writing#Legalese\">legalese\u003C\u002Fa> in these documents:\u003C\u002Fp>\n\u003Cblockquote>\nLegalese is an English term first used in 1914 for legal writing that is designed to be difficult for laymen to read and understand, the implication being that this abstruseness is deliberate for excluding the legally untrained and to justify high fees. Legalese, as a term, has been adopted in other languages. Legalese is characterized by long sentences, many modifying clauses, complex vocabulary, high abstraction, and insensitivity to the layman's need to understand the document's gist. Legalese arises most commonly in legal drafting, yet appears in both types of legal analysis. Today, the \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FPlain_Language_Movement\">Plain Language Movement\u003C\u002Fa> in legal writing is progressing and experts are busy trying to demystify legalese.\n\u003C\u002Fblockquote>\n\u003Cp>If you're unfamiliar, the \u003Ca href=\"http:\u002F\u002Fwww.partyofthefirstpart.com\u002FhallOfShame.html\">legalese hall of shame\u003C\u002Fa> is a great reminder of what we're striving to \u003Cem>avoid\u003C\u002Fem> here.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.partyofthefirstpart.com\u002FhallOfShame.html\">\u003Cimg src=\"http:\u002F\u002Fstackoverflow.blog\u002Fwp-content\u002Fuploads\u002F2017\u002F02\u002Fd2rdA.jpg\" alt=\"\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Please review these documents and let us know if they are reasonably clear, and answer your main questions, particularly concerning \u003Cstrong>usage of our logos, domains, and names in your own applications.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>While you can always comment here on the blog as usual, I \u003Ca href=\"http:\u002F\u002Fmeta.stackoverflow.com\u002Fquestions\u002F52894\u002Fnew-legal-jibba-jabba-for-your-reading-pleasure\">opened a meta topic\u003C\u002Fa> if you have any specific, actionable feedback you'd like us to follow up on.\u003C\u002Fp>","html","2010-06-08T12:00:00.000Z",{"current":305},"guidelines-for-use-of-our-logo-and-name",[307,315,320],{"_createdAt":308,"_id":309,"_rev":310,"_type":311,"_updatedAt":308,"slug":312,"title":314},"2023-05-23T16:43:21Z","wp-tagcat-community","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":313},"community","Community",{"_createdAt":308,"_id":316,"_rev":310,"_type":311,"_updatedAt":308,"slug":317,"title":319},"wp-tagcat-company",{"current":318},"company","Company",{"_createdAt":308,"_id":321,"_rev":310,"_type":311,"_updatedAt":308,"slug":322,"title":324},"wp-tagcat-legal",{"current":323},"legal","Legal","Guidelines for Use of our Logo and Name",[327,333,339,345],{"_id":328,"publishedAt":329,"slug":330,"sponsored":12,"title":332},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":331},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":334,"publishedAt":335,"slug":336,"sponsored":12,"title":338},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":337},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":340,"publishedAt":341,"slug":342,"sponsored":12,"title":344},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":343},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":346,"publishedAt":347,"slug":348,"sponsored":12,"title":350},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":349},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":352,"sourceMap":-1},{"count":353,"lastTimestamp":12},0]