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 "beepalabeep da beep beep [[Here We Go]]". Since there have been only a few results, also nearby values are displayed.

Showing below up to 26 results starting with #1.

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


    

List of results

  • Discord Messages#sneakers.the.rat-23-09-20 02:55:44  + ([[Tech WG/Ops Diary#23-09-19]] - Upgrading[[Tech WG/Ops Diary#23-09-19]] - Upgrading to 4.2-RC2 while trying to write the [[Upgrade Mastodon]] docs. currently doing the merge from upstream and noticing db migrations for exclusive lists failing, but not fixing now because that would put the fixes in the `glitch-soc-main` branch which is a local mirror of upstream which gets force pushed. Seems like that should happen in the `merge-upstream` branch after upstream is merged-upstream` branch after upstream is merged)
  • Upgrade Mastodon#mannazsci-23-10-01 07:44:40  + ([[Tech WG/Ops Diary#23-10-01]] I am ready[[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. The glitch-soc-main branch had commits from merge-upstream even after syncing the the branch. So I created a new branch called glitch-clean-sync from glitch-soc's main branch and added protections to this branch. This let's us keep this branch clean and not merge any custom features to this branch. We'd only use the sync feature. I also tried to follow the rest of the process but it seemed a bit complicated/unclear. I've tried to simplify it in a separate section above for glitch+4.2+our instance's features. I've also created a clean and stable dev-stable branch for custom features that we add. I've added branch protections here as well and PRs will require reviews on this branch.d PRs will require reviews on this branch.)
  • Tech WG/Ops Diary#mannazsci-23-10-01 07:44:40  + ([[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. I'll update the wiki with the steps I took.)
  • Discord Messages#mannazsci-23-10-01 07:44:40  + ([[Tech WG/Ops Diary#23-10-01]] I am ready to deploy v4.2 but I encountered a few issues while following the process mentioned in [[Upgrade_Mastodon]]. I'll update the wiki with the steps I took.)
  • Tech WG/Ops Diary#sneakers.the.rat-24-02-02 01:16:50  + ([[Tech WG/Ops Diary#24-02-01]] - Patching some mysterious critical security vuln thread)
  • Discord Messages#sneakers.the.rat-24-02-02 01:16:50  + ([[Tech WG/Ops Diary#24-02-01]] - Patching some mysterious critical security vuln thread)
  • Tech WG/Ops Diary#sneakers.the.rat-24-02-17 22:16:31  + ([[Tech WG/Ops Diary#24-02-14]] - Patching two more security bugs thread!)
  • Discord Messages#sneakers.the.rat-24-02-17 22:16:31  + ([[Tech WG/Ops Diary#24-02-14]] - Patching two more security bugs thread!)
  • Testing Wikibot#sneakers-the-rat-22-12-09 11:34:07  + ([[Testing Wikibot]])
  • Testing Wikibot#sneakers-the-rat-22-12-09 11:39:41  + ([[Testing Wikibot]])
  • Discord Messages#sneakers-the-rat-22-12-09 11:34:07  + ([[Testing Wikibot]])
  • Discord Messages#sneakers-the-rat-22-12-09 11:39:41  + ([[Testing Wikibot]])
  • Wiki#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Wiki/TODO#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Wikibot#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Discord Messages#sneakers-the-rat-22-12-09 12:38:45  + ([[Wiki#TODO]] Clean up link to [[Wiki/TODO]] and write some docs on [[Wikibot#Usage Patterns]])
  • Wiki/TODO#sneakers-the-rat-22-12-09 12:37:58  + ([[Wiki/TODO#Onboarding]] Document account migration process, re: https://fediscience.org/@dbarack/109483724167917771)
  • Discord Messages#sneakers-the-rat-22-12-09 12:37:58  + ([[Wiki/TODO#Onboarding]] Document account migration process, re: https://fediscience.org/@dbarack/109483724167917771)
  • Ruby#sneakers-the-rat-22-12-27 20:04:22  + (also need general [[Ruby]]also need general [[Ruby]] dev stuff, like a [[Masto Code Structure]] overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the [[Rails]] <-> [[Redux]] <-> [[React]] stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult) a declarative framework, which makes stuff difficult))
  • Masto Code Structure#sneakers-the-rat-22-12-27 20:04:22  + (also need general [[Ruby]]also need general [[Ruby]] dev stuff, like a [[Masto Code Structure]] overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the [[Rails]] <-> [[Redux]] <-> [[React]] stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult) a declarative framework, which makes stuff difficult))
  • Rails#sneakers-the-rat-22-12-27 20:04:22  + (also need general [[Ruby]]also need general [[Ruby]] dev stuff, like a [[Masto Code Structure]] overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the [[Rails]] <-> [[Redux]] <-> [[React]] stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult) a declarative framework, which makes stuff difficult))
  • Redux#sneakers-the-rat-22-12-27 20:04:22  + (also need general [[Ruby]]also need general [[Ruby]] dev stuff, like a [[Masto Code Structure]] overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the [[Rails]] <-> [[Redux]] <-> [[React]] stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult) a declarative framework, which makes stuff difficult))
  • React#sneakers-the-rat-22-12-27 20:04:22  + (also need general [[Ruby]]also need general [[Ruby]] dev stuff, like a [[Masto Code Structure]] overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the [[Rails]] <-> [[Redux]] <-> [[React]] stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult) a declarative framework, which makes stuff difficult))
  • Discord Messages#sneakers-the-rat-22-12-27 20:04:22  + (also need general [[Ruby]]also need general [[Ruby]] dev stuff, like a [[Masto Code Structure]] overview, which I'm feeling more and more capable of doing, and I have been doing on my personal wiki and could export over. still need to figure out how to write tests but yes I think I have gotten the big chunks of how stuff works. the [[Rails]] <-> [[Redux]] <-> [[React]] stuff still sorta eludes me, esp how it's "supposed" to be done in the program because I have more experience with react and you can do a lot of uh web app stuff with it that could also be done with rails (tho a lot of their components are a) written in the old object style which I find sorta clumsy after converting to the function style and b) actually pretty imperative for a declarative framework, which makes stuff difficult) a declarative framework, which makes stuff difficult))
  • Institutional Memory#sneakers-the-rat-22-12-09 12:10:47  + (as u talk about stuff you can tag in varioas u talk about stuff you can tag in various concepts like [[Institutional Memory]] or if your working group is organized you can even tag in specific projects and Todo lists or just use it to bookmark conversations so you have an indexical/plastic memorybank alongside a fluid/streamlike mode of communication. the cscw ppl in the workshop we did a month or so ago went bananas for this lol it is goodo ago went bananas for this lol it is good)
  • Discord Messages#sneakers-the-rat-22-12-09 12:10:47  + (as u talk about stuff you can tag in varioas u talk about stuff you can tag in various concepts like [[Institutional Memory]] or if your working group is organized you can even tag in specific projects and Todo lists or just use it to bookmark conversations so you have an indexical/plastic memorybank alongside a fluid/streamlike mode of communication. the cscw ppl in the workshop we did a month or so ago went bananas for this lol it is goodo ago went bananas for this lol it is good)
  • Accessibility#sneakers-the-rat-23-01-26 03:58:14  + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
  • Discord#sneakers-the-rat-23-01-26 03:58:14  + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
  • Discord Messages#sneakers-the-rat-23-01-26 03:58:14  + (great! let me plant a bookmark on the wiki to remind me to fill in this information when I get internet at my new place & can edit it. [[Accessibility#Disabling Motion]] [[Discord#Accessibility]])
  • Trends#sneakers.the.rat-24-01-15 03:31:15  + (i can't remember where we left off w.r.t. enabling [[trends]] on the instance, i can't think of a strong reason to leave them disabled, but does anyone have feelings about this?)
  • Discord Messages#sneakers.the.rat-24-01-15 03:31:15  + (i can't remember where we left off w.r.t. enabling [[trends]] on the instance, i can't think of a strong reason to leave them disabled, but does anyone have feelings about this?)
  • Mastodon/TODO#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay ai think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
  • DIY Algorithms#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay ai think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
  • Nested Threads#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay ai think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
  • Grants#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay ai think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
  • Mastodon/Grants#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay ai think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
  • Discord Messages#sneakers-the-rat-23-02-07 04:15:02  + (i think it would be cool if we could pay ai think it would be cool if we could pay a member or two to hack on the instance!! we could take proposals on what ppl would like to see improved that guide what they are working on so we actually can resolve some of the many tiny things littering our [[Mastodon/TODO]] and maybe even one or two big things like finally doing [[DIY Algorithms]] or [[Nested Threads]] or whatnot.</br>[[Grants]] [[Mastodon/Grants]][[Mastodon/Grants]])
  • Tech WG/Ops Diary#sneakers-the-rat-23-03-30 04:49:04  + (ok [[Tech WG/Ops Diary#23-03-29]]ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13</br></br> I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....</br>It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9</br></br>wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
  • Better Code Blocks#sneakers-the-rat-23-03-30 04:49:04  + (ok [[Tech WG/Ops Diary#23-03-29]]ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13</br></br> I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....</br>It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9</br></br>wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
  • Discord Messages#sneakers-the-rat-23-03-30 04:49:04  + (ok [[Tech WG/Ops Diary#23-03-29]]ok [[Tech WG/Ops Diary#23-03-29]]: going to pull in dev branch and deploy to tha server: https://github.com/NeuromatchAcademy/mastodon/pull/13</br></br> I thought this had fetch all replies in it but i need to rebase it and also now that we know how to write them i want to write some tests....</br>It does have [[Better Code Blocks]] in it from <@485848481995423755> : https://github.com/NeuromatchAcademy/mastodon/pull/9</br></br>wish e luckm/NeuromatchAcademy/mastodon/pull/9 wish e luck)
  • Tech WG/Ops Diary#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]]ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
  • WikiBot#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]]ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
  • Discord Messages#sneakers-the-rat-23-05-20 08:29:54  + (ok [[Tech_WG/Ops_Diary#23-05-19]]ok [[Tech_WG/Ops_Diary#23-05-19]]: We conclude this evening having gotten all the way to the last stage where we pull back to main and then deploy. see preceding chat logs for history and also for the millionth time [[WikiBot#TODO]] implement archiving ranges of posts[[WikiBot#TODO]] implement archiving ranges of posts)
  • Fetch All Replies#sneakers-the-rat-22-12-26 23:33:51  + (ok here's [[Fetch All Replies]]: https://neuromatch.social/@jonny/109582537808504261)
  • Discord Messages#sneakers-the-rat-22-12-26 23:33:51  + (ok here's [[Fetch All Replies]]: https://neuromatch.social/@jonny/109582537808504261)
  • Discussions#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again anok i'd like to raise an olde idea again and that is having an instancewide [[Sticky Posts]] to supplement announcements to be able to make discussions that are intended to lead to a proposal more visible to the instance. loomio and discord merely by virtue of being separate platforms are less visible, so let's try and do a lil bridging of mediums.</br></br>here's one idea of what that might look like:</br>v1</br>- currently we have a [[Discussions]] stage in governance docs (https://wiki.neuromatch.social/Governance#Discussions) we can make that a more formal definition and say that a discussion intended to lead to a proposal is a stickied post.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... have a "minimize" button that is persistent across sessions, so once you minimize a sticky post it is hidden but still visible, I'm thinking like a 1em bar across the top of the feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
  • Hacks#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again anok i'd like to raise an olde idea again and that is having an instancewide [[Sticky Posts]] to supplement announcements to be able to make discussions that are intended to lead to a proposal more visible to the instance. loomio and discord merely by virtue of being separate platforms are less visible, so let's try and do a lil bridging of mediums.</br></br>here's one idea of what that might look like:</br>v1</br>- currently we have a [[Discussions]] stage in governance docs (https://wiki.neuromatch.social/Governance#Discussions) we can make that a more formal definition and say that a discussion intended to lead to a proposal is a stickied post.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... have a "minimize" button that is persistent across sessions, so once you minimize a sticky post it is hidden but still visible, I'm thinking like a 1em bar across the top of the feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
  • Discord Messages#sneakers.the.rat-24-01-17 10:58:31  + (ok i'd like to raise an olde idea again anok i'd like to raise an olde idea again and that is having an instancewide [[Sticky Posts]] to supplement announcements to be able to make discussions that are intended to lead to a proposal more visible to the instance. loomio and discord merely by virtue of being separate platforms are less visible, so let's try and do a lil bridging of mediums.</br></br>here's one idea of what that might look like:</br>v1</br>- currently we have a [[Discussions]] stage in governance docs (https://wiki.neuromatch.social/Governance#Discussions) we can make that a more formal definition and say that a discussion intended to lead to a proposal is a stickied post.</br>- ping a member of social wg (make sure these are up to date) or start discussion here to make a sticky post</br>- sticky posts come from an autofollowed @ discussions account</br>- ... are local only posts</br>- ... show themselves at the top of the home and local feed with a highlighted background color to offset them from the feed</br>- ... have a "minimize" button that is persistent across sessions, so once you minimize a sticky post it is hidden but still visible, I'm thinking like a 1em bar across the top of the feed</br></br>questions: </br>- can we just use browser storage to remember collapsed status rather than needing to make a new column in the statuses table for 'collapsed'</br>- should stickies have a time limit? or just a mechanism to close them in governance process?</br></br>v2</br>a) The threading interface on the web interface is awful, </br>b) it would be nice to be able to show a title on a minimized sticky post</br>c) ideally we would be able to organize discussions around topics and questions rather than chronologically in a more forumlike way</br>so</br>- posts can have titles</br>- titles are declared with a special "title" field in the web ui</br>- or with a first line beginning with a # from other clients, a la markdown</br>- replies with titles can be minimized too</br>- replies with titles are sorted first (bc they can be minimized)</br></br>[[Hacks]][[Hacks]])
  • Lessons We Gone And Learned From Maintaining A Fork Of A Fork#sneakers.the.rat-24-02-16 23:01:41  + (ok so they refactored all the css, and it ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i think</br>https://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163aceat/8e54a6bf891ff855104225032dd9ccfb0163acea)
  • Discord Messages#sneakers.the.rat-24-02-16 23:01:41  + (ok so they refactored all the css, and it ok so they refactored all the css, and it was pretty hard to track down what in the heck was changed, so here is another [[Lessons We Gone And Learned From Maintaining A Fork Of A Fork]] - patching is good, editing in place can be fragile. i moved the custom styles from better code blocks and expanded status previews to their own set of stub scss files that then get imported at the end of the scss index, so they should override conflicting rules set previously. that keeps them nice and separate and survivable in the case of big refactorings. this is similar to the "flavours" system which takes whatever isn't overridden from base masto. i can't run the dev server rn bc my brother is in town but since these are just css changes we can uh test in prod i think</br>https://github.com/NeuromatchAcademy/mastodon/commit/8e54a6bf891ff855104225032dd9ccfb0163aceat/8e54a6bf891ff855104225032dd9ccfb0163acea)