Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Contains text" with value "re: [[PaperBot]] we also had talked about [[DOI Search]] and resolving urls to DOIs and embedding them in the [[JSON-LD]]. the DOI Search should actually be super easy if we do it by altering the hashtag regex. doing it by making it an additional search type would take a little more, as would doing automatic dereferencing, but all those sound like fun to me". Since there have been only a few results, also nearby values are displayed.

Showing below up to 27 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

    

List of results

  • DOI Search#sneakers-the-rat-23-03-23 15:11:22  +
  • Discord Messages#sneakers-the-rat-23-03-23 15:11:22  +
  • Discord Messages#sneakers.the.rat-24-01-09 04:53:38  + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )</br>the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). </br></br>That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. </br></br>That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
  • Stoplight#sneakers.the.rat-24-01-09 04:53:38  + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )</br>the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). </br></br>That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. </br></br>That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
  • Cooldown#sneakers.the.rat-24-01-09 04:53:38  + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )</br>the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). </br></br>That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. </br></br>That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
  • Sidekiq#sneakers.the.rat-24-01-09 04:53:38  + (so re: [[Stoplight]] … so re: [[Stoplight]] and [[Cooldown]]s, [[Sidekiq#Cooldown]] tries to deliver something 16 times ( https://github.com/NeuromatchAcademy/mastodon/blob/eb24c0ad07c4137517e6bd37ebcc99d6e2b86797/app/workers/activitypub/delivery_worker.rb#L11 )</br>the delay rises exponentially (^4) with each retry. So eg by the 10th retry we're delaying an average of 208 minutes, and by 16 we're at 1365 (22 hours). </br></br>That delay uses sidekiq's `sidekiq_retry_in` method, which applies to each delivery task (ie. each status we're trying to push), but there is also an additional control flow tool Stoplight ( https://blog.bolshakov.dev/stoplight/ ) that applies per inbox URL (rather than per job). You start in a good (green) state. Each failure counts towards a threshold (10), after which it halts all jobs matching that inbox (red). After the cooldown period (60 seconds) it flips into a "yellow" state: if the next job succeeds, it flips back to green. If it fails, it goes immediately back to red. </br></br>That configuration seems sorta... pointless to me? if it only kicks in after 10 failures, then it'll only be halting after really long delays, right? it seems like that should be a high threshold with like a really long cooldown to me - if we haven't been able to deliver like 200 messages, then cooldown for like 6 hours (i'm not sure if receiving a message clears the stoplight) receiving a message clears the stoplight))
  • WikiBot#sneakers-the-rat-22-12-29 00:22:33  + (the DOI thing I think will only take an ho … the DOI thing I think will only take an hour or two more, and then yeah will be adapting some of the [[WikiBot]] code that runs on this discord already to do an agora-like thing. I've talked to flancian about this as well a bunch of times, unifying the agora bots and making a general framework for that kind of cross platform linkingrk for that kind of cross platform linking)
  • Camel Case#sneakers-the-rat-22-12-29 00:27:20  + (we've talked about this as well, being abl … we've talked about this as well, being able to make the bot more granularly opt-in, as well as make some simple degeneracy rules like #CamelCase == [[Camel Case]] (actually proposed that probably to no result in masto here: https://github.com/mastodon/mastodon/issues/19992#issuecomment-1363496984 )don/issues/19992#issuecomment-1363496984 ))
  • Discord Messages#sneakers-the-rat-22-12-29 00:27:20  + (we've talked about this as well, being abl … we've talked about this as well, being able to make the bot more granularly opt-in, as well as make some simple degeneracy rules like #CamelCase == [[Camel Case]] (actually proposed that probably to no result in masto here: https://github.com/mastodon/mastodon/issues/19992#issuecomment-1363496984 )don/issues/19992#issuecomment-1363496984 ))
  • DOI Search#sneakers-the-rat-23-03-23 15:11:22  + (re: [[PaperBot]] … re: [[PaperBot]] we also had talked about [[DOI Search]] and resolving urls to DOIs and embedding them in the [[JSON-LD]]. the DOI Search should actually be super easy if we do it by altering the hashtag regex. doing it by making it an additional search type would take a little more, as would doing automatic dereferencing, but all those sound like fun to meencing, but all those sound like fun to me)
  • Discord Messages#sneakers-the-rat-23-03-23 15:11:22  + (re: [[PaperBot]] … re: [[PaperBot]] we also had talked about [[DOI Search]] and resolving urls to DOIs and embedding them in the [[JSON-LD]]. the DOI Search should actually be super easy if we do it by altering the hashtag regex. doing it by making it an additional search type would take a little more, as would doing automatic dereferencing, but all those sound like fun to meencing, but all those sound like fun to me)
  • JSON-LD#sneakers-the-rat-23-03-23 15:11:22  + (re: [[PaperBot]] … re: [[PaperBot]] we also had talked about [[DOI Search]] and resolving urls to DOIs and embedding them in the [[JSON-LD]]. the DOI Search should actually be super easy if we do it by altering the hashtag regex. doing it by making it an additional search type would take a little more, as would doing automatic dereferencing, but all those sound like fun to meencing, but all those sound like fun to me)
  • PaperBot#sneakers-the-rat-23-03-23 15:11:22  + (re: [[PaperBot]] … re: [[PaperBot]] we also had talked about [[DOI Search]] and resolving urls to DOIs and embedding them in the [[JSON-LD]]. the DOI Search should actually be super easy if we do it by altering the hashtag regex. doing it by making it an additional search type would take a little more, as would doing automatic dereferencing, but all those sound like fun to meencing, but all those sound like fun to me)
  • Discord Messages#sneakers-the-rat-23-02-02 03:11:06  + (Ah yes, this is a [[Consensus]] … Ah yes, this is a [[Consensus]] thing. I just updated the wiki page to explain a bit better: https://wiki.neuromatch.io/Mastodon/Governance#Voting</br>Yes, you can think of it analogously to a veto. Consensus refers both to making decisions that accommodate the needs of all members as well as consent - you should not be able to be coerced into consent by a bare majority of people. In more intimate consensus processes, a single person might be able to block a proposal. That becomes untenable in larger groups for sort of obvious reasons, hence the design of this governance system to have different proportional thresholds for different types of proposals, as well as division of decisionmaking power between working groups and the general membership. </br></br>A block means something different than voting in a few ways, including that blocks should be rare: consensus sort of inverts the decisionmaking process, where care should be taken to discuss with the membership and refine a proposal before, rather than after making the proposal - so in a majoritarian system one might make a proposal and make an argument in favor, people discuss in the comments and then make up their minds there. The purpose of requiring discussion beforehand is to make more space for everyone to craft the proposal in the first place, register concerns, etc. So if people are blocking a proposal, that is a sign that the process has failed (as opposed to in a majoritarian system that the proposal has failed). </br></br>Blocking also typically enjoins the person blocking to help remedy the reason for their block: if a proposal is being made in good faith, we assume that it is meeting some unmet need by the proposer/other members. If someone blocks a proposal, that will mean that it might cause them or the organization harm, but those unmet needs still remain - so it's basically like conflict res at that point. Ofc there are exceptions like not making marginalized ppl do additional labor, etc.marginalized ppl do additional labor, etc.)
  • Consensus#sneakers-the-rat-23-02-02 03:11:06  + (Ah yes, this is a [[Consensus]] … Ah yes, this is a [[Consensus]] thing. I just updated the wiki page to explain a bit better: https://wiki.neuromatch.io/Mastodon/Governance#Voting</br>Yes, you can think of it analogously to a veto. Consensus refers both to making decisions that accommodate the needs of all members as well as consent - you should not be able to be coerced into consent by a bare majority of people. In more intimate consensus processes, a single person might be able to block a proposal. That becomes untenable in larger groups for sort of obvious reasons, hence the design of this governance system to have different proportional thresholds for different types of proposals, as well as division of decisionmaking power between working groups and the general membership. </br></br>A block means something different than voting in a few ways, including that blocks should be rare: consensus sort of inverts the decisionmaking process, where care should be taken to discuss with the membership and refine a proposal before, rather than after making the proposal - so in a majoritarian system one might make a proposal and make an argument in favor, people discuss in the comments and then make up their minds there. The purpose of requiring discussion beforehand is to make more space for everyone to craft the proposal in the first place, register concerns, etc. So if people are blocking a proposal, that is a sign that the process has failed (as opposed to in a majoritarian system that the proposal has failed). </br></br>Blocking also typically enjoins the person blocking to help remedy the reason for their block: if a proposal is being made in good faith, we assume that it is meeting some unmet need by the proposer/other members. If someone blocks a proposal, that will mean that it might cause them or the organization harm, but those unmet needs still remain - so it's basically like conflict res at that point. Ofc there are exceptions like not making marginalized ppl do additional labor, etc.marginalized ppl do additional labor, etc.)
  • Discord Messages#sneakers-the-rat-22-12-17 00:07:49  + (For the moment, until we decide on a diffe … For the moment, until we decide on a different model, neuromatch bears the costs of the instance. Though we trust neuromatch to not abuse that power, one question we should answer as a community is whether we want to move to a fully cooperative model where the members of the instance support its costs so it is truly member-owned and operated. That would likely look like some sliding scale model where members are encouraged to pay what they can, a rough guideline based on nothing but vibes might be: </br>- $0/mo for students/people making <$50k annually</br>- $1/mo for postdocs/people making <$75k annually</br>- $5/mo for PIs/people making >$75k annually</br>though this would be something we would determine based on how many members we have and how much the instance costs to run. If we were to do this, then we would use opencollective to make our finances transparent. </br></br>We could also do a hybrid model where neuromatch kicks in some defined contribution and the members donate the rest, or if we establish a financial working group we could collectively apply for grants with neuromatch as a fiscal sponsor.</br></br>Another benefit is that by having some financial surplus we would be able to pay stipends to people who volunteer for mod duty/being on call for tech emergencies.</br></br>In the meantime though, mostly so the <#1049184335514828860> knows what it's working with: what kind of costs is neuromatch willing to bear? eg. upgrading to a 16GB ram node with 8 dedicated CPUs would be $120/month but would probably be as much scale as we need for the indefinite future. Currently we are going to upgrade to an 8GB ram node at $60/month, which is already $720 annually (just for the instance, we are also running another node that will host the wiki and loomio)</br><@215274946560131074> </br>[[Mastodon/Finances]][[Mastodon/Finances]])
  • Mastodon/Finances#sneakers-the-rat-22-12-17 00:07:49  + (For the moment, until we decide on a diffe … For the moment, until we decide on a different model, neuromatch bears the costs of the instance. Though we trust neuromatch to not abuse that power, one question we should answer as a community is whether we want to move to a fully cooperative model where the members of the instance support its costs so it is truly member-owned and operated. That would likely look like some sliding scale model where members are encouraged to pay what they can, a rough guideline based on nothing but vibes might be: </br>- $0/mo for students/people making <$50k annually</br>- $1/mo for postdocs/people making <$75k annually</br>- $5/mo for PIs/people making >$75k annually</br>though this would be something we would determine based on how many members we have and how much the instance costs to run. If we were to do this, then we would use opencollective to make our finances transparent. </br></br>We could also do a hybrid model where neuromatch kicks in some defined contribution and the members donate the rest, or if we establish a financial working group we could collectively apply for grants with neuromatch as a fiscal sponsor.</br></br>Another benefit is that by having some financial surplus we would be able to pay stipends to people who volunteer for mod duty/being on call for tech emergencies.</br></br>In the meantime though, mostly so the <#1049184335514828860> knows what it's working with: what kind of costs is neuromatch willing to bear? eg. upgrading to a 16GB ram node with 8 dedicated CPUs would be $120/month but would probably be as much scale as we need for the indefinite future. Currently we are going to upgrade to an 8GB ram node at $60/month, which is already $720 annually (just for the instance, we are also running another node that will host the wiki and loomio)</br><@215274946560131074> </br>[[Mastodon/Finances]][[Mastodon/Finances]])
  • Discord Messages#sneakers.the.rat-23-12-05 06:58:02  + (OK <@318247805124870145> i'm doing a … OK <@318247805124870145> i'm doing a little wiki gardening rn and here i'll narrate a little of what i'm doing as i do it to give you a sense of what that looks like:</br></br>first i am reading this and wondering how i could offer part of this to you, and with this set of prompts and with ur previous comments about 'where do i even start with this thing' which are extremely justified i want to make a 'how to get started with masto as software' page, so I go to where we have previously put such things on the Tech WG page (https://wiki.neuromatch.social/Tech_WG ) and add a link there to a new [[Intro To Mastohacking]] page ( https://wiki.neuromatch.social/Intro_To_Mastohacking ) since i figure "intro to mastodon" is too much like our general getting started on fedi pages. idk we can always change it later.</br></br>So then i do a search for "docs" to see where else we might have written stuff like this and lo and behold there's also a page for that, so i add a link from there too: https://wiki.neuromatch.social/Mastodon/Docs</br></br>then i start my new page by adding categories and backlinks. Don't worry about the syntax for right now, but what i'm doing here is making this page findable in a few different ways - by navigating from related pages, formally through the semantic relationship `Part Of`, and then also via the category system (which we can also query to eg. display a list of all pages in the "hacking" and "guide" categories if we want to make some automatic index, but i digress).</br></br>nothing on the page yet but that? fuck it, save page. we can keep saving as we update, no need to be shy on wiki</br></br>(sorry for notifs el i'm going to split this up into a few messages so i can intersperse images)into a few messages so i can intersperse images))
  • Slugified URLs#sneakers.the.rat-23-10-06 21:45:39  + (So idle thought, i saw someone whose inst … So idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )</br>And it looks like it would be pretty easy to do...</br>- add a `slug` db column in the statuses table</br>- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130</br>- add a field to the status composer component to optionally add a slug, which would need to validate for correct formatting and uniqueness (eg. Show red outline with message when slug is already used, disallow spaces and other non URI chars)</br>- add API endpoint to check if slug exists</br>- add button in "share" dropdown to copy slugified link</br>- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header</br></br>That would be for adding them as an additional ui thing, rather than changing the representation of the AP objects/etc. ID URL would remain canonical, slug would be useful for sharing, and also if we want to allow posts to behave more like pages (eg. Set custom page CSS for an `Article` type vs the usual `Note` ) for a future rich text editor hack that makes masto both micro and macro blog</br></br>[[Mastodon/Hacks]][[Mastodon/Hacks]])
  • Discord Messages#sneakers.the.rat-23-10-06 21:45:39  + (So idle thought, i saw someone whose inst … So idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )</br>And it looks like it would be pretty easy to do...</br>- add a `slug` db column in the statuses table</br>- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130</br>- add a field to the status composer component to optionally add a slug, which would need to validate for correct formatting and uniqueness (eg. Show red outline with message when slug is already used, disallow spaces and other non URI chars)</br>- add API endpoint to check if slug exists</br>- add button in "share" dropdown to copy slugified link</br>- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header</br></br>That would be for adding them as an additional ui thing, rather than changing the representation of the AP objects/etc. ID URL would remain canonical, slug would be useful for sharing, and also if we want to allow posts to behave more like pages (eg. Set custom page CSS for an `Article` type vs the usual `Note` ) for a future rich text editor hack that makes masto both micro and macro blog</br></br>[[Mastodon/Hacks]][[Mastodon/Hacks]])
  • Mastodon/Hacks#sneakers.the.rat-23-10-06 21:45:39  + (So idle thought, i saw someone whose inst … So idle thought, i saw someone whose instance had [[Slugified URLs]] for posts, ( eg. https://neuromatch.social/@Jonny /my-post-title )</br>And it looks like it would be pretty easy to do...</br>- add a `slug` db column in the statuses table</br>- add a route using `slug` https://github.com/mastodon/mastodon/blob/3262d1f1b62a984343f0f6c67c1d18921daabb0a/config/routes.rb#L130</br>- add a field to the status composer component to optionally add a slug, which would need to validate for correct formatting and uniqueness (eg. Show red outline with message when slug is already used, disallow spaces and other non URI chars)</br>- add API endpoint to check if slug exists</br>- add button in "share" dropdown to copy slugified link</br>- optionally: provide an auto-slug option that slugifies the first n unique characters in a post, or parses a leading # header</br></br>That would be for adding them as an additional ui thing, rather than changing the representation of the AP objects/etc. ID URL would remain canonical, slug would be useful for sharing, and also if we want to allow posts to behave more like pages (eg. Set custom page CSS for an `Article` type vs the usual `Note` ) for a future rich text editor hack that makes masto both micro and macro blog</br></br>[[Mastodon/Hacks]][[Mastodon/Hacks]])
  • Social WG/Responsibilities#mannaz-23-07-07 00:50:28  + (Thank you El and welcome onboard!! woohoo! … Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 </br></br>[[Social WG/Responsibilities]] continued: with great power comes great responsibility :) </br></br>Before taking any drastic decisions, we should discuss things with the instance -- things like defederation/limiting instances and banning accounts. Also, we should be careful when speaking on behalf of the instance from our "official" accounts like the @socialwg one (this one is quite scary for me because sometime mods say something that ticks another mod/instance member off and then it leads to pile ons 😬 -- so we try to be as cordial as possible and respect people from other instances even if they choose different things for their community - that's fine. we all don't have to be an exact replica of each other :) )</br></br>we learn new things from other mods too -- I follow the #fediblock hashtag and keep an eye on anything that could affect us terribly. In the past we have blocked instances based on reports from other mods on this hashtag (see <#1055915765133488158>) </br></br>I've been on call since December https://wiki.neuromatch.io/Mastodon/Mods_On_Call. You could add your availability here. Let's get you wiki access as well if you don't have already. Create an account here: https://wiki.neuromatch.io and <@305044217393053697> can approve it when they are back from their short holiday. </br></br>Being on call means I check for new account requests once a day and approve them if there aren't any issues. Or bring the discussion to the instance. And handle any reports. We get updates from linode when a few settings cross a threshold. Usually it just means the instance has been busy. But it could also be a DDoS attack -- so I also quickly browse through our local TL and this discord to see nothings blowing up. We have an admin@neuromatch.social account that I monitor every few days. We get very few emails there. monitor every few days. We get very few emails there.)
  • Discord Messages#mannaz-23-07-07 00:50:28  + (Thank you El and welcome onboard!! woohoo! … Thank you El and welcome onboard!! woohoo!! 🥳 ❤️ 💚 💜 💙 🧡 </br></br>[[Social WG/Responsibilities]] continued: with great power comes great responsibility :) </br></br>Before taking any drastic decisions, we should discuss things with the instance -- things like defederation/limiting instances and banning accounts. Also, we should be careful when speaking on behalf of the instance from our "official" accounts like the @socialwg one (this one is quite scary for me because sometime mods say something that ticks another mod/instance member off and then it leads to pile ons 😬 -- so we try to be as cordial as possible and respect people from other instances even if they choose different things for their community - that's fine. we all don't have to be an exact replica of each other :) )</br></br>we learn new things from other mods too -- I follow the #fediblock hashtag and keep an eye on anything that could affect us terribly. In the past we have blocked instances based on reports from other mods on this hashtag (see <#1055915765133488158>) </br></br>I've been on call since October https://wiki.neuromatch.io/Mastodon/Mods_On_Call. You could add your availability here. Let's get you wiki access as well if you don't have already. Create an account here: https://wiki.neuromatch.io and <@305044217393053697> can approve it when they are back from their short holiday. </br></br>Being on call means I check for new account requests once a day and approve them if there aren't any issues. Or bring the discussion to the instance. And handle any reports. We get updates from linode when a few settings cross a threshold. Usually it just means the instance has been busy. But it could also be a DDoS attack -- so I also quickly browse through our local TL and this discord to see nothings blowing up. We have an admin@neuromatch.social account that I monitor every few days. We get very few emails there. monitor every few days. We get very few emails there.)
  • Discord Messages#sneakers-the-rat-22-12-15 22:57:13  + ([[Mastodon/Tech WG#TODO]]: - Fix semantic … [[Mastodon/Tech WG#TODO]]: </br>- Fix semantic wikilinks in the [[WikiBot#TODO]], </br>- Allow `:` prefixed wikilinks to link to a page without embedding the post in that page (and then ofc stripping the colon) - this would trade off with n-back wikilinks because it wouldn't make sense to archive a series of posts at the same time as not embedding the posts into a pageime as not embedding the posts into a page)
  • WikiBot#sneakers-the-rat-22-12-15 22:57:13  + ([[Mastodon/Tech WG#TODO]]: - Fix semantic … [[Mastodon/Tech WG#TODO]]: </br>- Fix semantic wikilinks in the [[WikiBot#TODO]], </br>- Allow `:` prefixed wikilinks to link to a page without embedding the post in that page (and then ofc stripping the colon) - this would trade off with n-back wikilinks because it wouldn't make sense to archive a series of posts at the same time as not embedding the posts into a pageime as not embedding the posts into a page)
  • Discord Messages#sneakers-the-rat-22-12-21 19:37:07  + ([[Paper Thread Bot#Resolving URLs]] https://github.com/CrossRef/event-data-reverse)
  • Paper Thread Bot#sneakers-the-rat-22-12-21 19:37:07  + ([[Paper Thread Bot#Resolving URLs]] https://github.com/CrossRef/event-data-reverse)
  • Tech WG/Ops Diary#sneakers-the-rat-23-05-23 01:35:39  + ([[Tech WG/Ops Diary#23-05-22]]: What up it's me and we're about to deploy [[Exclusive Lists]] and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2)
  • Discord Messages#sneakers-the-rat-23-05-23 01:35:39  + ([[Tech WG/Ops Diary#23-05-22]]: What up it's me and we're about to deploy [[Exclusive Lists]] and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2)
  • Exclusive Lists#sneakers-the-rat-23-05-23 01:35:39  + ([[Tech WG/Ops Diary#23-05-22]]: What up it's me and we're about to deploy [[Exclusive Lists]] and update to 4.1.2. starting by making a linode backup and then following instructions on https://github.com/mastodon/mastodon/releases/tag/v4.1.2)
  • Discord Messages#mannaz-23-07-07 18:47:50  + ([[Tech WG/Ops Diary#23-07-07]]: masto 4.1. … [[Tech WG/Ops Diary#23-07-07]]: masto 4.1.3 update -- security patch. Jonny's on the road so Lina and Manisha are going to give this a try. If we muck something up, please be kind 🥺 starting by making a linode backup and then following instructions on ... </br></br>oh wait! dang they already released 4.1.4 just an hour ago </br>https://github.com/mastodon/mastodon/releases/tag/v4.1.4 </br></br>4.1.3 from yesterday: https://github.com/mastodon/mastodon/releases/tag/v4.1.3.com/mastodon/mastodon/releases/tag/v4.1.3)
  • Tech WG/Ops Diary#mannaz-23-07-07 18:47:50  + ([[Tech WG/Ops Diary#23-07-07]]: masto 4.1. … [[Tech WG/Ops Diary#23-07-07]]: masto 4.1.3 update -- security patch. Jonny's on the road so Lina and Manisha are going to give this a try. If we muck something up, please be kind 🥺 starting by making a linode backup and then following instructions on ... </br></br>oh wait! dang they already released 4.1.4 just an hour ago </br>https://github.com/mastodon/mastodon/releases/tag/v4.1.4 </br></br>4.1.3 from yesterday: https://github.com/mastodon/mastodon/releases/tag/v4.1.3.com/mastodon/mastodon/releases/tag/v4.1.3)
  • Tech WG/Ops Diary#mannaz-23-07-10 00:35:37  + ([[Tech WG/Ops Diary#23-07-09]]: Updating r … [[Tech WG/Ops Diary#23-07-09]]: Updating reverse proxy config to the recommended one</br>as root</br></br>cd /etc/nginx</br>cd sites-enabled</br>vim mastodon</br></br>search for "system"</br>added the following two headers in that block as per the release notes:</br></br>`add_header X-Content-Type-Options nosniff;</br> add_header Content-Security-Policy "default-src 'none'; form-action 'none'";`</br></br>save</br>test nginx configs are valid or not (w/o running)</br></br>`nginx -t`</br></br>all looked good</br></br>`nginx: the configuration file /etc/nginx/nginx.conf syntax is ok</br>nginx: configuration file /etc/nginx/nginx.conf test is successful`</br></br>Reload nginx</br>`nginx reload`s successful` Reload nginx `nginx reload`)
  • Discord Messages#mannaz-23-07-10 00:35:37  + ([[Tech WG/Ops Diary#23-07-09]]: Updating r … [[Tech WG/Ops Diary#23-07-09]]: Updating reverse proxy config to the recommended one</br>as root</br>`cd /etc/nginx</br>cd site-enabled</br>vim mastodon`</br></br>search for "system"</br>added the following two headers in that block as per the release notes:</br>`add_header X-Content-Type-Options nosniff;</br> add_header Content-Security-Policy "default-src 'none'; form-action 'none'"; `</br></br>save</br>test nginx configs are valid or not (w/o running)</br>`nginx -t `</br></br>all looked good</br>`nginx: the configuration file /etc/nginx/nginx.conf syntax is ok</br>nginx: configuration file /etc/nginx/nginx.conf test is successful</br>`</br>Reload nginxinx.conf test is successful ` Reload nginx)
  • Discord Messages#sneakers-the-rat-23-03-23 15:11:22  +
  • DOI Search#sneakers-the-rat-23-03-23 15:11:22  +
Retrieved from "https://wiki.neuromatch.social/Special:SearchByProperty"