Thomas Moore

Originally a junior full-stack developer but have since transitioned into a frontend only role. At work we use Razor & Knockout for legacy code but we are moving to react for new projects.

I handled a lot of the front end tasks such as slicing sites and some back end tasks using PHP and MySQL to integrate designs into our custom CMS, Wordpress or a bespoke control panel depending on the client.

Panty & Stocking with Garterbelt: The Original Soundtrack

TCY FORCE feat. Emyli

Champion

spotify/backstage

whitecolor/yalc

https://api.github.com/repos/tomouchuu/tomo.uchuu.io/contents/{+path}

tomo.uchuu.io

Bumps [acorn](https://github.com/acornjs/acorn) from 6.4.0 to 6.4.1.
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/acornjs/acorn/commit/9a2e9b6678e243d66846b91179d650d28453e70c"><code>9a2e9b6</code></a> Mark version 6.4.1</li>
<li><a href="https://github.com/acornjs/acorn/commit/90a9548ea0ce351b54f956e2c4ed27cca9631284"><code>90a9548</code></a> More rigorously check surrogate pairs in regexp validator</li>
<li>See full diff in <a href="https://github.com/acornjs/acorn/compare/6.4.0...6.4.1">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=acorn&package-manager=npm_and_yarn&previous-version=6.4.0&new-version=6.4.1)](https://help.github.com/articles/configuring-automated-security-fixes)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/tomouchuu/tomo.uchuu.io/network/alerts).

</details>

Pull requests that update a dependency file

dependencies

Bump acorn from 6.4.0 to 6.4.1

tomouchuu/tomo.uchuu.io

Done in e653a5ca921379f532ab5b00c4cfa00bcddc5b71

[//]: # (dependabot-start)
⚠️  **Dependabot is rebasing this PR** ⚠️ 

If you make any changes to it yourself then they will take precedence over the rebase.

---

[//]: # (dependabot-end)

Bumps [next](https://github.com/zeit/next.js) from 9.1.6 to 9.3.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/zeit/next.js/releases">next's releases</a>.</em></p>
<blockquote>
<h2>v9.3.2</h2>
<p><strong>This upgrade is <em>completely backwards compatible and recommended for all users on versions below 9.3.2.</em> For future security related communications of our OSS projects, please <a href="https://zeit.co/security">join this mailing list</a>.</strong></p>
<p>Next.js has just been audited by one of the top security firms in the world.</p>
<p>They found that attackers could craft special requests to access files in the dist directory (<code>.next</code>).</p>
<p><strong>This does not affect files outside of the dist directory (<code>.next</code>).</strong></p>
<p>In general, the dist directory only holds build assets unless your application intentionally stores other assets under this directory.</p>
<p>We recommend upgrading to the latest version of Next.js to improve the overall security of your application.</p>
<h2>How to Upgrade</h2>
<ul>
<li>We have released patch versions for both the stable and canary channels of Next.js.</li>
<li>To upgrade run <code>npm install next@latest --save</code></li>
</ul>
<h2>Impact</h2>
<ul>
<li><strong>Not affected</strong>: Deployments on ZEIT Now v2 (<a href="https://zeit.co/">https://zeit.co</a>) are not affected</li>
<li><strong>Not affected</strong>: Deployments using the <code>serverless</code> target</li>
<li><strong>Not affected</strong>: Deployments using <code>next export</code></li>
<li><strong>Affected</strong>: Users of Next.js below 9.3.2 that use <code>next start</code></li>
</ul>
<p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p>
<h3>How to Assess Impact</h3>
<p>If you think sensitive code or data could have been exposed, you can filter logs of affected sites by <code>../</code> with a 200 response.</p>
<h2>What is Being Done</h2>
<p>As Next.js has grown in popularity, it has received the attention of security researchers and auditors. We are thankful to Luca Carettoni from Doyensec for their investigation and discovery of the original bug and subsequent responsible disclosure.</p>
<p>We've landed a patch that ensures only known filesystem paths of <code>.next/static</code> are made available under <code>/_next/static</code>.
Regression tests for this attack were added to the <a href="https://github.com/zeit/next.js/blob/canary/test/integration/production/test/security.js">security</a> integration test suite.</p>
<ul>
<li>We have notified known Next.js users in advance of this publication.</li>
<li>A public CVE was issued.</li>
<li>If you want to stay on top of our security related news impacting Next.js or other ZEIT projects, please <a href="https://zeit.co/security">join this mailing list</a>.</li>
<li>We encourage responsible disclosure of future issues. Please email us at <strong><a href="https://github.com/zeit/next.js/blob/HEAD/mailto:security@zeit.co">security@zeit.co</a></strong>. We are actively monitoring this mailbox.</li>
</ul>
<hr />
<h3>Patches</h3>
<ul>
<li>Add Numeric Separator Support for TypeScript: <a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11308">#11308</a></li>
<li>Update CLI custom config documentation link: <a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11152">#11152</a></li>
<li>Add error when attempting to export GSSP page: <a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11154">#11154</a></li>
</ul>
</tr></table> ... (truncated)
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/zeit/next.js/commit/ee0081356d7ea166dfed4765f134730c11ecaecf"><code>ee00813</code></a> v9.3.2</li>
<li><a href="https://github.com/zeit/next.js/commit/dd4cee724590892ff4939f7682601c867dc23537"><code>dd4cee7</code></a> v9.3.2-canary.9</li>
<li><a href="https://github.com/zeit/next.js/commit/e02b66a52c0a9bb837845e6ec4e6356b3ee1697f"><code>e02b66a</code></a> Add with-redux-toolkit example (<a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11358">#11358</a>)</li>
<li><a href="https://github.com/zeit/next.js/commit/044ddf44216f848a0a6641e2471eb67dffc71f93"><code>044ddf4</code></a> [Example] Use .jpg for images in blog-starter (<a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11176">#11176</a>)</li>
<li><a href="https://github.com/zeit/next.js/commit/ee249ee6cd3c7987496e256b7fdd9db171c821d7"><code>ee249ee</code></a> v9.3.2-canary.8</li>
<li><a href="https://github.com/zeit/next.js/commit/1d6ffc39f7b2da55aec02da8dc53a24eab8a6c5d"><code>1d6ffc3</code></a> Fix <code>static/</code> file name encoding (<a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11373">#11373</a>)</li>
<li><a href="https://github.com/zeit/next.js/commit/e83cd4aa967e8b49ff32f9fe12713d9dd436a2dd"><code>e83cd4a</code></a> v9.3.2-canary.7</li>
<li><a href="https://github.com/zeit/next.js/commit/d8155b22ffbd2e64ca1aca6a7a843481a4f1c913"><code>d8155b2</code></a> Add initial support for new env handling (<a href="https://github-redirect.dependabot.com/zeit/next.js/issues/10525">#10525</a>)</li>
<li><a href="https://github.com/zeit/next.js/commit/a391d328ae5606282d99513c6330d78512d2e203"><code>a391d32</code></a> Add docs for multi zones (<a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11348">#11348</a>)</li>
<li><a href="https://github.com/zeit/next.js/commit/4801dcdd15132f485f2701101e4c2ee77b8666c3"><code>4801dcd</code></a> Update AMP docs (<a href="https://github-redirect.dependabot.com/zeit/next.js/issues/11353">#11353</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/zeit/next.js/compare/v9.1.6...v9.3.2">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=next&package-manager=npm_and_yarn&previous-version=9.1.6&new-version=9.3.2)](https://help.github.com/articles/configuring-automated-security-fixes)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/tomouchuu/tomo.uchuu.io/network/alerts).

</details>

Bump next from 9.1.6 to 9.3.2

manojVivek/responsively-app

ijjk/notion-blog

Hey @guysoft, not really I'm afraid as I don't really use mastodon anymore (especially since the instance I was on closed). You're more than welcome to fork and submit PRs as I'm active enough to approve them here / give collaboration or if it's just easier to fork and maintain separately then that's cool too.

Is this maintained?
Asking to understand if its worth helping fixing it.

Is this maintained?

tomouchuu/mastodon-translate

There is currently some content that I remove as was hidden under the chat window. It would be nice if we could resurface this under the chat window

Move the channel details under the chat

tomouchuu/vertical-twitch

Occasionally the chat window will be too big for the window so it needs to work out how much it can specifically expand to

Better handle chat height

Moves chat below the video on vertical/potrait screens

WebDeveloper. EU @yamato__ao TO / 一番好き@sayuri_ppppphm / @yui_ppppphm❤️ / PPPPPHM, Nijicon & Dempagumi / Drumming / DisneyParks / FFXIV (Tomo Uchuu@Omega) / よろしく

thomas

Anyway raiding with static tomorrow, not sure if we'll be doing our reclears or giving the EX version of the trial a go. Before that hope to get the "weapon" duty done and really want to buy the new suzaku bow since it's so on brand with the suzaku minion &amp; songboy feeling