MetaTalk posts tagged with documentation http://metatalk.metafilter.com/tags/documentation Posts tagged with 'documentation' at MetaTalk. Wed, 02 Feb 2022 08:24:00 -0800 Wed, 02 Feb 2022 08:24:00 -0800 en-us http://blogs.law.harvard.edu/tech/rss 60 FanFare is confusing and scary. How can we make it not? http://metatalk.metafilter.com/25990/FanFare%2Dis%2Dconfusing%2Dand%2Dscary%2DHow%2Dcan%2Dwe%2Dmake%2Dit%2Dnot Something that came up in "<a href="https://metatalk.metafilter.com/25988/Mefi-as-a-Counteraction-to-an-Upcoming-Terrible-Media-Age">Mefi as a Counteraction to an Upcoming "Terrible Media Age"? </a>" is that FanFare seems like a part of Metafilter that has the potential for significant growth. However, as someone who is generally familiar with Mefi culture and who is interested in engaging with FanFare, the ways to engage with it and social norms are largely inscrutable to me. How can we fix this? I think what I'd like is a document that explains "here is how FanFare works, and here are a handful of ways that people choose to engage with it". But I'm sure there are other solutions and improvements that could be made as well. Here are some specific things that I find confusing or that make me wary of engaging: <ul> <li>If I'm consuming media that is old/obscure, is it worth making a post about? How can I know that people will be interested before I put in the effort of trying to start a discussion?</li> <li>It seems like often people will get together and decide to rewatch some TV show/etc. How does that happen? Does one person just decide to try to make it happen? Does that usually work?</li> <li>If the kind of media I tend to consume isn't on FanFare right now, how can I tell whether that's because the people on FanFare aren't interested in that kind of media, vs no one having happened to post it yet?</li> <li>In general, is the expectation that people use FanFare as a place to find media that they wouldn't have otherwise, or is the idea that they go there to discuss media they already know they like?</li> <li>How do clubs work? Do people use them? How do they get made?</li> <li>What kinds of media are OK, and what aren't? There's a books section, but it doesn't seem like people talk about nonfiction books much — are those out of place/not welcome?</li> <li>How can I follow media that I would like to get notified if there are discussions on in the future? Is this what "My FanFare" is for? How does that work?</li> <li>Similarly, if I consume some piece of media after there's already a old thread about it, how old is too old to post in the existing thread? A week? A month? A year?</li> <li>Is there any way to subscribe to updates to a specific post, so you can know if someone posts in it in the future without having to go an check back constantly?</li> </ul> I would be curious to hear from other people who haven't engaged with FanFare despite being interested about what their reasons for hesitation are. I'm also curious to know the answers to my questions, but my hope is less that I specifically will have my questions answered, and more that future people who are interested in engaging with FanFare won't have to have the same questions, since they'll be answered in some obvious place. tag:metatalk.metafilter.com,2022:site.25990 Wed, 02 Feb 2022 08:24:00 -0800 documentation fanfare wesleyac Site Update #7, 2020 http://metatalk.metafilter.com/25689/Site%2DUpdate%2D7%2D2020 Hello, everyone! Teeth gritted, we continue on towards November. Development <ul> <li>Internally, we’re getting some things set up so we can cross-train a few staff members to be able to make minor text and HTML bugfixes, hopefully making better use of Frimble’s time. <li>The backend tech for getting the profile pronoun field change pushed live is still in progress <li>The “also on” services list has been tidied with no-longer running services removed <li>Bugs: <ul> <li>Frimble has fixed the Chrome https redirect problem <li>A bug with the Best of RSS feed has been resolved <li>The issue with some emails from us not getting received has been solved. </li></li></li></ul></li></li></li></li></ul> General <ul> <li><a href="https://metatalk.metafilter.com/25678/MetaFilter-Gift-Swap-2020-Sign-ups">Signups are open</a> for the annual Metafilter Gift Swap! The deadline to sign up is Oct. 28: <li>US-based Mefites, <a href="https://metatalk.metafilter.com/25684/If-youre-in-the-US-vote-and-get-Trump-out-of-office">don't forget to vote</a> if you can! </li></li></ul> Advisory Board <ul> <li>The next BIPOC Advisory Board Meeting is being scheduled. <li>The full meeting minutes from meeting #1 have been approved and are posted on <a href="https://www.metafilter.com/board-rc.mefi">the Board page</a>. <li> Meeting #2 was held on 10/11 and the minutes are being reviewed from that meeting. <li>We are paying an honorarium per meeting for each board member, and we welcome funding for it! If you want to help with this, you can do that via the <a href="https://login.metafilter.com/funding.mefi">Funding Page</a>. Just send a message via the <a href="https://www.metafilter.com/contact/">Contact Form</a> or to <a href="mailto:travelingthyme@metafilter.com">travelingthyme@metafilter.com</a> and let us know to earmark your contribution for that purpose. <li>If any POC are interested in participating in the board or receiving meeting notes regularly, please email <a href="mailto:travelingthyme@metafilter.com">travelingthyme@metafilter.com</a> </li></li></li></li></li></ul> Documentation <ul> <li>Loup continues with work on the GDPR compliance documents, a formal Privacy Policy, and similar tasks. <li>Several questions on the FAQ have been updated, and updates will continue. (It’s a very long FAQ.) As always, if you see problems or have questions, <a href="https://www.metafilter.com/contact/">contact us!</a> </li></li></ul> Thanks! We'll post another Site Update on Nov. 6. (<a href="https://metatalk.metafilter.com/tags/siteupdate">previous updates</a>) tag:metatalk.metafilter.com,2020:site.25689 Fri, 23 Oct 2020 13:32:45 -0800 advisoryboard development documentation siteupdate swap restless_nomad Site Update #6, 2020 http://metatalk.metafilter.com/25676/Site%2DUpdate%2D6%2D2020 Hey everyone! It's been a wild couple of weeks in the world, but fortunately not quite as wild here in Metafilter HQ. We're celebrating a successful Fundraising Month, chugging forward with a bunch of long-term projects, and beginning to plot some fun stuff for later in the year. Development <ul> <li>A project that jumped to the top of the list this week was an internal tool to help us make sure user requests get captured and tracked accurately across shifts. <li>The backend tech for getting the profile pronoun field change pushed live is still in progress <li>Bugs: <ul> <li>Frimble is digging into the Chrome problem with posting and mysteriously mixed http/https <li>They’re also trying to find why some emails are getting lost. If you send a contact form message and don’t get a reply within an hour or two, please <a href="https://www.metafilter.com/contact/">try again</a> and/or mefi mail a mod while we try to sort this out. </li></li></ul></li></li></li></ul> General <ul> <li>As the US political season heats up, please remember to stay on topic. We are NOT running megathreads; just because it’s political doesn’t mean it goes in a thread about a different political subject. <li>If you missed it, the <a href="https://metatalk.metafilter.com/25673/The-Fundraising-Month-Finale">Fundraising Month Wrap-Up</a> is here! <li>A reminder - you can use<a href="https://irl.metafilter.com/"> IRL</a> to schedule online meetups! Just choose “Online” as the Event Category. </li></li></li></ul> Advisory Board <ul> <li>The next BIPOC Advisory Board Meeting is this Sunday, 10/11. <li>You can read about the update from the previous meeting <a href="https://www.metafilter.com/board-rc.mefi">here</a>. <li>We are paying an honorarium per meeting for each board member, and we welcome funding for it! If you want to help with this, you can do that via the <a href="https://login.metafilter.com/funding.mefi">Funding Page</a>. Just send a message via the <a href="https://www.metafilter.com/contact/">Contact Form</a> or to <a href="mailto:travelingthyme@metafilter.com">travelingthyme@metafilter.com</a> and let us know to earmark your contribution for that purpose. <li>If any POC are interested in participating in the board or receiving meeting notes regularly, please email <a href="mailto:travelingthyme@metafilter.com">travelingthyme@metafilter.com</a> </li></li></li></li></ul> Documentation <ul> <li>Loup continues with work on the GDPR compliance documents, a formal Privacy Policy, and similar tasks. <li>Updates to the FAQ are in progress - anything with the “2020update” tag is slated for review. If you see a question without that tag that seems out of date or confusing, please<a href="https://www.metafilter.com/contact/"> drop us a line</a>. Likewise let us know if there’s a question you would like to see answered! </li></li></ul> Thanks, folks! Look for the next Site Update on Oct. 23. (<a href="https://metatalk.metafilter.com/tags/siteupdate">previous updates</a>) tag:metatalk.metafilter.com,2020:site.25676 Fri, 09 Oct 2020 13:32:40 -0800 advisoryboard development documentation siteupdate restless_nomad Site Update #3, 2020 http://metatalk.metafilter.com/25648/Site%2DUpdate%2D3%2D2020 Hello everyone! We’re coming to the end of August, and things are getting caught up around here. We have a lot of stuff in store, so stay tuned! As usual, comments are turned off. Drop us a line at the <a href="https://www.metafilter.com/contact/">Contact Form</a> if you have feedback, and you’re welcome to open a MetaTalk thread for any subject you want to discuss with the community. Development: <ul> <li>The big project this last two weeks was building out a system for the mods to be able to anonymize comments and posts on all subsites. Frimble’s got that up and working on the technical side. <ul> <li>We still have some internal discussion to do to figure out exactly what our policy and recommendations are going to be with this. Some things we would prefer to anonymize vs. delete, some things we will only delete. Figuring out the exact shape of this is on the agenda for this weekend’s staff meeting. <li>We’ll have an updated FAQ available as soon as we have that sorted out. <li>If you have questions or want to discuss this option, drop us a line and we can talk through the possibilities. </li></li></li></ul> <li>Next up is another round of back-end work - necessary but makes boring headlines. </li></li></ul> September: <ul> <li>September will be our fundraising month! We have a whole list of fun things to play with to encourage contributions and also just blow off some steam. <li>More news on this on the first and throughout the month </li></li></ul> Advisory Board: <ul> <li>The board is in the process of scheduling its first meeting! <li>If you’d like to help fund honoraria for the board, you can do that via the <a href="https://login.metafilter.com/funding.mefi">Funding Page</a>. Just send a message via the <a href="https://www.metafilter.com/contact/">Contact Form</a> or to <a href="mailto:travelingthyme@metafilter.com">travelingthyme@metafilter.com</a> and let us know to earmark your contribution for that purpose. <li>If any POC are interested in participating in the board or receiving meeting notes regularly, please email <a href="mailto:travelingthyme@metafilter.com">travelingthyme@metafilter.com</a> </li></li></li></ul> Documentation: <ul> <li>Loup’s big project this last two weeks was the <a href="https://www.metafilter.com/content_policy.mefi">Content Policy</a>. This is a companion to the Guidelines, and lays out in simple terms the kind of content we <em>don’t</em> allow. <li>Next up is some of the complicated legal stuff around the GDPR and our Privacy Policy. This will likely take a while (and will involve outside consultation) so I don’t have an ETA as yet. </li></li></ul> Moderation: <ul> <li>We’ve had <a href="https://metatalk.metafilter.com/25642/Talk-less">a couple</a> of <a href="https://metatalk.metafilter.com/25646/FPP-Local-Elections">general</a> MetaTalk threads discussing the impact and structure of (mostly US) politics threads on the site. If you haven’t given those a look, and you’re active in political discussions here, I recommend you do so. Politics threads remain the most contentious, difficult-to-moderate, and high-bandwidth threads on the site, and improving them is going to require the participants to be thoughtful about their own interactions. </ul> Thank you, everyone! The next update will be on September 11, 2020. (<a href="https://metatalk.metafilter.com/tags/siteupdate">previous updates</a>)</li> tag:metatalk.metafilter.com,2020:site.25648 Fri, 28 Aug 2020 11:38:16 -0800 contentpolicy development documentation moderation siteupdate update restless_nomad Rolling out some updated site documentation http://metatalk.metafilter.com/25343/Rolling%2Dout%2Dsome%2Dupdated%2Dsite%2Ddocumentation We're updating some site documents today to better reflect contemporary MetaFilter.  Today's updates include the New User pages that potential new community members move through when signing up, the site's core guidelines page, and a new document discussing common microaggressions and being mindful about the impact of dominant-culture dynamics on a diverse membership.  I'll talk in more detail about all that below the fold. MeFi's documentation has been built up incrementally over the last 20 years, and a lot of pieces of it are closer to 20 years old than they should be.  We talked earlier this year about revisiting all of it for updates, and this is part of that.  These documents in particular are among the first things someone joining the site will see, so we wanted to make sure they cover some basic but fundamental ground about what this place is and what expectations we have for community members. The mod team ended up rewriting most of these from scratch; as much as the historical value of the old pages has a place in my heart, revising those in place would have made for messy, compromised documents mostly <i>for</i> historical value's sake, so we've chosen to make a fresh start on these instead. The new pages: - the <a href="https://www.metafilter.com/newuser.mefi">New User page</a>, which potential new members reach when they click on the "Sign Up" link on the front page.  The old version was a little structurally scattered and philosophical.  The new one outlines more directly the signup process itself and hits on the major points of confusion or site misuse we run into with new users, and is more concise overall. (Here's the <a href="https://www.metafilter.com/newuser_old.mefi">old New User page</a>, for reference.) - the <a href="https://login.metafilter.com/join.mefi">Join page</a>, where potential new members go after the New User page, which is substantially the same as before but we've slightly expanded it to be clearer about current character limitations on usernames, the visibility of optional personal info fields on profile pages, and the fact that stuff posted on the site will turn up in google searches. - the <a href="https://www.metafilter.com/guidelines.mefi">Community Guidelines and Expectations page</a> is a brief statement of the site's overarching goals and a detailed list of DOs and DON'Ts that outline point-by-point the core aspects of member participation that make this place work and the things that aren't welcome or okay, and more specifically outlines some unacceptable behavior that had been treated more as implied or assumed before.  Previously the Guidelines pages were site-specific documents for MeFi and Ask MeFi, and focused more on "good/bad post" etiquette without substantially discussing behavioral expectations; that's information that can be handled in the FAQ and on posting pages.  We want this updated Guidelines document to be a site-wide page that is more visible to the members and readers and to be more useful as a reference about basic expectations in comments and interactions. (Old <a href="https://www.metafilter.com/guidelines_old.mefi">MeFi</a> and <a href="https://ask.metafilter.com/guidelines_old.mefi">AskMe</a> versions.) - the entirely new <a href="https://www.metafilter.com/microaggressions.mefi">Microaggressions and making space</a> page is a more detailed run-down of a couple things: an explanation of the need for folks who belong to one or more majority or culturally-dominant groups to be aware of and take responsibility for the impact that has on other members, and a list of some of the most common microaggressions that tend to come up on MetaFilter.  These are all things that have been repeated points of discussion over the years on the site; our hope is that identifying and summing them up on this page will make it useful as a reference to point people to, so that members of marginalized groups don't feel compelled to personally do the work of explaining these points yet again when they come up in conversation on the site. We've gotten these into good enough shape to start with, so we're rolling them out now.  I don't expect them to be perfect at this point, so feedback on the details is welcome; I'd like these to be living documents informed by the community, and there are likely things we will want to tweak and add both now and in the long run while still aiming to keep them fairly concise and readable. This is a subset of the overall site documentation work we've had in progress; some of these currently link to other site pages that are dated right now but will be revised in the long run.   But we'd rather get these out as a start than delay longer to try to get the entire interlocking structure in place. Thanks again to everyone in the community for the feedback and suggestions, in site discussion and over email, that have helped inform this work. tag:metatalk.metafilter.com,2019:site.25343 Mon, 14 Oct 2019 08:49:16 -0800 community documentation guidelines metafilter microaggressions newmember newuser policy signup cortex Deleting meta-commentary without just silencing pile-on victims? http://metatalk.metafilter.com/25068/Deleting%2Dmeta%2Dcommentary%2Dwithout%2Djust%2Dsilencing%2Dpile%2Don%2Dvictims I discovered the metacommentary deletion policy under less than great circumstances. Can we talk about how to enforce that policy with a little less collateral damage? Maybe by better documentation, or user education? I had a bad experience recently on AskMe. As one of the mods later speculated over email[1], I described an unprovoked assault that didn't really make sense, so people tried to make sense of it by assuming that I had provoked it somehow. Not that it makes me feel any better, but I can believe that reasonable people got there in good faith. What bothers me is what happened when I posted a clarification with a comment at the end that I thought people were unjustifiably assuming the worst of me. That comment was deleted as metacommentary, and with it my clarification. The mods later explained over email that we have two blanket policies: any comment containing negative metacommentary will be deleted, and comments are always deleted wholesale, never redacted. While I see how these policies are individually useful, I hadn't known either of them previously, and I'm still unable to find any mention of them by searching the FAQ or the wiki. So from my perspective at the time, I had sixty people telling me I was to blame, many of them due to a clear misunderstanding of the situation. It felt natural and in many contexts would have been appropriate to say so. When the mods then turned up to delete my comment for metacommentary, that just increased my feeling of getting it from all sides. To be more specific, it feels very much like tone policing in the way a facially neutral rule about how and where to speak had the effect of removing what was mostly a substantive and permitted contribution. So I'm here to ask: I don't object to the metacommentary deletion policy, nor to the wholesale deletion policy, but what else can we do so that we can enforce those policies with less collateral damage? Two ideas: 1. Document these policies. The mods treat these as bright-line rules, and are happy to say so over email. (And someone must have known about these rules, because it was a user flag that got the mods looking at my comment.) Can we put them somewhere public, so that I don't have to email the mods after the fact to learn about them? 2. Is there any pro-active user education we can do so that people know that they're expected to turn to the mods rather than responding directly if they feel that a thread is turning against them undeservedly? That is not the norm on most of the internet. Honestly, it sounds like a better practice than most of the internet has, but it is not what people unfamiliar with the norms of this site would expect. (3. Increase mod resources s.t. people need less knowledge of the system to avail themselves of it. I was told after the fact that had a mod been following my thread earlier, they would have been able to intervene earlier. I'm guessing this one is a non-starter for budgetary reasons, outside the megathreads, but I'll put it out there just for the confirmation.) I'd ideally like to avoid making this MeTa a referendum on my specific case. I'm not looking for an apology or exoneration. I feel like I've discovered a sharp corner in the user experience and I'd like to focus discussion on padding that a little. [1] I wouldn't usually publish a private correspondence like this, but mods speaking as mods seem like fair game and anyway they will review this MeTa before it goes live. tag:metatalk.metafilter.com,2019:site.25068 Sun, 13 Jan 2019 15:37:55 -0800 askme askmetafilter documentation education metacommentary meaty shoe puppet
http://metatalk.metafilter.com/tags/documentation/rss
metatalk.metafilter.com
CC-MAIN-2023-40
27020
application/http; msgtype=response
sha1:HI72EOZUVD7MCPQREQX7B2LOTBXW3WBU
<urn:uuid:e844fa3f-c3b5-4009-ad22-c70630338022>
2023-09-29T04:25:53Z
54.203.56.158
application/rss+xml
sha1:PJNSCGIH36YLBGQATN2XFJ4MB2N3V66A
<urn:uuid:19ffa43a-2450-478b-a48e-b0bdecb1ab1e>
http://metatalk.metafilter.com/tags/documentation/rss
response
<urn:uuid:a5ecf5ee-d9c0-42dd-bd70-bfe18bb92be4>
isPartOf: CC-MAIN-2023-40
publisher: Common Crawl
description: Wide crawl of the web for September/October 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-159
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/