BreadTopia
Archives / breads-webhook-old
Original category: archive
Floof™ errors BOT 16/02/2022 2:09 PM
An error occurred in timeout command: `Traceback (most recent call last): File "/home/container/.local/lib/python3.9/site-packages/discord/ext/commands/core.py", line 220, in wrapped ret = await coro(*args, **kwargs) File "/home/container/cogs/mod.py", line 68, in timeout until = discord.utils.utcnow() + datetime.timedelta(seconds=times[option]) NameError: name 'times' is not defined The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/container/.local/lib/python3.9/site-packages/discord/ext/commands/bot.py", line 1215, in invoke await ctx.command.invoke(ctx) File "/home/container/.local/lib/python3.9/site-packages/discord/ext/commands/core.py", line 998, in invoke await injected(*ctx.args, **ctx.kwargs) File "/home/container/.local/lib/python3.9/site-packages/discord/ext/commands/core.py", line 229, in wrapped raise CommandInvokeError(exc) from exc discord.ext.commands.errors.CommandInvokeError: Command raised an exception: NameError: name 'times' is not defined`
HetrixTools BOT 28/02/2022 1:32 AM
This is a test notification.
Nishi-Breadotron eki 28/02/2022 1:33 AM
ok that works
HetrixTools BOT 1/03/2022 10:28 AM
Main Website is now DOWN Target: breadtm.xyz Noticed at: 2022-02-28 23:28:34 (UTC 00:00) Encountered errors: New York: HTTP code 521 London: HTTP code 200 Singapore: HTTP code 521 Mumbai: HTTP code 521
10:29 AM
Main Website is now UP Downtime: 1 min Target: breadtm.xyz Noticed at: 2022-02-28 23:29:34 (UTC 00:00)
Nishi-Breadotron eki 1/03/2022 10:40 AM
Hmm
HetrixTools BOT 1/03/2022 11:46 AM
Google Sites is now DOWN Target: test.breadtm.xyz Noticed at: 2022-03-01 00:46:46 (UTC 00:00) Encountered errors: New York: Timeout (10 sec) London: Timeout (10 sec) Singapore: Timeout (10 sec) Mumbai: Timeout (10 sec)
11:47 AM
Google Sites is now UP Downtime: 1 min Target: test.breadtm.xyz Noticed at: 2022-03-01 00:47:43 (UTC 00:00)
Nishi-Breadotron eki 1/03/2022 11:48 AM
Fuck
11:48 AM
What timeout
11:48 AM
Cloudflare you didn't mistake my uptime monitor as threat right?
11:50 AM
11:51 AM
No more 100%, so sad
Nishi-Breadotron eki
Fuck
Toaster™ 1/03/2022 11:53 AM
what
Toaster™
what
Nishi-Breadotron eki 1/03/2022 11:53 AM
Scroll up
11:53 AM
And down
Nishi-Breadotron eki
Scroll up
Toaster™ 1/03/2022 11:54 AM
Nishi-Breadotron eki
Toaster™ 1/03/2022 11:54 AM
BRUH LMAO
HetrixTools BOT 1/03/2022 11:30 PM
Main Website is now DOWN Target: breadtm.xyz Noticed at: 2022-03-01 12:30:34 (UTC 00:00) Encountered errors: New York: HTTP code 521 London: HTTP code 521 Singapore: HTTP code 521 Mumbai: HTTP code 521
HetrixTools
Click to see attachment 🖼️
Nishi-Breadotron eki 1/03/2022 11:30 PM
️
HetrixTools BOT 1/03/2022 11:31 PM
Main Website is now UP Downtime: 1 min Target: breadtm.xyz Noticed at: 2022-03-01 12:31:34 (UTC 00:00)
Nishi-Breadotron eki 1/03/2022 11:31 PM
Lol
HetrixTools BOT 2/03/2022 12:13 AM
Google Sites is now DOWN Target: test.breadtm.xyz Noticed at: 2022-03-01 13:13:32 (UTC 00:00) Encountered errors: New York: HTTP code 200 London: HTTP code 429 Singapore: HTTP code 429 Mumbai: HTTP code 429
Nishi-Breadotron eki 2/03/2022 12:14 AM
FUCK
GitHub BOT 7/03/2022 8:46 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`4e4421b` projects: prepublish - ItsBreadTime
GitHub BOT 8/03/2022 12:00 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`678d555` added 404 page - ItsBreadTime
GitHub BOT 8/03/2022 6:27 PM
[breadtm.xyz] Cloudflare Pages checks success on main
6:27 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 678d555 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://771c3079.breadtm-xyz.pages.dev View logs
GitHub
Click to see attachment 🖼️
Nishi-Breadotron eki 8/03/2022 6:29 PM
6:29 PM
no wae
GitHub BOT 8/03/2022 9:01 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Now open sourced!
9:02 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`5ea23b3` Create CNAME - ItsBreadTime
9:02 PM
[breadtm.xyz] Cloudflare Pages checks success on 5ea23b3
9:02 PM
[breadtm.xyz] Deployed successfully on 5ea23b3
Latest commit: 5ea23b3 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://077ec618.breadtm-xyz.pages.dev View logs
9:02 PM
[breadtm.xyz] build on main
There are 1 failures, 0 warnings, and 0 notices.
9:02 PM
[breadtm.xyz] deploy skipped on main
9:02 PM
[breadtm.xyz] build success on main
9:03 PM
[breadtm.xyz] deploy success on main
9:03 PM
[breadtm.xyz] GitHub Actions checks success on main
9:06 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`a0fa022` Delete CNAME - ItsBreadTime
9:06 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: a0fa022 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b30ded39.breadtm-xyz.pages.dev View logs
9:06 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:07 PM
[breadtm.xyz] build success on main
9:07 PM
[breadtm.xyz] deploy on main
There are 2 failures, 0 warnings, and 0 notices.
9:07 PM
[breadtm.xyz] GitHub Actions checks failure on main
GitHub
Click to see attachment 🖼️
GnorpSylver 8/03/2022 9:08 PM
Imagine being closed source
9:08 PM
Now I can steal your site's source code
GnorpSylver
Imagine being closed source
Nishi-Breadotron eki 8/03/2022 9:08 PM
️
GitHub BOT 8/03/2022 9:09 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`d221880` Update .gitignore - ItsBreadTime
9:09 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: d221880 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://86dd1ae9.breadtm-xyz.pages.dev View logs
9:09 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:10 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`d3c4657` Delete node_modules directory - ItsBreadTime
9:10 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:10 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: d3c4657 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://8fc31e9b.breadtm-xyz.pages.dev View logs
9:10 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`aced1f4` Delete forms directory - ItsBreadTime
9:10 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: aced1f4 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://ed8fe41c.breadtm-xyz.pages.dev View logs
9:10 PM
[breadtm.xyz] Cloudflare Pages checks success on main
Nishi-Breadotron eki 8/03/2022 9:10 PM
oml
9:11 PM
ok paused
GitHub BOT 8/03/2022 9:11 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`1aa5df8` Delete Readme.txt - ItsBreadTime
9:11 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`242c2f4` Delete portfolio-details.html - ItsBreadTime
9:12 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`d1939d8` Delete inner-page.html - ItsBreadTime
9:12 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`6fd1aa0` Delete blog-single.html - ItsBreadTime
9:12 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`0301833` Delete blog.html - ItsBreadTime
9:12 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`766d234` Delete changelog.txt - ItsBreadTime
9:13 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`1c73567` Delete package-lock.json - ItsBreadTime
9:13 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`5f880ce` Delete package.json - ItsBreadTime
9:13 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Now open sourced!
9:18 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`72c719d` Create codeql-analysis.yml - ItsBreadTime
9:18 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 72c719d Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b5a3afd9.breadtm-xyz.pages.dev View logs
9:18 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:19 PM
[breadtm.xyz] Analyze (javascript) success on main
9:19 PM
[breadtm.xyz] GitHub Actions checks success on main
9:20 PM
[breadtm.xyz] build success on main
9:20 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:20 PM
[breadtm.xyz] GitHub Actions checks failure on main
9:20 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`5a24b58` Create CNAME - ItsBreadTime
9:20 PM
[breadtm.xyz] Deployed successfully on 5a24b58
Latest commit: 5a24b58 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://6bbfceac.breadtm-xyz.pages.dev View logs
9:20 PM
[breadtm.xyz] Cloudflare Pages checks success on 5a24b58
9:21 PM
[breadtm.xyz] build success on main
9:21 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:21 PM
[breadtm.xyz] GitHub Actions checks failure on main
9:22 PM
[breadtm.xyz] Analyze (javascript) success on main
9:22 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub
Click to see attachment 🖼️
Nishi-Breadotron eki 8/03/2022 9:24 PM
why
GitHub BOT 8/03/2022 9:37 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`9938f49` Update CNAME - ItsBreadTime
9:37 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`28b45bf` Delete CNAME - ItsBreadTime
9:37 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`dbd3014` Create CNAME - ItsBreadTime
9:37 PM
[breadtm.xyz] Cloudflare Pages checks success on 9938f49
9:37 PM
[breadtm.xyz] Deployed successfully on 9938f49
Latest commit: 9938f49 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://400350c6.breadtm-xyz.pages.dev View logs
9:37 PM
[breadtm.xyz] Deployed successfully on 28b45bf
Latest commit: 28b45bf Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://297075da.breadtm-xyz.pages.dev View logs
9:37 PM
[breadtm.xyz] Cloudflare Pages checks success on 28b45bf
9:38 PM
[breadtm.xyz] GitHub Actions checks cancelled on main
9:38 PM
[breadtm.xyz] GitHub Actions checks cancelled on main
9:38 PM
[breadtm.xyz] Cloudflare Pages checks success on dbd3014
9:38 PM
[breadtm.xyz] build success on main
9:38 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:38 PM
[breadtm.xyz] GitHub Actions checks failure on main
9:39 PM
[breadtm.xyz] Analyze (javascript) success on main
9:39 PM
[breadtm.xyz] GitHub Actions checks success on main
9:39 PM
[breadtm.xyz] Analyze (javascript) success on main
9:39 PM
[breadtm.xyz] GitHub Actions checks success on main
9:39 PM
[breadtm.xyz] Analyze (javascript) success on main
9:39 PM
[breadtm.xyz] GitHub Actions checks success on main
9:46 PM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`0d2e9ab` Create Readme.md - ItsBreadTime `a539da6` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
9:46 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:46 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: a539da6 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://34acb513.breadtm-xyz.pages.dev View logs
9:46 PM
[breadtm.xyz] build success on main
9:46 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:46 PM
[breadtm.xyz] GitHub Actions checks failure on main
9:47 PM
[breadtm.xyz] Analyze (javascript) success on main
9:47 PM
[breadtm.xyz] GitHub Actions checks success on main
9:49 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`8ca13b4` Update and rename Readme.md to README.md - ItsBreadTime
9:49 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:49 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 8ca13b4 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://11bcb201.breadtm-xyz.pages.dev View logs
9:50 PM
[breadtm.xyz] build success on main
9:50 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:50 PM
[breadtm.xyz] GitHub Actions checks failure on main
9:52 PM
[breadtm.xyz] Analyze (javascript) success on main
9:52 PM
[breadtm.xyz] GitHub Actions checks success on main
9:53 PM
[breadtm.xyz] build failure on main
9:53 PM
[breadtm.xyz] deploy on main
There are 1 failures, 0 warnings, and 0 notices.
9:53 PM
[breadtm.xyz] GitHub Actions checks cancelled on main
9:54 PM
[breadtm.xyz] build success on main
9:54 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:54 PM
[breadtm.xyz] GitHub Actions checks failure on main
Nishi-Breadotron eki 8/03/2022 9:57 PM
when will it passsss
GitHub BOT 8/03/2022 9:58 PM
[breadtm.xyz] build success on main
9:58 PM
[breadtm.xyz] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
9:58 PM
[breadtm.xyz] GitHub Actions checks failure on main
Nishi-Breadotron eki 8/03/2022 9:58 PM
ffffuck
GitHub BOT 8/03/2022 10:00 PM
[my-website] build success on main
10:00 PM
[my-website] deploy on main
There are 2 failures, 1 warnings, and 0 notices.
10:00 PM
[my-website] GitHub Actions checks failure on main
Nishi-Breadotron eki
when will it passsss
GnorpSylver 8/03/2022 10:07 PM
Neverr
Nishi-Breadotron eki 8/03/2022 10:07 PM
GitHub BOT 8/03/2022 10:10 PM
[itsbreadtime.github.io] build success on main
10:10 PM
[itsbreadtime.github.io] deploy success on main
10:10 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
Nishi-Breadotron eki 8/03/2022 10:10 PM
NO WAY
10:10 PM
im stupid
10:10 PM
i have to change the repo name (edited)
10:10 PM
lmao
GnorpSylver 8/03/2022 10:11 PM
Lmao
GitHub BOT 8/03/2022 10:12 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`b7cc042` Update README.md - ItsBreadTime
10:13 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
10:13 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: b7cc042 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://96989d01.breadtm-xyz.pages.dev View logs
10:13 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`8db0445` Update README.md - ItsBreadTime
10:13 PM
[itsbreadtime.github.io] build on main
There are 2 failures, 0 warnings, and 0 notices.
10:13 PM
[itsbreadtime.github.io] deploy skipped on main
10:13 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 8db0445 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://d7678004.breadtm-xyz.pages.dev View logs
10:13 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
10:13 PM
[itsbreadtime.github.io] build success on main
10:14 PM
[itsbreadtime.github.io] deploy success on main
10:14 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:14 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
10:14 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:14 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
10:14 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:19 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`97f38f8` Change "hi there" to "hey there" - ItsBreadTime
10:19 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 97f38f8 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://964f742b.breadtm-xyz.pages.dev View logs
10:19 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
10:20 PM
[itsbreadtime.github.io] build success on main
10:20 PM
[itsbreadtime.github.io] deploy success on main
10:20 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
Nishi-Breadotron eki 8/03/2022 10:21 PM
Why tf is cloudflare page so much faster than GitHub page
GitHub BOT 8/03/2022 10:21 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
10:21 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
Nishi-Breadotron eki 8/03/2022 10:21 PM
and why would i use github page if i already have cloudflare page…
10:22 PM
i don’t understand myself
GitHub BOT 8/03/2022 10:38 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`7e962ec` Create greetings.yml - ItsBreadTime
10:38 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
10:38 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 7e962ec Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://a0695559.breadtm-xyz.pages.dev View logs
10:38 PM
[itsbreadtime.github.io] build success on main
10:38 PM
[itsbreadtime.github.io] deploy success on main
10:38 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:39 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
10:39 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:41 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`bfbc1f5` Create label.yml - ItsBreadTime
10:41 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: bfbc1f5 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://09c19b82.breadtm-xyz.pages.dev View logs
10:41 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
10:42 PM
[itsbreadtime.github.io] build success on main
10:42 PM
[itsbreadtime.github.io] deploy success on main
10:42 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:42 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`cea7820` Create stale.yml - ItsBreadTime
10:43 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
10:43 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:43 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
10:43 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: cea7820 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://86f389f1.breadtm-xyz.pages.dev View logs
10:43 PM
[itsbreadtime.github.io] build success on main
Nishi-Breadotron eki 8/03/2022 10:43 PM
github sending fuck ton of embed lol
GitHub BOT 8/03/2022 10:43 PM
[itsbreadtime.github.io] deploy success on main
10:43 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:44 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
10:44 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
GitHub BOT 8/03/2022 11:05 PM
Agent-Paws
[ItsBreadTime/itsbreadtime.github.io] Fork created: Agent-Paws/itsbreadtime.github.io
GnorpSylver 8/03/2022 11:06 PM
@Nishi-Breadotron eki
GnorpSylver
@Nishi-Breadotron eki
Nishi-Breadotron eki 8/03/2022 11:06 PM
GnorpSylver 8/03/2022 11:06 PM
I stol the code
GitHub BOT 8/03/2022 11:09 PM
itsbreadfun
[ItsBreadTime/itsbreadtime.github.io] Fork created: itsbreadfun/itsbreadtime.github.io
GitHub BOT 9/03/2022 1:35 AM
ItsBreadTime
[itsbreadtime.github.io:main] 2 new commits
`78913dc` replace promise with project in navbar - ItsBreadTime `9313c4c` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
1:35 AM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 9313c4c Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://823bb009.breadtm-xyz.pages.dev View logs
1:35 AM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
Nishi-Breadotron eki 9/03/2022 1:35 AM
wow thats fast
GitHub BOT 9/03/2022 1:35 AM
[itsbreadtime.github.io] build success on main
1:36 AM
[itsbreadtime.github.io] deploy success on main
1:36 AM
[itsbreadtime.github.io] GitHub Actions checks success on main
1:36 AM
[itsbreadtime.github.io] Analyze (javascript) success on main
1:36 AM
[itsbreadtime.github.io] GitHub Actions checks success on main
GitHub BOT 9/03/2022 2:24 AM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`b03a230` updated 404 page - ItsBreadTime
2:24 AM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
2:24 AM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: b03a230 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://5e270ddc.breadtm-xyz.pages.dev View logs
2:24 AM
[itsbreadtime.github.io] build success on main
2:24 AM
[itsbreadtime.github.io] deploy success on main
2:24 AM
[itsbreadtime.github.io] GitHub Actions checks success on main
Nishi-Breadotron eki 9/03/2022 2:25 AM
:D
GitHub BOT 9/03/2022 2:26 AM
[itsbreadtime.github.io] Analyze (javascript) success on main
2:26 AM
[itsbreadtime.github.io] GitHub Actions checks success on main
GitHub BOT 9/03/2022 2:51 AM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`3ff0d2e` added viewport tag - ItsBreadTime
2:52 AM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 3ff0d2e Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://68da8661.breadtm-xyz.pages.dev View logs
2:52 AM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
2:52 AM
[itsbreadtime.github.io] build success on main
2:52 AM
[itsbreadtime.github.io] deploy success on main
2:52 AM
[itsbreadtime.github.io] GitHub Actions checks success on main
2:53 AM
[itsbreadtime.github.io] Analyze (javascript) success on main
2:53 AM
[itsbreadtime.github.io] GitHub Actions checks success on main
Nishi-Breadotron eki
:D
GnorpSylver 9/03/2022 9:42 AM
Is that a custom 404 page or CloudFlare one (edited)
GitHub BOT 9/03/2022 12:08 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`a0b0e63` Delete CNAME - ItsBreadTime
12:09 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: a0b0e63 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://bc28bf7a.breadtm-xyz.pages.dev View logs
12:09 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
12:09 PM
[itsbreadtime.github.io] build success on main
12:09 PM
[itsbreadtime.github.io] deploy success on main
12:09 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
12:10 PM
ItsBreadTime
[itsbreadtime.github.io:main] 1 new commit
`67aa9db` Edit readme.md - ItsBreadTime
12:10 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
12:10 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
12:10 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 67aa9db Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://4199c61c.breadtm-xyz.pages.dev View logs
12:10 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
12:11 PM
[itsbreadtime.github.io] build success on main
12:11 PM
ItsBreadTime
[ItsBreadTime/itsbreadtime.github.io] New branch created: index
12:11 PM
[itsbreadtime.github.io] deploy success on main
12:11 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
12:11 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 67aa9db Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://2614e37b.breadtm-xyz.pages.dev View logs
12:12 PM
ItsBreadTime
[ItsBreadTime/itsbreadtime.github.io] New branch created: mainaaaaaa
12:12 PM
ItsBreadTime
[ItsBreadTime/itsbreadtime.github.io] branch deleted: main
12:12 PM
[itsbreadtime.github.io] Analyze (javascript) success on main
12:12 PM
[itsbreadtime.github.io] GitHub Actions checks success on main
12:12 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 67aa9db Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://87f0eed7.breadtm-xyz.pages.dev View logs
12:15 PM
ItsBreadTime
[ItsBreadTime/itsbreadtime.github.io] New branch created: main
12:15 PM
ItsBreadTime
[ItsBreadTime/itsbreadtime.github.io] branch deleted: mainaaaaaa
12:15 PM
[itsbreadtime.github.io] Cloudflare Pages checks success on main
12:15 PM
[itsbreadtime.github.io] Deployed successfully on main
Latest commit: 67aa9db Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://e5764e49.breadtm-xyz.pages.dev View logs
12:16 PM
[breadtm.xyz] build success on main
12:16 PM
[breadtm.xyz] deploy success on main
12:16 PM
[breadtm.xyz] GitHub Actions checks success on main
12:17 PM
[breadtm.xyz] Analyze (javascript) success on main
12:17 PM
[breadtm.xyz] GitHub Actions checks success on main
12:18 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`ff7a44c` Delete stale.yml - ItsBreadTime
12:18 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:18 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: ff7a44c Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://2aaacc42.breadtm-xyz.pages.dev View logs
12:18 PM
ItsBreadTime
[breadtm.xyz:ItsBreadTime-patch-1] 1 new commit
`301bcd5` Delete label.yml - ItsBreadTime
12:18 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: ItsBreadTime-patch-1
12:18 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #1 Delete label.yml
12:18 PM
[breadtm.xyz] Cloudflare Pages checks success on pull request #1
12:18 PM
[breadtm.xyz] Deployed successfully on pull request #1
Latest commit: 301bcd5 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://e8e34b7c.breadtm-xyz.pages.dev View logs
12:18 PM
cloudflare-pages[bot]
[ItsBreadTime/breadtm.xyz] New comment on pull request #1: Delete label.yml

## Deploying with &nbsp;<a href="https://pages.dev"><img alt="Cloudflare Pages" src="https://user-images.githubusercontent.com/23264/106598434-9e719e00-654f-11eb-9e59-6167043cfa01.png" width="16"></a> &nbsp;Cloudflare Pages

<table><tr><td><strong>Latest commit:</strong> </td><td> <code>301bcd5</code> </td></tr> <tr><td><strong>Status:</strong></td><td>&nbsp;✅&nbsp; Deploy successful!</td></tr> <tr><td><strong>Preview URL:</strong></td><td> <a href='https://e8e34b7c.breadtm-xyz.pages.dev'>htt...
12:18 PM
ItsBreadTime
[breadtm.xyz:ItsBreadTime-patch-1-1] 1 new commit
`aff8ec3` Delete greetings.yml - ItsBreadTime
12:18 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: ItsBreadTime-patch-1-1
12:19 PM
[breadtm.xyz] Cloudflare Pages checks success on ItsBreadTime-patch-1-1
12:19 PM
[breadtm.xyz] Deployed successfully on ItsBreadTime-patch-1-1
Latest commit: aff8ec3 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://370a5930.breadtm-xyz.pages.dev View logs
12:19 PM
github-actions[bot]
[ItsBreadTime/breadtm.xyz] Pull request review submitted: #1 Delete label.yml
Thanks for creating a pull request for my personal website :D
12:19 PM
[breadtm.xyz] greeting success on pull request #1
12:19 PM
[breadtm.xyz] GitHub Actions checks success on pull request #1
12:19 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #1 Delete label.yml
12:19 PM
[breadtm.xyz] Analyze (javascript) success on main
12:19 PM
[breadtm.xyz] GitHub Actions checks success on main
12:20 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`88f9989` Delete greetings.yml - ItsBreadTime
12:20 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`8838fb7` Delete label.yml - ItsBreadTime
12:20 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 88f9989 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://42879eae.breadtm-xyz.pages.dev View logs
12:20 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:20 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:20 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 8838fb7 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://040b5cf4.breadtm-xyz.pages.dev View logs
12:20 PM
[breadtm.xyz] No new or fixed alerts on ItsBreadTime-patch-1
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/1/merge` (commit a50b470e546b1be15468f5a6592dbd631d53cc99) and `refs/heads/ItsBreadTime-patch-1` (commit 301bcd5fcff49d9c711232acd8bd3579cbec3703). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:jav...
12:20 PM
[breadtm.xyz] GitHub Code Scanning checks success on ItsBreadTime-patch-1
12:20 PM
[breadtm.xyz] Analyze (javascript) success on ItsBreadTime-patch-1
12:20 PM
[breadtm.xyz] GitHub Actions checks success on ItsBreadTime-patch-1
12:21 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #2 Delete greetings.yml
12:21 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #2 Delete greetings.yml
12:21 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] branch deleted: ItsBreadTime-patch-1-1
12:21 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] branch deleted: ItsBreadTime-patch-1
12:21 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] branch deleted: index
12:21 PM
[breadtm.xyz] Analyze (javascript) success on main
12:21 PM
[breadtm.xyz] GitHub Actions checks success on main
12:23 PM
[breadtm.xyz] Analyze (javascript) success on ItsBreadTime-patch-1-1
12:23 PM
[breadtm.xyz] GitHub Actions checks success on ItsBreadTime-patch-1-1
12:23 PM
[breadtm.xyz] GitHub Code Scanning checks success on ItsBreadTime-patch-1-1
12:23 PM
[breadtm.xyz] No new or fixed alerts on ItsBreadTime-patch-1-1
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/2/merge` (commit 35cef3d76956cde098c25cd3c85b38f44eba0aea) and `refs/heads/ItsBreadTime-patch-1-1` (commit aff8ec32f03631b3925ed8e2e6955d89046c89d6). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:j...
GitHub BOT 9/03/2022 2:37 PM
ItsBreadTime
[breadtm.xyz:main] 3 new commits
`03a89ba` move 404 path to asset directory - ItsBreadTime `ac48463` Delete stale.yml - ItsBreadTime `a4c588d` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
2:38 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: a4c588d Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://6878a908.breadtm-xyz.pages.dev View logs
2:38 PM
[breadtm.xyz] Cloudflare Pages checks success on main
2:39 PM
[breadtm.xyz] Analyze (javascript) success on main
2:39 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 9/03/2022 9:19 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`b48f9aa` Create jekyll.yml - ItsBreadTime
9:19 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:19 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: b48f9aa Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://63aa0096.breadtm-xyz.pages.dev View logs
9:19 PM
[breadtm.xyz] build success on main
9:20 PM
[breadtm.xyz] GitHub Actions checks success on main
9:20 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`87393a3` Delete jekyll.yml - ItsBreadTime
9:21 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:21 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 87393a3 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://97592116.breadtm-xyz.pages.dev View logs
9:21 PM
[breadtm.xyz] Analyze (javascript) success on main
9:21 PM
[breadtm.xyz] GitHub Actions checks success on main
9:22 PM
[breadtm.xyz] Analyze (javascript) success on main
9:22 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 9/03/2022 10:38 PM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`9a9916c` github button, replace about pic with my selfie - ItsBreadTime `b88f412` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
10:38 PM
[breadtm.xyz] Cloudflare Pages checks success on main
10:38 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: b88f412 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://e071204a.breadtm-xyz.pages.dev View logs
10:40 PM
[breadtm.xyz] Analyze (javascript) success on main
10:40 PM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki 9/03/2022 10:47 PM
Chrome is caching shit again The color won't change (edited)
Nishi-Breadotron eki
Chrome is caching shit again The color won't change (edited)
Deleted User 9/03/2022 11:00 PM
oof
GitHub BOT 9/03/2022 11:25 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`57514dd` clean up image assets, converting to webp - ItsBreadTime
11:25 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:25 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 57514dd Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://3f373ea3.breadtm-xyz.pages.dev View logs
11:27 PM
[breadtm.xyz] Analyze (javascript) success on main
11:27 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 9/03/2022 11:44 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`4cd7b44` resize image, remove unnecessary js - ItsBreadTime
11:44 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 4cd7b44 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://9943cee1.breadtm-xyz.pages.dev View logs
11:44 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:46 PM
[breadtm.xyz] Analyze (javascript) success on main
11:46 PM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki
Chrome is caching shit again The color won't change (edited)
GnorpSylver 10/03/2022 6:22 AM
Imagine not using Firefox and telling it to delete your browsing history and cache on exit :P
GnorpSylver
Imagine not using Firefox and telling it to delete your browsing history and cache on exit :P
Nishi-Breadotron eki 10/03/2022 12:44 PM
okay
GnorpSylver 10/03/2022 12:45 PM
I didn't expect that
Nishi-Breadotron eki 10/03/2022 12:46 PM
tf happened to the image
GnorpSylver 10/03/2022 12:47 PM
AAAAAAAA
12:47 PM
image dead
GitHub BOT 10/03/2022 12:50 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`ea33133` convert svg to webp to hopefully display properly - ItsBreadTime
Nishi-Breadotron eki 10/03/2022 12:51 PM
hopefully it works
GitHub BOT 10/03/2022 12:51 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:51 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: ea33133 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b6d74305.breadtm-xyz.pages.dev View logs
GnorpSylver 10/03/2022 12:51 PM
ooh
12:51 PM
New button :P
12:51 PM
GitHub BOT 10/03/2022 12:52 PM
[breadtm.xyz] Analyze (javascript) success on main
12:52 PM
[breadtm.xyz] GitHub Actions checks success on main
GnorpSylver 10/03/2022 12:52 PM
Image
12:53 PM
Don't trust me my network is bad
Nishi-Breadotron eki 10/03/2022 12:53 PM
smh
Nishi-Breadotron eki
okay
Nishi-Breadotron eki 10/03/2022 12:53 PM
done
12:53 PM
its still the svg version
12:53 PM
smh
GnorpSylver 10/03/2022 12:54 PM
Just wait
Nishi-Breadotron eki
tf happened to the image
Deleted User 10/03/2022 12:54 PM
rip image (edited)
Nishi-Breadotron eki 10/03/2022 12:55 PM
oops i actually fuck up
12:56 PM
by not using safe delete and replacing the image in the code
12:56 PM
im stoopid
Deleted User 10/03/2022 12:56 PM
as hell
Nishi-Breadotron eki 10/03/2022 12:56 PM
mmmm rainbow
Deleted User
as hell
Nishi-Breadotron eki 10/03/2022 12:57 PM
Nishi-Breadotron eki
Deleted User 10/03/2022 12:58 PM
Okay okay not sorry
GitHub BOT 10/03/2022 12:58 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`bfd12d3` fixes previous commit - ItsBreadTime
Deleted User
Okay okay not sorry
Nishi-Breadotron eki 10/03/2022 12:58 PM
GitHub BOT 10/03/2022 12:58 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: bfd12d3 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://c0c6c381.breadtm-xyz.pages.dev View logs
12:58 PM
[breadtm.xyz] Cloudflare Pages checks success on main
Nishi-Breadotron eki 10/03/2022 12:59 PM
okay
Deleted User 10/03/2022 1:00 PM
and i forgot to charge my laptop AAAAA
GitHub BOT 10/03/2022 1:00 PM
[breadtm.xyz] Analyze (javascript) success on main
1:00 PM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki
Deleted User 10/03/2022 1:03 PM
Yeah im sorry
GitHub BOT 10/03/2022 1:30 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`d30bc10` Update index.html - ItsBreadTime
1:30 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:30 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: d30bc10 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://adb6d4c4.breadtm-xyz.pages.dev View logs
1:31 PM
[breadtm.xyz] Analyze (javascript) success on main
1:31 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 10/03/2022 6:28 PM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`769e170` remove some unused css - ItsBreadTime `40afeef` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
6:28 PM
[breadtm.xyz] Cloudflare Pages checks success on main
6:28 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 40afeef Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://e0e3034b.breadtm-xyz.pages.dev View logs
6:29 PM
[breadtm.xyz] Analyze (javascript) success on main
6:29 PM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki
mmmm rainbow
GnorpSylver 10/03/2022 6:48 PM
What editor do you use
6:48 PM
i use notepad
6:48 PM
Quite literally
GnorpSylver
i use notepad
Nishi-Breadotron eki 10/03/2022 6:48 PM
GnorpSylver 10/03/2022 6:49 PM
Wha?
6:49 PM
It comes with windows and it works
GnorpSylver
What editor do you use
Nishi-Breadotron eki 10/03/2022 6:49 PM
https://www.jetbrains.com/webstorm/
WebStorm: The Smartest JavaScript IDE, by JetBrains
WebStorm, our IDE for JS and related technologies, makes the development experience more enjoyable by automating routine work and helping with complex tasks.
GnorpSylver
It comes with windows and it works
Nishi-Breadotron eki 10/03/2022 6:49 PM
right yeah yeah
GitHub BOT 11/03/2022 12:17 PM
imgbot[bot]
[breadtm.xyz:imgbot] 1 new commit
`478f9a4` [ImgBot] Optimize images - ImgBotApp
12:17 PM
imgbot[bot]
[ItsBreadTime/breadtm.xyz] New branch created: imgbot
12:17 PM
[breadtm.xyz] Deployed successfully on imgbot
Latest commit: 478f9a4 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://6047dcd3.breadtm-xyz.pages.dev View logs
12:17 PM
[breadtm.xyz] Cloudflare Pages checks success on imgbot
12:17 PM
imgbot[bot]
[ItsBreadTime/breadtm.xyz] Pull request opened: #3 [ImgBot] Optimize images

## Beep boop. Your images are optimized!

Your image file size has been reduced by 6% Details | File | Before | After | Percent reduction | |:--|:--|:--|:--| | /assets/vendor/remixicon/remixicon.symbol.svg | 876.89kb | 812.52kb | 7.34% | | /assets/vendor/remixicon/remixicon.svg | 1,167.50kb | 1,116.11kb | 4.40% | | | | | | | Total : | 2,044.39kb | 1,928.63kb | 5.66% | --- docs | [:octocat: repo](https://github.com/i...
12:18 PM
[breadtm.xyz] GitHub Code Scanning checks success on pull request #3
12:18 PM
[breadtm.xyz] No new or fixed alerts on pull request #3
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/3/merge` (commit 89f5e675b0f6de5ad49ca1dc431fab36e09382e4) and `refs/heads/imgbot` (commit 478f9a40c0aa8ae2a4cf1acf99f7f39981a90af3). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:javascript | :hea...
12:18 PM
[breadtm.xyz] Analyze (javascript) success on pull request #3
12:18 PM
[breadtm.xyz] GitHub Actions checks success on pull request #3
GitHub BOT 11/03/2022 12:26 PM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #3 [ImgBot] Optimize images
12:26 PM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`478f9a4` [ImgBot] Optimize images - ImgBotApp `3816116` Merge pull request #3 from ItsBreadTime/imgbot - ItsBreadTime
12:26 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 3816116 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://adb439f7.breadtm-xyz.pages.dev View logs
12:26 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:26 PM
imgbot[bot]
[ItsBreadTime/breadtm.xyz] branch deleted: imgbot
12:28 PM
[breadtm.xyz] Analyze (javascript) success on main
12:28 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 12/03/2022 3:21 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`73fc6f8` (hopefully) fix 404 page not loading css and js - ItsBreadTime
3:21 PM
[breadtm.xyz] Cloudflare Pages checks success on main
3:21 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 73fc6f8 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://30c859af.breadtm-xyz.pages.dev View logs
3:23 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`17b6f00` fix 404 page title - ItsBreadTime
3:23 PM
[breadtm.xyz] Cloudflare Pages checks success on main
3:23 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 17b6f00 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://910034cd.breadtm-xyz.pages.dev View logs
3:23 PM
[breadtm.xyz] Analyze (javascript) success on main
3:23 PM
[breadtm.xyz] GitHub Actions checks success on main
3:24 PM
[breadtm.xyz] Analyze (javascript) success on main
3:25 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 13/03/2022 11:49 PM
[breadtm.xyz] Analyze (javascript) success on main
11:49 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub
Click to see attachment 🖼️
Nishi-Breadotron eki 13/03/2022 11:50 PM
uhm what
11:51 PM
oh its scheduled
GitHub BOT 13/03/2022 11:53 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`406552c` stop scheduled code analysis - ItsBreadTime
11:54 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:54 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 406552c Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://d4b4cf3a.breadtm-xyz.pages.dev View logs
11:55 PM
[breadtm.xyz] Analyze (javascript) success on main
11:55 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 14/03/2022 12:27 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`2adc393` Update codeql-analysis.yml - ItsBreadTime
12:27 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 2adc393 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://8366fb5e.breadtm-xyz.pages.dev View logs
12:27 AM
[breadtm.xyz] Cloudflare Pages checks success on main
12:29 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`4de9048` Update codeql-analysis.yml - ItsBreadTime
12:29 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 4de9048 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://15b891e2.breadtm-xyz.pages.dev View logs
12:29 AM
[breadtm.xyz] Cloudflare Pages checks success on main
12:30 AM
[breadtm.xyz] Analyze (javascript) on main
There are 1 failures, 0 warnings, and 0 notices.
12:30 AM
[breadtm.xyz] GitHub Actions checks failure on main
12:31 AM
[breadtm.xyz] Analyze (javascript) success on main
12:31 AM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki discord developers #api-announcements 17/03/2022 2:15 AM
Deleted User 17/03/2022 2:26 AM
can i get mod
Deleted User
can i get mod
Nishi-Breadotron eki 17/03/2022 2:36 AM
Ok
Deleted User 17/03/2022 2:36 AM
2:36 AM
Nishi-Breadotron eki 17/03/2022 2:37 AM
Deleted User 17/03/2022 2:41 AM
Such a friendly man
Deleted User 17/03/2022 3:56 AM
love ya bro
Deleted User
love ya bro
Toaster™ 17/03/2022 5:18 AM
yo you takin floof away from me?! (edited)
Toaster™
yo you takin floof away from me?! (edited)
Nishi-Breadotron eki 17/03/2022 11:48 AM
Toaster™
yo you takin floof away from me?! (edited)
Deleted User 17/03/2022 12:10 PM
what
Nishi-Breadotron eki
Toaster™ 17/03/2022 4:41 PM
Toaster™
Deleted User 17/03/2022 4:46 PM
wdym taking floof away from you
1
4:46 PM
4:47 PM
I'm not taking away anything what
4:48 PM
u okay or in a nutshell
Discord Developers #api-announcements SERVER 18/03/2022 9:36 AM
API versions & deprecations update Based on a review of bot usage and discussion with developers, we are postponing the decommission of API v7 until early 2023 The API v6 decommission will continue as planned. The last officially supported date is Tuesday, May 3. Additionally, we’ve gotten some questions around what the decommission process looks like. We've provided further details on what to expect here: https://github.com/discord/discord-api-docs/discussions/4657 Thanks to all community members for their feedback and input!
Discord Developers #api-announcements SERVER 25/03/2022 9:26 AM
Hi all! We’re happy to announce that open beta for slash command localization is starting today! In addition to being something we know a lot of you have been eager for, it’s also a great feature for expanding the userbase of your apps. We have betas available for iOS and desktop. -The iOS beta requires you to have an app of version 117.0 or higher installed. You don't have to do anything special to enable it, other than be a member of this server. -The desktop beta requires a build override, which is linked below. It's built on top of slate 2, so it will include the look and feel changes from that override. -(Android is under development and we’ll have more news on it in the future.) In addition, you can already begin submitting translations for slash commands, as the API for this is stable. See the documentation at https://discord.com/developers/docs/interactions/application-commands#localization for instructions and other details. As a reminder, a user’s chosen language is now available in interaction payloads, so you can localize your interaction responses as well. Please let us know in #deleted-channel if you have any feedback about the behavior of localized slash commands! Desktop build override: https://discord.com/__development/link?s=BfVH8Z8qL1z5eLXlAUJT5uqob9jkwn937VrnvSL5kXg%3D.eyJ0YXJnZXRCdWlsZE92ZXJyaWRlIjp7ImRpc2NvcmRfd2ViIjp7InR5cGUiOiJicmFuY2giLCJpZCI6ImZlYXR1cmUvd2ViLXNsYXNoLWNvbW1hbmQtbG9jYWxpemF0aW9uIn19LCJyZWxlYXNlQ2hhbm5lbCI6bnVsbCwidmFsaWRGb3JVc2VySWRzIjpbXSwiYWxsb3dMb2dnZWRPdXQiOmZhbHNlLCJleHBpcmVzQXQiOiJXZWQsIDMxIEF1ZyAyMDIyIDE3OjU2OjQ2IEdNVCJ9 (edited)
Nishi-Breadotron eki 25/03/2022 11:39 AM
huh
Nishi-Breadotron eki
huh
Deleted User 25/03/2022 3:10 PM
Discord Developers #api-announcements SERVER 31/03/2022 11:07 AM
API v6 decommission extension Another update on decommission plans for deprecated API versions. We are extending the API v6 decommission to 2023 to match the v7 timeline. For more information, see here: https://github.com/discord/discord-api-docs/discussions/4725
Discord Developers #api-announcements SERVER 1/04/2022 6:09 AM
Hey everyone, Last summer, we shared a big announcement: on April 30, 2022, Message Content would become a Privileged Intent. This change was for only verified apps, and it meant that over the following nine months, developers would need to migrate to our new best practices on commands (i.e. use Slash Commands, or request and be approved for the Message Intent). This was and still is a significant change for many of you, and one you’ve told us you were anxious about. With that in mind, we have an update about the timeline. Now that we’ve finished the major feature work required to enable those of you who have not been able to migrate - including massive projects like the new command permissions system (in testing!), Slate v2, a whole set of improvements like attachments, localization (desktop and iOS), autocomplete, channel type restrictions, min/max constraints on numeric option types, and other features like modal interactions and guild locales -- we believe there is a clear pathway to migration for verified apps. That said, we also want to acknowledge two things: 1. Even with the tools and time, migration can still be a big lift for some developers. 2. Users can benefit from more proactive information and education about Slash Commands. Privacy is paramount for users on Discord, so we want to support you by doing our part to spread awareness about the new way to interact with apps. We want to help your users, and you, feel as confident about Slash Commands as we do. With all this in mind, we have some news to share with you: ️ We have extended the deprecation period for message content by an additional four months. The new deadline is now Wednesday, August 31, 2022, with enforcement starting on Thursday, September 1, 2022. During this time, we’re going to be educating users actively on Slash Commands, from content in our marketing to in-app indicators and prompts. ️ Note that since this milestone is a requirement for the App Directory, that will be moving out to later this year as well. ---- What should you do during this additional time? 1. Finish migrating as soon as you can. We want to encourage everyone to work toward the original date, so you can participate in opportunities that require your migration to be completed. Make sure to read our Message Content review policy (https://support.discord.com/hc/en-us/articles/4410940809111-Message-Content-Intent-Review-Policy) if you haven’t yet, and if you need the intent and meet the criteria, submit your request ASAP. 2. Try out our new features! Give us feedback in their respective channels, and make new feature requests on GitHub discussions for functionality that would help with your use case. 3. Get ready for discovery. You now have more time for this, as well. Create some new marketing assets for your app, localize your commands -- anything you think puts your best foot forward. If you are verified, you will see an "App Directory" section of the Developer Portal with a checklist of things to complete before you can click Enable Discovery. As always, we’ll post news here as soon as we have rollout timing updates to share. You all have done such a fantastic job iterating, joining alphas and betas for our features, submitting productive questions to our Q&As, and most importantly being specific about what you need to be successful. Keep it up! As always, thanks for joining us on the journey. Happy migrating,

- Discord

(edited)
Discord Developers #api-announcements SERVER 1/04/2022 7:24 AM
Guild Bans Pagination Today we've made a breaking API change to improve reliability and stability of the `GET /guilds/{guild.id}/bans` endpoint. Starting today, a maximum number of results will be returned in the response (configurable via a `limit` parameter). `before` and `after` can be supplied with a user `id` to paginate the response from the endpoint. You can learn more about the new endpoint parameters over on our docs site: https://discord.com/developers/docs/resources/guild#get-guild-bans
Discord Developers #api-announcements
Hey everyone, Last summer, we shared a big announcement: on April 30, 2022, Message Content would become a Privileged Intent. This change was for only verified apps, and it meant that over the following nine months, developers would need to migrate to our new best practices on commands (i.e. use Slash Commands, or request and be approved for the Message Intent). This was and still is a significant change for many of you, and one you’ve told us you were anxious about. With that in mind, we have an update about the timeline. Now that we’ve finished the major feature work required to enable those of you who have not been able to migrate - including massive projects like the new command permissions system (in testing!), Slate v2, a whole set of improvements like attachments, localization (desktop and iOS), autocomplete, channel type restrictions, min/max constraints on numeric option types, and other features like modal interactions and guild locales -- we believe there is a clear pathway to migration for verified apps. That said, we also want to acknowledge two things: 1. Even with the tools and time, migration can still be a big lift for some developers. 2. Users can benefit from more proactive information and education about Slash Commands. Privacy is paramount for users on Discord, so we want to support you by doing our part to spread awareness about the new way to interact with apps. We want to help your users, and you, feel as confident about Slash Commands as we do. With all this in mind, we have some news to share with you: ️ We have extended the deprecation period for message content by an additional four months. The new deadline is now Wednesday, August 31, 2022, with enforcement starting on Thursday, September 1, 2022. During this time, we’re going to be educating users actively on Slash Commands, from content in our marketing to in-app indicators and prompts. ️ Note that since this milestone is a requirement for the App Directory, that will be moving out to later this year as well. ---- What should you do during this additional time? 1. Finish migrating as soon as you can. We want to encourage everyone to work toward the original date, so you can participate in opportunities that require your migration to be completed. Make sure to read our Message Content review policy (https://support.discord.com/hc/en-us/articles/4410940809111-Message-Content-Intent-Review-Policy) if you haven’t yet, and if you need the intent and meet the criteria, submit your request ASAP. 2. Try out our new features! Give us feedback in their respective channels, and make new feature requests on GitHub discussions for functionality that would help with your use case. 3. Get ready for discovery. You now have more time for this, as well. Create some new marketing assets for your app, localize your commands -- anything you think puts your best foot forward. If you are verified, you will see an "App Directory" section of the Developer Portal with a checklist of things to complete before you can click Enable Discovery. As always, we’ll post news here as soon as we have rollout timing updates to share. You all have done such a fantastic job iterating, joining alphas and betas for our features, submitting productive questions to our Q&As, and most importantly being specific about what you need to be successful. Keep it up! As always, thanks for joining us on the journey. Happy migrating,

- Discord

(edited)
GnorpSylver 1/04/2022 8:40 AM
Does this mean I can't use commands like ! on my unverified bot
GitHub BOT 3/04/2022 1:58 PM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`10fbeee` resized image - ItsBreadTime `ad82413` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
1:59 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: ad82413 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://cf2049b2.breadtm-xyz.pages.dev View logs
1:59 PM
[breadtm.xyz] Cloudflare Pages checks success on main
2:00 PM
[breadtm.xyz] Analyze (javascript) success on main
2:00 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 24/04/2022 8:59 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`fbb39b7` Update index.html - ItsBreadTime
9:00 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: fbb39b7 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://cd3a5026.breadtm-xyz.pages.dev View logs
9:00 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:01 PM
[breadtm.xyz] Analyze (javascript) success on main
9:01 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 27/04/2022 10:51 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`0a7c36c` Create pc-specs.txt - ItsBreadTime
10:51 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 0a7c36c Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://5d2657d6.breadtm-xyz.pages.dev View logs
10:51 PM
[breadtm.xyz] Cloudflare Pages checks success on main
10:53 PM
[breadtm.xyz] Analyze (javascript) success on main
10:53 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 28/04/2022 1:50 AM
ItsBreadTime
[breadtm.xyz:ItsBreadTime-patch-1] 1 new commit
`2f1d363` Added proper pc specs - ItsBreadTime
1:50 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: ItsBreadTime-patch-1
1:50 AM
[breadtm.xyz] Deployed successfully on ItsBreadTime-patch-1
Latest commit: 2f1d363 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://e8272ad5.breadtm-xyz.pages.dev View logs
1:50 AM
[breadtm.xyz] Cloudflare Pages checks success on ItsBreadTime-patch-1
1:50 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #4 Added proper pc specs
I tried my best to make it responsive, it did not turn out great tbh.
1:51 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #4 Added proper pc specs
1:52 AM
ItsBreadTime
[breadtm.xyz:ItsBreadTime-patch-2] 1 new commit
`1694977` Make proper pc specs page - ItsBreadTime
1:52 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: ItsBreadTime-patch-2
1:52 AM
[breadtm.xyz] Cloudflare Pages checks success on ItsBreadTime-patch-2
1:52 AM
[breadtm.xyz] Deployed successfully on ItsBreadTime-patch-2
Latest commit: 1694977 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://d7faf62f.breadtm-xyz.pages.dev View logs
1:52 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`77e8e2d` Delete other directory - ItsBreadTime
1:52 AM
[breadtm.xyz] GitHub Code Scanning checks success on ItsBreadTime-patch-1
1:52 AM
[breadtm.xyz] No new or fixed alerts on ItsBreadTime-patch-1
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/4/merge` (commit 11124663b04fe406f38009c1631f43328c163f32) and `refs/heads/ItsBreadTime-patch-1` (commit 2f1d3630392668d39dcee4397324d6cbd51c43b4). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/la...
1:53 AM
[breadtm.xyz] Analyze (javascript) success on ItsBreadTime-patch-1
1:53 AM
[breadtm.xyz] GitHub Actions checks success on ItsBreadTime-patch-1
1:53 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #5 Make proper pc specs page
1:53 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 77e8e2d Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://70813df0.breadtm-xyz.pages.dev View logs
1:53 AM
[breadtm.xyz] Cloudflare Pages checks success on main
1:53 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #5 Make proper pc specs page
1:53 AM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`1694977` Make proper pc specs page - ItsBreadTime `d513ae3` Merge pull request #5 from ItsBreadTime/ItsBrea... - ItsBreadTime
1:53 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] branch deleted: ItsBreadTime-patch-2
1:53 AM
[breadtm.xyz] Cloudflare Pages checks success on main
1:53 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: d513ae3 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://915c6f94.breadtm-xyz.pages.dev View logs
1:54 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`69f19ad` Create proper setup page - ItsBreadTime
1:54 AM
[breadtm.xyz] GitHub Code Scanning checks success on ItsBreadTime-patch-2
1:54 AM
[breadtm.xyz] No new or fixed alerts on ItsBreadTime-patch-2
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/5/merge` (commit 1c034682aac67bbfc4fcb6eef2c125085ad9e58e) and `refs/heads/ItsBreadTime-patch-2` (commit 1694977781453f125ab4d554cc00f08804f56b60). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/la...
1:54 AM
[breadtm.xyz] Cloudflare Pages checks success on main
1:54 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 69f19ad Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://43310f47.breadtm-xyz.pages.dev View logs
1:54 AM
[breadtm.xyz] Analyze (javascript) success on ItsBreadTime-patch-2
1:54 AM
[breadtm.xyz] GitHub Actions checks success on main
1:55 AM
[breadtm.xyz] Analyze (javascript) success on main
1:55 AM
[breadtm.xyz] GitHub Actions checks success on main
1:56 AM
[breadtm.xyz] Analyze (javascript) success on main
1:56 AM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki 28/04/2022 1:57 AM
Thank god it didn't fail
1:57 AM
(I'm sleepy)
Discord Developers #api-announcements SERVER 28/04/2022 6:29 AM
Hey everyone! Today we are rolling out our new Command Permissions system to the rest of the servers on desktop. You can see our documentation for it here: https://github.com/discord/discord-api-docs/pull/4830 If you haven’t checked it out yet, you can head to Server Settings → Integrations and then click ‘Manage’ next to an app. Here you can customize individual permissions for each command, as well as specify where they can be used and who can use them. As many of you know, we’ve been testing this for a while - thanks to those who have given us great feedback along the way! Anyone is still welcome to send us more (https://survey.alchemer.com/s3/6826166/Command-Permissions-feedback) and you can see the full blog post here: https://discord.com/blog/slash-commands-permissions-discord-apps-bots Thanks!
GitHub BOT 28/04/2022 1:06 PM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`736f9f7` better responsiveness, more info - ItsBreadTime `c137b44` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
1:06 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: c137b44 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://dbaa0041.breadtm-xyz.pages.dev View logs
1:06 PM
[breadtm.xyz] Cloudflare Pages checks success on main
Nishi-Breadotron eki 28/04/2022 1:06 PM
yay
1:06 PM
it workss (edited)
GitHub BOT 28/04/2022 1:07 PM
[breadtm.xyz] Analyze (javascript) success on main
1:07 PM
[breadtm.xyz] GitHub Actions checks success on main
1:10 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`2c1ad03` removed previous setup page - ItsBreadTime
1:10 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 2c1ad03 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://faf1d6b5.breadtm-xyz.pages.dev View logs
1:10 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:12 PM
[breadtm.xyz] Analyze (javascript) success on main
1:12 PM
[breadtm.xyz] GitHub Actions checks success on main
1:16 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`2d52a52` added setup hyperlink to main page - ItsBreadTime
1:17 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:17 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 2d52a52 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://4ecea355.breadtm-xyz.pages.dev View logs
1:18 PM
[breadtm.xyz] Analyze (javascript) success on main
1:18 PM
[breadtm.xyz] GitHub Actions checks success on main
1:23 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`740a382` Update setup.html - ItsBreadTime
1:23 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 740a382 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b70cac24.breadtm-xyz.pages.dev View logs
1:23 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:24 PM
[breadtm.xyz] Analyze (javascript) success on main
1:24 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 29/04/2022 6:57 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`fff1076` Added favicon, web embed - ItsBreadTime
6:57 PM
[breadtm.xyz] Cloudflare Pages checks success on main
6:57 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: fff1076 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://19e53340.breadtm-xyz.pages.dev View logs
6:58 PM
[breadtm.xyz] Analyze (javascript) success on main
6:58 PM
[breadtm.xyz] GitHub Actions checks success on main
Discord Developers #api-announcements SERVER 30/04/2022 9:12 AM
Hi everyone, Earlier this week, we rolled out the long-awaited Command Permissions v2. If you’re active in this server, you’ve seen the iteration of permissions over the course of several months, from wireframes and tech proposals to betas and sneak peeks. (If you’re not, the first you heard about this new feature may have been Wednesday’s announcement.) We’ve been working with many of you over those several months to make a great new system for managing slash commands. We landed on something we’re proud of: a system that gives moderators the power to configure their servers how best works for them, and also gives developers peace of mind when you make new commands or migrate for the first time. The new permissions system is inherently a breaking change, because it is an inversion of control from the previous command permissions system. Before, developers were entirely in control of permission setups, much like text commands. Now, that control lies in the hands of server moderators. There is no API version bump that can protect against that change; both cannot be supported simultaneously. For changes like this, there needs to be an ample amount of heads up and communication to those using the current system, which we failed to provide. Here’s what we’ll be doing moving forward:

- We’ll continue investing in the new permissions system, and fix the bugs that were reported to us in the past few days—thank you to all who did so

- We’ll do an internal postmortem on this launch to understand why this release did not get properly audited as a breaking change requiring communication. We’ll also review our internal runbooks for breaking changes to ensure that things are properly communicated when raised

- Moving forward, that communication will happen here in our API docs as well as the Discord Developers server. We recognize that not all developers are present in DDevs, but we hope you’ll consider joining—discord.gg/discord-developers. Our announcement channels are the place to follow for API updates, product announcements, and community events!

- We’ll take another look at our public roadmaps. Right now, they’re useful for understanding what kinds of projects we’re thinking about, but not for understanding timing or near-ness

- We’ll also take another look at how we are running feature betas. The most surefire way to be prepared for changes is to be able to experience them ahead of time.

Thank you again for all the great thoughts and suggestions to our new Command Permissions system (over the past months as well as yesterday). We appreciate it and will share more updates here on the above.
GitHub BOT 1/05/2022 2:03 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`81aca23` overall improvement - ItsBreadTime
2:03 AM
[breadtm.xyz] Cloudflare Pages checks success on main
2:03 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 81aca23 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://660951e9.breadtm-xyz.pages.dev View logs
2:05 AM
[breadtm.xyz] Analyze (javascript) success on main
2:05 AM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 1/05/2022 6:02 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`38bbda1` Update setup.html - ItsBreadTime
6:03 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 38bbda1 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://cd353da1.breadtm-xyz.pages.dev View logs
6:03 PM
[breadtm.xyz] Cloudflare Pages checks success on main
6:04 PM
[breadtm.xyz] Analyze (javascript) success on main
6:04 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 1/05/2022 6:44 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`0dccfe0` Minor correction - ItsBreadTime
6:44 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 0dccfe0 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://2eec0343.breadtm-xyz.pages.dev View logs
6:44 PM
[breadtm.xyz] Cloudflare Pages checks success on main
6:46 PM
[breadtm.xyz] Analyze (javascript) success on main
6:46 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 2/05/2022 4:26 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`458101e` Update index.html - ItsBreadTime
4:26 PM
[breadtm.xyz] Cloudflare Pages checks success on main
4:26 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 458101e Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://e8636582.breadtm-xyz.pages.dev View logs
4:28 PM
[breadtm.xyz] Analyze (javascript) success on main
4:28 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 3/05/2022 12:43 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`f15b710` Create _redirects - ItsBreadTime
12:43 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: f15b710 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://5224cf04.breadtm-xyz.pages.dev View logs
12:43 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:45 PM
[breadtm.xyz] Analyze (javascript) success on main
12:45 PM
[breadtm.xyz] GitHub Actions checks success on main
12:46 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`edbad0d` change setup.html to my-setup - ItsBreadTime
12:47 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: edbad0d Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://14a99ad2.breadtm-xyz.pages.dev View logs
12:47 PM
[breadtm.xyz] Cloudflare Pages checks success on main
12:48 PM
[breadtm.xyz] Analyze (javascript) success on main
12:48 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 4/05/2022 1:07 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`76d77cb` correct setup link, embed readme, more redirect - ItsBreadTime
1:07 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:07 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 76d77cb Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://875517ea.breadtm-xyz.pages.dev View logs
1:09 PM
[breadtm.xyz] Analyze (javascript) success on main
1:09 PM
[breadtm.xyz] GitHub Actions checks success on main
1:12 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`474ab95` will this work? - ItsBreadTime
1:12 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 474ab95 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b3c19d04.breadtm-xyz.pages.dev View logs
1:12 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:13 PM
[breadtm.xyz] Analyze (javascript) success on main
1:13 PM
[breadtm.xyz] GitHub Actions checks success on main
1:16 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`d618953` it did not work. - ItsBreadTime
1:16 PM
[breadtm.xyz] Cloudflare Pages checks success on main
1:16 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: d618953 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b16d3d10.breadtm-xyz.pages.dev View logs
1:18 PM
[breadtm.xyz] Analyze (javascript) success on main
1:18 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 5/05/2022 12:32 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] branch deleted: ItsBreadTime-patch-1
12:32 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: testing
12:32 AM
[breadtm.xyz] Cloudflare Pages checks success on main
12:32 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: d618953 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://cdf28608.breadtm-xyz.pages.dev View logs
12:36 AM
ItsBreadTime
[breadtm.xyz:testing] 1 new commit
`3f0a92c` change color - ItsBreadTime
12:36 AM
[breadtm.xyz] Cloudflare Pages checks success on testing
12:36 AM
[breadtm.xyz] Deployed successfully on testing
Latest commit: 3f0a92c Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://36bd9e42.breadtm-xyz.pages.dev View logs
12:37 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #6 change color
12:38 AM
[breadtm.xyz] GitHub Code Scanning checks success on pull request #6
12:38 AM
[breadtm.xyz] No new or fixed alerts on pull request #6
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/6/merge` (commit 59069c9f13abb113b7520354dd97bdf0c0e1cc18) and `refs/heads/testing` (commit 3f0a92ce36169943e5dda9936a37db032f1f9b4f). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:javasc...
12:38 AM
[breadtm.xyz] Analyze (javascript) success on pull request #6
12:38 AM
[breadtm.xyz] GitHub Actions checks success on pull request #6
GitHub BOT 5/05/2022 12:48 AM
ItsBreadTime
[breadtm.xyz:test-2] 1 new commit
`a311d0c` brown green - ItsBreadTime
12:48 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: test-2
12:48 AM
[breadtm.xyz] Cloudflare Pages checks success on test-2
12:48 AM
[breadtm.xyz] Deployed successfully on test-2
Latest commit: a311d0c Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://a495821a.breadtm-xyz.pages.dev View logs
12:49 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #7 Test 2
12:50 AM
[breadtm.xyz] GitHub Code Scanning checks success on pull request #7
12:50 AM
[breadtm.xyz] No new or fixed alerts on pull request #7
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/7/merge` (commit f7ee9aba734d12aa08057b01f06ed3e35ade03c6) and `refs/heads/test-2` (commit a311d0c7ee40f1d69814968035d123cb214821ef). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:javascr...
12:50 AM
[breadtm.xyz] Analyze (javascript) success on pull request #7
12:50 AM
[breadtm.xyz] GitHub Actions checks success on pull request #7
12:54 AM
ItsBreadTime
[breadtm.xyz:test-3] 1 new commit
`cefc8dd` Light grey background - ItsBreadTime
12:54 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] New branch created: test-3
12:55 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request opened: #8 Test 3
12:55 AM
[breadtm.xyz] Deployed successfully on pull request #8
Latest commit: cefc8dd Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://46e7a247.breadtm-xyz.pages.dev View logs
12:55 AM
[breadtm.xyz] Cloudflare Pages checks success on pull request #8
12:55 AM
cloudflare-pages[bot]
[ItsBreadTime/breadtm.xyz] New comment on pull request #8: Test 3

## Deploying with &nbsp;<a href="https://pages.dev"><img alt="Cloudflare Pages" src="https://user-images.githubusercontent.com/23264/106598434-9e719e00-654f-11eb-9e59-6167043cfa01.png" width="16"></a> &nbsp;Cloudflare Pages

<table><tr><td><strong>Latest commit:</strong> </td><td> <code>cefc8dd</code> </td></tr> <tr><td><strong>Status:</strong></td><td>&nbsp;✅&nbsp; Deploy successful!</td></tr> <tr><td><strong>Preview URL:</strong></td><td> <a href='https://46e7a247.breadtm-xyz.pages.dev'>htt...
12:56 AM
[breadtm.xyz] No new or fixed alerts on pull request #8
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/8/merge` (commit 4808cd0709e4362def0baf58288b961d3d50f5e3) and `refs/heads/test-3` (commit cefc8dda8fe348dc2c6cad4a373d48662e16f892). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:javascr...
12:56 AM
[breadtm.xyz] GitHub Code Scanning checks success on pull request #8
12:57 AM
[breadtm.xyz] Analyze (javascript) success on pull request #8
12:57 AM
[breadtm.xyz] GitHub Actions checks success on pull request #8
12:57 AM
ItsBreadTime
[breadtm.xyz:test-3] 1 new commit
`3c78e19` darker gray - ItsBreadTime
12:57 AM
[breadtm.xyz] Deployed successfully on pull request #8
Latest commit: 3c78e19 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://15dd4374.breadtm-xyz.pages.dev View logs
12:57 AM
[breadtm.xyz] Cloudflare Pages checks success on pull request #8
12:59 AM
[breadtm.xyz] No new or fixed alerts on pull request #8
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/8/merge` (commit e95ba56b865b7aaef8fd6aca8f062ceb8e7dc4e4) and `refs/heads/test-3` (commit 3c78e190cee448d7e6c46b019107534b7d7fca86). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:javascr...
12:59 AM
[breadtm.xyz] GitHub Code Scanning checks success on pull request #8
12:59 AM
[breadtm.xyz] Analyze (javascript) success on pull request #8
12:59 AM
[breadtm.xyz] GitHub Actions checks success on pull request #8
1:03 AM
ItsBreadTime
[breadtm.xyz:test-3] 1 new commit
`c46313e` MORE DARKER - ItsBreadTime
1:03 AM
[breadtm.xyz] Deployed successfully on pull request #8
Latest commit: c46313e Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://3b225dc1.breadtm-xyz.pages.dev View logs
1:03 AM
[breadtm.xyz] Cloudflare Pages checks success on pull request #8
1:05 AM
[breadtm.xyz] No new or fixed alerts on pull request #8
#### No new or fixed alerts View all branch alerts.

### Analyses

Code scanning compared `refs/heads/main` with `refs/pull/8/merge` (commit e4c17d08e33d8f8218d09e76a284d80eb9c015b4) and `refs/heads/test-3` (commit c46313edb94b9fcc78df63f264e0ee273be6e347). | Category | Base branch | Pull request | | :------- | :---------: | :----------: | | .github/workflows/codeql-analysis.yml:analyze/language:javascr...
1:05 AM
[breadtm.xyz] GitHub Code Scanning checks success on pull request #8
1:05 AM
[breadtm.xyz] Analyze (javascript) success on pull request #8
1:05 AM
[breadtm.xyz] GitHub Actions checks success on pull request #8
1:10 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #8 Test 3
1:10 AM
ItsBreadTime
[breadtm.xyz:main] 6 new commits
`3f0a92c` change color - ItsBreadTime `a311d0c` brown green - ItsBreadTime `cefc8dd` Light grey background - ItsBreadTime `3c78e19` darker gray - ItsBreadTime `c46313e` MORE DARKER - ItsBreadTime
1:10 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #7 Test 2
1:10 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] Pull request closed: #6 change color
1:10 AM
ItsBreadTime
[ItsBreadTime/breadtm.xyz] branch deleted: test-3
1:11 AM
[breadtm.xyz] Cloudflare Pages checks success on main
1:11 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 03569e4 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://f52b2216.breadtm-xyz.pages.dev View logs
1:13 AM
[breadtm.xyz] Analyze (javascript) success on main
1:13 AM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki 5/05/2022 1:13 AM
Fuck ton of opinion testing
1:13 AM
1:14 AM
Might as well make a theme switcher to switch from dark to uhhhh... Dark? I mean luxurious green and lively blue I'm such a genius at naming ikr (edited)
Nishi-Breadotron eki pinned a message to this channel. 5/05/2022 1:18 AM
Deleted User 5/05/2022 1:19 AM
GitHub BOT 5/05/2022 3:49 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`9f9f965` make it more easier because - ItsBreadTime
3:49 PM
[breadtm.xyz] Cloudflare Pages checks success on main
3:49 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 9f9f965 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://1121e229.breadtm-xyz.pages.dev View logs
3:50 PM
[breadtm.xyz] Analyze (javascript) success on main
3:50 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 5/05/2022 4:18 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`4900882` Update 404.html - ItsBreadTime
4:18 PM
[breadtm.xyz] Cloudflare Pages checks success on main
4:18 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 4900882 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://db1706cd.breadtm-xyz.pages.dev View logs
4:20 PM
[breadtm.xyz] Analyze (javascript) success on main
4:20 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 9/05/2022 12:20 AM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`690e6b6` added software section - ItsBreadTime
12:20 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 690e6b6 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://8084ca1b.breadtm-xyz.pages.dev View logs
12:20 AM
[breadtm.xyz] Cloudflare Pages checks success on main
12:22 AM
[breadtm.xyz] Analyze (javascript) success on main
12:22 AM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 9/05/2022 2:18 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`cfa9034` added internet section - ItsBreadTime
2:18 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: cfa9034 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://c9781300.breadtm-xyz.pages.dev View logs
2:18 PM
[breadtm.xyz] Cloudflare Pages checks success on main
2:20 PM
[breadtm.xyz] Analyze (javascript) success on main
2:20 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 9/05/2022 3:02 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`3d0859d` idfk just wanted to commit - ItsBreadTime
3:02 PM
[breadtm.xyz] Cloudflare Pages checks success on main
3:02 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 3d0859d Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://d8fc7c34.breadtm-xyz.pages.dev View logs
3:04 PM
[breadtm.xyz] Analyze (javascript) success on main
3:04 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 10/05/2022 9:03 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`d06c92f` removed bullshit - ItsBreadTime
9:03 PM
[breadtm.xyz] Cloudflare Pages checks success on main
9:03 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: d06c92f Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b2a825a0.breadtm-xyz.pages.dev View logs
9:05 PM
[breadtm.xyz] Analyze (javascript) success on main
9:05 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 14/05/2022 1:47 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `d06c92f`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz.vercel.app breadtm-xyz-git-main-itsbreadtime.vercel.app breadtm-xyz-itsbreadtime.vercel.app
Nishi-Breadotron eki 14/05/2022 1:52 PM
hehe
GitHub BOT 14/05/2022 8:36 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`e7b5ce6` added soon page - ItsBreadTime
8:36 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `e7b5ce6`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz-git-main-itsbreadtime.vercel.app breadtm-xyz-itsbreadtime.vercel.app breadtm-xyz.vercel.app ver.breadtm.xyz
8:36 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: e7b5ce6 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://6ac456bd.breadtm-xyz.pages.dev View logs
8:36 PM
[breadtm.xyz] Cloudflare Pages checks success on main
8:36 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`ba44340` change soon text color - ItsBreadTime
8:37 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: ba44340 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://b85c00f1.breadtm-xyz.pages.dev View logs
8:37 PM
[breadtm.xyz] Cloudflare Pages checks success on main
8:38 PM
[breadtm.xyz] Analyze (javascript) on main
There are 0 failures, 3 warnings, and 0 notices.
8:38 PM
[breadtm.xyz] GitHub Actions checks success on main
8:39 PM
[breadtm.xyz] Analyze (javascript) on main
There are 0 failures, 3 warnings, and 0 notices.
8:39 PM
[breadtm.xyz] GitHub Actions checks success on main
Nishi-Breadotron eki cloudflare developers #cloudflare-status 18/05/2022 4:48 PM
GitHub BOT 18/05/2022 11:02 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`33b2ba0` added index for my setup page - ItsBreadTime
11:02 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `33b2ba0`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz.vercel.app breadtm-xyz-git-main-itsbreadtime.vercel.app breadtm-xyz-itsbreadtime.vercel.app ver.breadtm.xyz
11:02 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:02 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 33b2ba0 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://f41506c5.breadtm-xyz.pages.dev View logs
11:04 PM
[breadtm.xyz] Analyze (javascript) on main
There are 0 failures, 3 warnings, and 0 notices.
11:04 PM
[breadtm.xyz] GitHub Actions checks success on main
11:06 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`09b4b35` i forgot to add quick link to notices section - ItsBreadTime
11:06 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `09b4b35`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz.vercel.app breadtm-xyz-itsbreadtime.vercel.app ver.breadtm.xyz breadtm-xyz-git-main-itsbreadtime.vercel.app
11:06 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:06 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 09b4b35 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://a25577f6.breadtm-xyz.pages.dev View logs
11:08 PM
[breadtm.xyz] Analyze (javascript) on main
There are 0 failures, 3 warnings, and 0 notices.
11:08 PM
[breadtm.xyz] GitHub Actions checks success on main
11:10 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`3a0d35a` fix the email link - ItsBreadTime
11:10 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `3a0d35a`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz.vercel.app breadtm-xyz-git-main-itsbreadtime.vercel.app breadtm-xyz-itsbreadtime.vercel.app ver.breadtm.xyz
11:10 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:10 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 3a0d35a Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://5a24b44f.breadtm-xyz.pages.dev View logs
11:12 PM
[breadtm.xyz] Analyze (javascript) on main
There are 0 failures, 3 warnings, and 0 notices.
11:12 PM
[breadtm.xyz] GitHub Actions checks success on main
Floofie Bread™ BOT 18/05/2022 11:12 PM
3 warnings?
Nishi-Breadotron eki 18/05/2022 11:14 PM
oh
GitHub BOT 18/05/2022 11:17 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`876d5d4` codeql v2 - ItsBreadTime
11:17 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `876d5d4`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

ver.breadtm.xyz breadtm-xyz-itsbreadtime.vercel.app breadtm-xyz.vercel.app breadtm-xyz-git-main-itsbreadtime.vercel.app
11:17 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:17 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 876d5d4 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://0d55caa7.breadtm-xyz.pages.dev View logs
11:17 PM
[breadtm.xyz] Analyze (javascript) on main
There are 1 failures, 0 warnings, and 0 notices.
11:17 PM
[breadtm.xyz] GitHub Actions checks failure on main
11:18 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`34ff886` oops, fixed it - ItsBreadTime
11:18 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `34ff886`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

ver.breadtm.xyz breadtm-xyz-git-main-itsbreadtime.vercel.app breadtm-xyz-itsbreadtime.vercel.app breadtm-xyz.vercel.app
11:18 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 34ff886 Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://f4dade9e.breadtm-xyz.pages.dev View logs
11:18 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:19 PM
[breadtm.xyz] Analyze (javascript) success on main
11:19 PM
[breadtm.xyz] GitHub Actions checks success on main
11:21 PM
ItsBreadTime
[breadtm.xyz:main] 1 new commit
`8c5582d` Create dependency-review.yml - ItsBreadTime
11:21 PM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `8c5582d`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz-itsbreadtime.vercel.app breadtm-xyz.vercel.app breadtm-xyz-git-main-itsbreadtime.vercel.app ver.breadtm.xyz
11:21 PM
[breadtm.xyz] Cloudflare Pages checks success on main
11:21 PM
[breadtm.xyz] Deployed successfully on main
Latest commit: 8c5582d Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://63565b50.breadtm-xyz.pages.dev View logs
11:23 PM
[breadtm.xyz] Analyze (javascript) success on main
11:23 PM
[breadtm.xyz] GitHub Actions checks success on main
GitHub BOT 19/05/2022 12:13 AM
ItsBreadTime
[breadtm.xyz:main] 2 new commits
`af0d4b4` change beta to dev channel - ItsBreadTime `50c241a` Merge branch 'main' of https://github.com/ItsBr... - ItsBreadTime
12:13 AM
vercel[bot]
[ItsBreadTime/breadtm.xyz] New comment on commit `50c241a`
Successfully deployed to the following URLs:

## breadtm-xyz – ./

breadtm-xyz-itsbreadtime.vercel.app breadtm-xyz-git-main-itsbreadtime.vercel.app breadtm-xyz.vercel.app ver.breadtm.xyz
12:13 AM
[breadtm.xyz] Cloudflare Pages checks success on main
12:13 AM
[breadtm.xyz] Deployed successfully on main
Latest commit: 50c241a Status:&nbsp;✅&nbsp; Deploy successful! Preview URL: https://cc6e0879.breadtm-xyz.pages.dev View logs
12:15 AM
[breadtm.xyz] Analyze (javascript) success on main
12:15 AM
[breadtm.xyz] GitHub Actions checks success on main
Cloudflare Developers #cloudflare-status SERVER 19/05/2022 7:00 AM
(edited)
Cloudflare Dashboard and Cloudflare API service issues
May 18, 21:16 UTC Resolved - This incident has been resolved. May 18, 21:06 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 18, 21:00 UTC Update - We are continuing to investigate this issue. May 18, 20:59 UTC Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
Cloudflare Developers #cloudflare-status SERVER 19/05/2022 9:53 PM
(edited)
Issues with Captcha Service
May 19, 12:29 UTC Resolved - This incident has been resolved. May 19, 12:15 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 19, 11:53 UTC Investigating - Cloudflare is aware of, and investigating, an issue which potentially impacts multiple customers. Customers might see issues with captcha service preventing access to the desired page. This is currently localized in Spain. Further detail will be provided as more information becomes available.
Cloudflare Developers #cloudflare-status SERVER 20/05/2022 1:27 AM
(edited)
Magic Transit API issues
May 19, 16:08 UTC Resolved - This incident has been resolved. May 19, 15:42 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 19, 15:25 UTC Investigating - Cloudflare is investigating issues with Magic Transit APIs. Customers using Magic Transit APIs are impacted as requests to change configs, including tunnel and static routes, might fail and/or errors may be displayed. These issues do not affect edge traffic, existing prefix advertisements or any other security features at the Cloudflare Edge.
Cloudflare Developers #cloudflare-status SERVER 20/05/2022 2:58 AM
(edited)
Canary Colo DNS issues at Edge
May 19, 17:30 UTC Resolved - This incident has been resolved. May 19, 17:13 UTC Update - We are continuing to monitor for any further issues. May 19, 17:09 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 19, 17:03 UTC Update - We are continuing to investigate this issue. May 19, 16:58 UTC Investigating - Cloudflare is investigating issues that may impact DNS issues at our canary colos these include KUL, LIS, and YYZ. We are currently working on a resolution and will provide an update as soon as possible.
Cloudflare Developers #cloudflare-status SERVER 20/05/2022 7:22 AM
(edited)
Cloudflare Community Maintenance
May 23, 06:00 UTC Completed - The scheduled maintenance has been completed. May 22, 22:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 19, 21:21 UTC Scheduled - Our vendor will be conducting a planned maintenance on the Cloudflare Community site (https://community.cloudflare.com). The Community will experience a period of read-only at some point during the maintenance period, lasting no more than 2 hours. We will update as soon as this maintenance window expires.
7:25 AM
(edited)
Cloudflare Community Maintenance
May 23, 15:00 UTC Completed - The scheduled maintenance has been completed. May 23, 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 19, 21:24 UTC Scheduled - Our vendor will be conducting a planned maintenance on the Cloudflare Community site (https://community.cloudflare.com). The Community may observe a short (1 - 2 minutes) window of read-only while our vendor performs database updates. We will update as soon as this maintenance window expires.
Cloudflare Developers #cloudflare-status SERVER 20/05/2022 3:39 PM
(edited)
Network Performance Issues in Eastern Canada
May 20, 07:01 UTC Resolved - This incident has been resolved. May 20, 06:03 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 20, 05:55 UTC Identified - The issue has been identified and a fix is being implemented. May 20, 05:38 UTC Investigating - Cloudflare is investigating issues with network performance Eastern Canada. We are working to analyse and mitigate this problem. More updates to follow shortly.
Cloudflare Developers #cloudflare-status SERVER 21/05/2022 6:36 AM
(edited)
Long hold delays for Enterprise telephone support
May 20, 21:58 UTC Resolved - This incident has been resolved. May 20, 21:17 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 20, 20:36 UTC Investigating - Our Enterprise telephone support system is currently experiencing issues - you may not be able to connect to report a technical issue via the phone. Please submit a ticket at https://dash.cloudflare.com/?to=/:account/support with your issue as an alternative, or if it's urgent - use live chat while logged into your Enterprise account on the Cloudflare dashboard. We will issue further updates on this status page as we work with our providers to resolve this issue.
Cloudflare Developers #cloudflare-status SERVER 21/05/2022 10:26 AM
(edited)
Elevated number of 522 errors in Newark, NJ, United States
May 20, 23:46 UTC Resolved - Between 23:46 - 00:04 UTC customers reaching Newark, NJ would have experienced an elevated number of 522 errors.
Cloudflare Developers #cloudflare-status SERVER 24/05/2022 1:54 AM
(edited)
Network Performance Issues in the Czech Republic
May 23, 17:24 UTC Resolved - This incident has been resolved. May 23, 15:57 UTC Identified - The issue has been identified and a fix is being implemented. May 23, 15:54 UTC Investigating - Cloudflare is investigating issues with network performance in the Czech Republic. We are working to analyze and mitigate this problem. More updates to follow shortly.
Cloudflare Developers #cloudflare-status SERVER 24/05/2022 7:51 AM
(edited)
Cloudflare Workers Analytics Issues
May 23, 23:54 UTC Resolved - This incident has been resolved. May 23, 23:46 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 23, 21:51 UTC Investigating - Some customers might experience errors accessing Cloudflare Workers Analytics data in the Cloudflare dashboard and APIs.
Cloudflare Developers #cloudflare-status SERVER 24/05/2022 6:37 PM
(edited)
Cloudflare API service issues impacting API Shield - API Discovery
May 24, 13:34 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 24, 10:32 UTC Identified - The issue has been identified and a fix is being implemented. May 24, 08:36 UTC Investigating - Cloudflare is investigating issues with Cloudflare APIs related to API Shield's API Discovery. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
Cloudflare Developers #cloudflare-status SERVER 24/05/2022 11:48 PM
Workers Update Delays and Cloudflare Pages Build Delays
May 24, 13:48 UTC Investigating - Cloudflare is experiencing delays in updating Workers on the edge and executing new Cloudflare Pages builds. This does not impact existing Workers and Pages projects already deployed in production. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Discord Developers #api-announcements SERVER 27/05/2022 5:14 AM
Hi everyone! As mentioned earlier this week, we’ve built a way to preview what your app product page will look like (if your app is verified and you are interested in joining the App Directory, coming later this year). How to preview your page:

- In the Developer Portal’s new App Directory section, the Product Page tab now shows a “Preview” button at the top. Clicking this will open a new tab that displays how the information you added in that tab will appear.
- You can also view your app product page in your browser directly by going to https://discord.com/application-directory/your_application_id. This will display information from the last time you clicked “Save changes” on your Product Page tab.

A few things to note:

- The only Discord user who can see your preview page is you! (If you’re on an app’s team, anyone on the team can see the preview).
- We’ve heard from some of you that you’d like to get your app ready early - i.e. even before you’ve checked off everything in the Discovery Status tab’s list or clicked the “Enable Discovery” button - so we’ve made this available for you as well! This means no matter your eligibility or opt-in status, you will still be able to preview your app product page. (However, note that your app must be at least verified to see this section of the Developer Portal.)
- Lastly, as with any feature, things may evolve so certain details can change.

We encourage you to make the most of all these available fields - think about how you want your bot to look and feel to users who will visit your page and consider adding it to their servers. Not all of these fields are required, but we encourage you to fill out all you can and take advantage of them. Below is an example for inspiration. Enjoy! (edited)
HetrixTools BOT 28/05/2022 11:37 AM
Uptime Kuma is now DOWN Target: uptime.ibred.co Noticed at: 2022-05-28 01:37:39 (UTC 00:00) Encountered errors: New York: HTTP code 200 Frankfurt: HTTP code 503 Singapore: HTTP code 503 Sydney: HTTP code 502
HetrixTools BOT 28/05/2022 11:51 AM
Uptime Kuma is now UP Downtime: 14 min Target: uptime.ibred.co Noticed at: 2022-05-28 01:51:33 (UTC 00:00)
HetrixTools BOT 28/05/2022 12:15 PM
Uptime Kuma is now DOWN Target: uptime.ibred.co Noticed at: 2022-05-28 02:15:36 (UTC 00:00) Encountered errors: New York: HTTP code 200 Frankfurt: HTTP code 503 Singapore: HTTP code 502 Sydney: HTTP code 502
12:20 PM
Uptime Kuma is now UP Downtime: 5 min Target: uptime.ibred.co Noticed at: 2022-05-28 02:20:48 (UTC 00:00)
Uptime Kuma BOT 28/05/2022 12:42 PM
My Discord Alert (1) Testing
12:42 PM
My Discord Alert (1) Testing
Uptime Kuma BOT 28/05/2022 3:15 PM
@Nishi-Breadotron eki Your website is currently broken, go fix it!
✅ Your service The other status page is up! ✅
Service Name
The other status page
Service URL
Visit Service
Time (UTC)
2022-05-28 05:15:08
Ping
1496 ms
Nishi-Breadotron eki 28/05/2022 3:15 PM
LOL
3:15 PM
wdym it works
3:15 PM
stupid
3:15 PM
oh nvm
3:15 PM
smh
3:16 PM
ah it was down
Uptime Kuma BOT 28/05/2022 3:17 PM
My Discord Alert (1) Testing
Nishi-Breadotron eki
ah it was down
Nishi-Breadotron eki 28/05/2022 3:17 PM
why didnt it sent message that it was down then smh
3:17 PM
oh i forgor to set it im the stupid
HetrixTools BOT 28/05/2022 3:35 PM
Uptime Kuma is now DOWN Target: uptime.ibred.co Noticed at: 2022-05-28 05:35:30 (UTC 00:00) Encountered errors: New York: HTTP code 503 Frankfurt: HTTP code 503 Singapore: HTTP code 503 Sydney: HTTP code 503
Nishi-Breadotron eki 28/05/2022 4:22 PM
Nooooo
4:22 PM
Oh I forgot to set it to not sleep
4:22 PM
I'm stupid smh
Uptime Kuma BOT 28/05/2022 7:29 PM
@Nishi-Breadotron eki @Bread Supporter
✅ Your service The other status page is up! ✅
Service Name
The other status page
Service URL
Visit Service
Time (UTC)
2022-05-28 09:29:05
Ping
1503 ms
HetrixTools BOT 28/05/2022 7:29 PM
Uptime Kuma is now UP Downtime: 3 hr 54 min Target: uptime.ibred.co Noticed at: 2022-05-28 09:29:30 (UTC 00:00)
HetrixTools BOT 28/05/2022 8:07 PM
Uptime Kuma is now DOWN Target: uptime.ibred.co Noticed at: 2022-05-28 10:07:33 (UTC 00:00) Encountered errors: New York: HTTP code 200 Frankfurt: HTTP code 503 Singapore: HTTP code 503 Sydney: HTTP code 503
Nishi-Breadotron eki 28/05/2022 8:08 PM
shut upo im trying to migrate to wsl2
Uptime Kuma BOT 28/05/2022 8:27 PM
@Nishi-Breadotron eki @Bread Supporter
❌ Your service Main website went down. ❌
Service Name
Main website
Service URL
https://breadtm.xyz
Time (UTC)
2022-05-28 10:27:55
Error
Flip UP to DOWN
Nishi-Breadotron eki 28/05/2022 8:28 PM
uhmmm
Uptime Kuma BOT 28/05/2022 8:28 PM
@Nishi-Breadotron eki @Bread Supporter
✅ Your service Main website is up! ✅
Service Name
Main website
Service URL
Visit Service
Time (UTC)
2022-05-28 10:28:21
Ping
167 ms
Nishi-Breadotron eki 28/05/2022 8:28 PM
OOPS
Deleted User 28/05/2022 8:28 PM
my man dont ping
8:28 PM
lol
Nishi-Breadotron eki 28/05/2022 8:28 PM
smh ok
8:28 PM
i accidentally enable flip up to down
Todd Floofley Breadfox 🦊 28/05/2022 9:11 PM
Oh well
Discord Developers #api-announcements SERVER 17/06/2022 1:29 AM
Happy Thursday everyone! Today we’re excited to roll out AutoMod, a new auto-moderation tool in Discord, along with new APIs and events for developers to build on top of it. Details about the API updates can be found in the Changelog and AutoMod docs: ✏️ https://discord.com/developers/docs/change-log#auto-moderation https://discord.com/developers/docs/resources/auto-moderation And information about the feature itself can be found in the Help Center article: https://support.discord.com/hc/en-us/articles/4421269296535-AutoMod-FAQ If you have any questions or feedback about the API updates, we'd love to have you at the event later today! The AutoMod team will be walking through the feature and API in detail, and answering the questions you've submitted. (edited)
Discord Developers #api-announcements SERVER 18/06/2022 9:49 AM
Updated Connection Property Field Names A teeny tiny API change for your Friday afternoon delight... The `$` prefix in identify connection properties are deprecated. Now instead of the `$os`, `$browser`, and `$device` fields, you should use `os`, `browser`, and `device`. Full details can be found in the change log:
https://discord.com/developers/docs/change-log#updated-connection-property-field-names
Do I need to do anything?? Nah, at least not on a lovely Friday afternoon like today. Discord's server will automatically resolve `$`-prefixed fields to their non-prefixed counterparts for now, so nothing is going to imminently break. However, with the next major API version, support for this resolution will go away and you'll need to update your app. When that deadline is near, we'll give ya another heads up. (edited)
Discord Developers #api-announcements SERVER 22/06/2022 8:31 AM
Removing Message Content in `AUTO_MODERATION_ACTION_EXECUTION` Event As you probably know, in API v10+, the `MESSAGE_CONTENT` (`1 << 15`) intent is required for your app to receive message content. Message content is currently being exposed in the `content` and `matched_content` fields for `AUTO_MODERATION_ACTION_EXECUTION` gateway events, so we're updating its behavior to match other content fields across the API. Starting next week, apps using API v10+ will start receiving empty strings for `content` and `matched_content` unless the app has the `MESSAGE_CONTENT` intent.
https://discord.com/developers/docs/change-log#message-content-in-automod-events
What do I need to do? If your app depends on `matched_content` or `content` in `AUTO_MODERATION_ACTION_EXECUTION` events, remove that dependency OR make sure your app is using the `MESSAGE_CONTENT` (`1 << 15`) intent. When will the change go in effect? The change will rollout next Monday, June 27. While we technically consider this a bug fix (as no message content should be exposed in API v10+), we realize it's also a breaking change so we're going to hold off deployment of the change until next week. (edited)
Discord Developers #api-announcements SERVER 30/06/2022 4:50 AM
Calculated Permissions in Interaction Payloads Say hey to the newest field on the block Interaction payloads now contain an `app_permissions` field whose value is the computed permissions for a bot or app in the context of a specific interaction. Similar to other permission fields, the value of `app_permissions` is a bitwise OR-ed set of permissions expressed as a string. `app_permissions` is meant to help identify the permissions your bot or app has without having to cache or store any server-specific permission settings or updates. It can be used before replying to an interaction in order to prevent any permission-related failures. Neat!
Change log entry: https://discord.com/developers/docs/change-log#calculated-permissions-in-interaction-payloads
(edited)
Discord Developers #api-announcements SERVER 30/06/2022 8:02 AM
Change to Bot Permissions in Interactions and Webhooks
️ This includes an upcoming breaking change for some bots
Starting on July 28, 2022 (in about a month), the way bot's permissions will be calculated for interaction responses and webhook execution will be updated. Instead of using the permissions calculated for `@-everyone`, permissions will be calculated specifically for the bot (including any overwrites). This change aligns with how bot's permissions are calculated when performing actions like posting a message to a channel. The permissions that may be affected for your bot are `ATTACH_FILES`, `EMBED_LINKS`, `MENTION_EVERYONE` and `USE_EXTERNAL_EMOJIS`. More details can be found in the change log entry.
Change log entry: https://discord.com/developers/docs/change-log#changes-to-bot-permissions-for-interactions-and-webhooks
‍ Updating your app If your bot wants to use any affected permissions when responding to interactions or executing a webhook, ensure that the bot was installed with them. If it wasn’t, your app with the bot should be re-authenticated with them before July 28. Using the new `app_permissions` field will hopefully make it a bit easier to fetch the contextual permissions your bot has. (edited)
Discord Developers #api-announcements SERVER 1/07/2022 6:39 AM
Hi all! We're pushing a change to `message.interaction` which will make its `name` field include subcommand group and subcommand if applicable (i.e. if the message is a response to a slash command with subcommand groups or subcommands). This change is not retroactive, and will affect messages from gateway as well as api. Please let us know if you see any issues invoking slash commands with subcommands. This is being reverted, sorry for the disruption! (edited)
Discord Developers #api-announcements SERVER 9/07/2022 7:07 AM
Min and Max Length for Command Options
Change log entry: https://discord.com/developers/docs/change-log#min-and-max-length-for-command-options
A little delayed, but last week the `min_length` and `max_length` fields were added to application command options. These fields let apps control the allowed length of text a user can input.
Discord Developers #api-announcements SERVER 12/07/2022 3:21 AM
Default `applications.commands` Scope for Bots After upgrading to the latest client (or when using the web), users installing an app with the `bot` scope will have the `applications.commands` scope automatically requested during the OAuth flow. Apps without the `bot` scope will still need to explicitly request the `applications.commands` scope. Moderators’ and admins’ ability to limit an app’s permissions for commands are unaffected by this change. Do I have to do anything? Nope! As commands become more essential for apps, we wanted to make it easier for devs to start installing and implementing them. If you're requesting the `bot` scope during OAuth installation, you're all set.
Discord Developers #api-announcements SERVER 12/07/2022 6:16 AM
Reminder: Upcoming Message Interaction Object Change Just a reminder about the minor breaking change to Message Interaction Objects rolling out on 19/07/2022 (mostly because I forgot to publish the last one ). This change updates the `name` field for message interaction objects to include subcommands and subcommand groups in its value (in addition to the existing top-level command). The `name` field is only on messages that are a response to an interaction without an existing message, so interaction responses are unaffected.
Original message with more info: https://discord.com/channels/613425648685547541/697138785317814292/992530580879183883
Discord Developers #api-announcements SERVER 14/07/2022 4:10 AM
Upcoming Prompt for Mods/Admins to Enable Slash Commands Next week, we’ll begin rolling out a prompt to users with the `Manage Server` permission in servers with one or more apps installed that have the `bot` scope but are not granted the `applications.commands` scope. The prompt will provide information about slash commands and include a button to enable them. Enabling slash commands will grant all eligible apps in the server the ability to install commands without requiring reinstallation with the `applications.commands` scope. This update has no effect on the existing permissions system. After enabling commands, the prompted user will be guided through toggling command permissions on a per-app basis in the `Integrations` tab within Server Settings so that users can invoke each app's commands. Users with the `Manage Server` permission will only be shown the modal once, but after that they can still enable slash commands through a sidebar banner. ️ Preview images in thread~
Discord Developers #api-announcements SERVER 14/07/2022 10:22 AM
Upcoming Permissions Change to Webhook Routes Hey fam. On Monday, 8 August 2022 we will begin requiring the `VIEW_CHANNEL (1 << 10)` permission for webhook routes which require `MANAGE_WEBHOOKS (1 << 29)`, to align with our documented behavior. We don't expect that many applications will be affected by this, but in case you are, please ensure you have updated permissions needed for accessing the following routes:

- `GET /webhooks/{webhook.id}`
- `DELETE /webhooks/{webhook.id}`
- `PATCH /webhooks/{webhook.id}`
- `GET /channels/{channel.id}/webhooks`
- `POST /channels/{channel.id}/webhooks`

Discord Developers #api-announcements SERVER 19/07/2022 8:33 AM
TLS 1.2+ required Discord has raised the minimum TLS version from 1.0+ to 1.2+ for all Discord websites, including the API. Transport Layer Security (TLS) is an encryption protocol that protects Internet communications. TLS 1.2 was released in August 2008 (along with Twilight: Breaking Dawn) and its requirement is in line with industry best practices.
Discord Developers #api-announcements SERVER 22/07/2022 4:12 AM
Hey everyone! We’ve got an announcement to share with you: we're testing a commands badge on bot profiles, which will help draw attention to the fact that a bot supports commands - as well as help educate users on features that bots have, which we know is something you all have requested. If your app has at least one global command, you will see this badge show today! What to know: The badge will be displayed on the bot's user profile The tooltip (when hovering over the badge) will say "Supports Commands" Clicking on the badge itself will direct users to a web page that describes in more detail what slash commands are, what additional features bots can support, and other FAQ. If you haven’t seen this page yet, it’s here: https://discord.com/blog/welcome-to-the-new-era-of-discord-apps All bots and apps are eligible! Slash commands, user commands, and message commands all count. All you need to do is register at least one global command for your app. (You can learn more about how to do this here: https://discord.com/developers/docs/tutorials/upgrading-to-application-commands) If your app already meets this criteria, congrats! Helping users understand how to get the most out of apps has been and will continue to be one of our top priorities. This is one thing we’re trying out, and there will be more coming soon! Enjoy. (edited)
Discord Developers #api-announcements SERVER 22/07/2022 11:23 PM
Hi everyone. There is currently an issue being investigated with interaction edits, deletes, and followups. This issue results in receiving `50027: Invalid Webhook Token` errors when trying to edit, delete, follow up, or take some other actions on interaction webhooks.
Discord Developers #api-announcements SERVER 23/07/2022 1:48 AM
Webhook token problem has been identified and we are working on rolling out a fix. We will update this message when it is resolved.
Discord Developers #api-announcements SERVER 23/07/2022 2:50 AM
The webhook token problem should be fixed. As a reminder, we saw a Snowflake length increase to 19 characters today! Snowflakes are 64 bit integers, so the max base 10 length is 20 digits now. (edited)
Discord Developers #api-announcements SERVER 2/08/2022 9:24 AM
Hey everyone An important reminder for developers of verified apps: the deadline for the new message content restrictions is Thursday, 1 September 2022, so you have 1 month left to make any remaining changes. This is a breaking change and will restrict access to message content for verified bots and apps across the Discord API, including in the `content`, `embeds`, `attachments`, and `components` fields. To prevent your app from breaking, you should update it to follow the new restrictions before the Thursday, 1 September 2022 deadline (most apps can use slash commands and message components to maintain functionality without needing access to message content), or you can apply for the message content privileged intent within the developer portal. For additional information about the change and how your app may be affected, you can read the Message Content FAQ: https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ
Discord Developers #api-announcements SERVER 10/08/2022 6:38 AM
Session-specific Gateway Resume URLs A new `resume_gateway_url` field has been added to the Ready gateway event to support session-specific gateway connections. The value of `resume_gateway_url` is a session-specific URL that should be used when resuming the gateway session after a disconnect. Previously, `wss://gateway.discord.gg` was used to connect and resume sessions, but should now only be used during the connection. ️ Starting on September 12, apps that aren’t using `resume_gateway_url` to resume gateway sessions will be disconnected faster than normal. `wss://gateway.discord.gg` will NOT stop working.
Change log entry: https://discord.com/developers/docs/change-log#sessionspecific-gateway-resume-urls
Note: At the moment, the value of `resume_gateway_url` will always be `wss://gateway.discord.gg` to give developers more time to adopt the new field. In the near future, the value will change to the zone-specific URLs (ex: `wss://us-east1-b.gateway.discord.gg`). (edited)
Discord Developers #api-announcements SERVER 17/08/2022 6:57 AM
Localized Application Commands Today, support for localized command names and descriptions will be rolling out across all* clients. To add localized commands to your app, you can use the `name_localizations` and `description_localizations` fields when creating or updating commands.

- For Android, only the new React Native client (https://discord.com/blog/android-react-native-framework-update) supports localized commands

✍️ Documentation: https://discord.com/developers/docs/interactions/application-commands#localization
Penguin fact: while penguins can't fly, they can jump out of the water up to 9ft in the air
(edited)
Discord Developers #api-announcements SERVER 23/08/2022 6:49 AM
Automatic Command Scope Migration Hey all Based on feedback from our scope migration experiment announced on 14/07/2022, we’ve decided to grant `applications.commands` to all apps with the `bot` scope. This will be rolling out within the next couple of days. How it’ll work When an admin opens a server, apps in that server will automatically be granted the `applications.commands` scope. If the app previously didn't have `applications.commands` and has at least one global command registered, the `@everyone` role's permission to use the app’s commands will be turned off by default. However, the admin will be shown a banner that prompts them to navigate to their server settings and toggle that permission. And just a reminder: as of 12/07/2022, any apps installed with a `bot` scope are granted the `applications.commands` scope by default.
Discord Developers #api-announcements SERVER 23/08/2022 8:26 AM
@@@ Slash Command Mentions @@@
Change log: https://discord.com/developers/docs/change-log#slash-command-mentions
Slash Command mentions are rolling out across all clients* this week! Similar to mentioning a user or channel, you can now mention a Slash Command to surface and share it. Simply use the new format `</NAME:COMMAND_ID>`, and the command will display inline as a clickable element. When a user clicks the mention, the command will auto-populate in their message input. Subcommands and subcommand groups can also be mentioned by using `</NAME SUBCOMMAND_NAME:ID>` and `</NAME SUBCOMMAND_GROUP SUBCOMMAND_NAME:ID>` respectively.

- For Android, only the new React Native client (https://discord.com/blog/android-react-native-framework-update) supports Slash Command mentions

Otter fact: Otters have a small pocket under each forearm that they use to store and carry their favorite rock wherever the world may take them. How relatable!
Discord Developers #api-announcements SERVER 31/08/2022 6:38 AM
Global Slash Commands in Bot Profiles As many of you noticed, we recently began rolling out global slash commands to bot profiles last week for verified apps. This week, we're rolling them out to 100% of verified apps With this update, a max of 5 of your app's most-used global slash commands are now visible in your bot profile (as long as your app is verified). These commands are directly invokable, making them more discoverable and usable for users across Discord How do I enable it? You don't have to do anything! As long as your app is verified and has at least one global slash command, a max of 5 will be displayed in your bot profile automatically. Can I change which commands appear in my bot profile? No, at the moment you can't control which commands are present. (edited)
Discord Developers #api-announcements SERVER 1/09/2022 8:06 AM
[Original Message Deleted] (edited)
Discord Developers #api-announcements SERVER 2/09/2022 5:05 AM
Message Content is Now a Privileged Intent ️ ️ Today, message content is becoming a privileged intent for verified bots and apps as previously detailed: https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ Any app that does not have the message content intent configured in its settings within the Developer Portal wiIl receive empty values in fields that expose message content across Discord's APIs. These restrictions do not apply for messages that a bot or app sends, in DMs that it receives, or in messages in which it is mentioned. The new message content restrictions will happen gradually throughout today, so you may not immediately encounter the new restrictions.
Details about the message content intent is in the docs: https://discord.com/developers/docs/topics/gateway#message-content-intent
➡️ If your app is verified or eligible for verification: Verified apps must be approved for the message content intent to receive message content. If your verified app isn’t approved, or doesn’t account for the new message content restrictions, it will break for users. Temporary Message Content Intent Toggle Verified apps or apps that have submitted for verification can temporarily opt-in to a grace period which will allow your app to continue receiving message content until October 1. However, if you opt-in to the grace period, your app will be prevented from joining any additional servers until you opt-out. You can toggle the temporary grace period at any time in your app's settings within the Developer Portal. After Oct 1, the toggle will be disabled and there will be no way to enable the message content intent without Discord approval.
Details about temporarily enabling message content: https://support-dev.discord.com/hc/en-us/articles/8561391080471
Applying for the Message Content Intent To be approved for the intent, your app must have a use case that requires message content as described in the Review Policy: https://support-dev.discord.com/hc/articles/5324827539479. You can apply for privileged intent from your app’s settings in the Developer Portal after it’s verified. Once your app is approved for the message content intent, you still must toggle the intent in your app’s settings on the Bot page under the “Privileged Gateway Intents” section. ➡️ If your app is not verified: For unverified apps (that aren't eligible for verification), Discord approval is not required to use the message content intent, but you still must enable the intent in your app’s settings within the Developer Portal. Existing unverified apps will automatically have the message content intent toggled on in their settings, but going forward, newly-created unverified apps will have the message content intent toggled off by default. ➡️ Gateway session reconnects: As part of the deployment of the new message content restrictions, the majority of connected bots (verified and unverified) will see their WebSocket gateway sessions invalidated and closed. Because of the amount of bots using the Gateway, these restarts will not happen all at once. If your bot is correctly implementing normal recovery logic of a dropped connection, you shouldn't see any issues. Most developer libraries have recovery logic built-in, but if you aren't sure you can check the library's documentation or ask its maintainers. For the Gateway session rollovers, bots will receive an `INVALID_SESSION` (Opcode `9`) and the `d` field will be set to `false`, indicating the session is not resumable and that your bot will need to reconnect to the Gateway and send a new Identify event.
Details about `INVALID_SESSION` and how to handle it: https://discord.com/developers/docs/topics/gateway#invalid-session
FAQs and Resources are pinned in #deleted-channel (in DDevs) (edited)
Discord Developers #api-announcements SERVER 14/09/2022 11:16 AM
Update to App Directory listing fields Hey all, just a quick update about recent changes to App Directory listing fields. There are now two fields where you can add Directory-specific descriptions for your app: Description and Expanded Description. Both fields are in your app's settings within the Developer Portal (if your app is verified). On the left sidebar under App Directory `>` Product Page: • Description is a short description for your app (up to 200 characters) that cannot contain markdown. This will be shown in places like search, and will be required for your app to appear in the Directory. • Expanded Description is a longer description for your app (up to 8k characters) that can contain markdown. It will be shown as the description on your actual App Directory listing. This field is optional, but if you don't provide an expanded description for your app, the listing will fall back to the Description field.
Snake fact: The fastest snake in the world is the Black Mamba, recorded at 12.5 miles per hour. It would take a Black Mamba about 2 years to slither to the moon!
(edited)
Discord Developers #api-announcements SERVER 15/09/2022 2:46 AM
Forum channels released to community servers As you may have seen on the blog, forum channels have started rolling out more broadly to community servers. Forum channels are a new channel type (`GUILD_FORUM`) that offer a more dedicated space for topics of discussion, composed only of threads. ✏️ API documentation: https://discord.com/developers/docs/topics/threads#forums Change log: https://discord.com/developers/docs/change-log#forum-channels-release And more information about forum channels can be found in the blog post: https://discord.com/blog/forum-channels-space-for-organized-conversation -- In our DDevs stage event at 4:00 AM, you can hear from an engineer from the Forum channels team and ask any questions you may have.
Discord Developers #api-announcements SERVER 22/09/2022 3:30 AM
AutoMod Spam and Mention Spam Trigger Types Hey all, a few new trigger types were added to AutoMod to protect against server spam and raids:

- `MENTION_SPAM` blocks messages that mention more than a set number of unique server members or roles. The limit can be controlled with the new `mention_total_limit` field.
- `SPAM` blocks links and messages that are identified as spam

Just like before, your app must have the `MANAGE_GUILD` permission to create, update, or delete any Auto Moderation rules. And feedback or questions can be answered in the #deleted-channel channel ✏️ API documentation: https://discord.com/developers/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types Change log: https://discord.com/developers/docs/change-log#automod-spam-and-mention-spam-trigger-types And more information about the new trigger types is in the blog post: https://discord.com/blog/new-anti-spam-raid-automod-safety-update Sticking with the animal speed theme...
Corgi fact: Corgis can run up to 25mph, just under the world sprinting record for humans (and twice as fast as black mambas)
(edited)
Discord Developers #api-announcements SERVER 14/10/2022 9:09 AM
New Select Menu Components ✍️ Change Log: https://discord.com/developers/docs/change-log#new-select-menu-components Documentation: https://discord.com/developers/docs/interactions/message-components#select-menus Four shiny brand new select menu message components have been added. The new components' options are automatically populated with the corresponding resource:

- User selects (type `5`)
- Role selects (type `6`)
- Mentionable (user and role) selects (type `7`)
- Channel selects (type `8`) They're defined in a similar way to the existing select menu component (now named the string select component), though their payload doesn't include `options`. Channel selects also have an additional `channel_types` field available to filter on channel type.
  Pelican fact: Oh pelicans pelicans, their beaks can hold more than their bellies can~ (up to 1 galloon in the stomach, and 3 galloons in the beak!)

(edited)
Discord Developers #api-announcements SERVER 18/10/2022 2:39 AM
As you may have seen this morning (https://discord.com/blog/building-the-future-of-discord), our App Directory is about to start rolling out! The experiment will be rolling out to a select number of users in the next 1-3 days. It will be accessible in server settings, which means you’ll only see it in servers where you have manage server permissions. We’ve also given the experiment to anyone with an app in the App Directory, so if you’ve completed your checklist and opted-in, you will see it in your support server starting tomorrow It’s been a long road and we’re so thrilled to be sharing this with you! (edited)
Discord Developers #api-announcements SERVER 19/10/2022 4:34 AM
Happy App Directory day! The App Directory experiment is now rolling out! If your app is approved for discovery, your support server will have access, and the experiment will be more widely available very very soon The Directory will be accessible in server settings, which means you’ll only see it in servers where you have manage server permissions.
Discord Developers #api-announcements SERVER 21/10/2022 11:04 AM
Delete Ephemeral Messages Change Log: https://discord.com/developers/docs/change-log#delete-ephemeral-messages Add even more ephemerality to your already-ephemeral messages by deleting them oOoooOOoOoo Ephemeral interaction responses and follow-ups can be deleted with a valid interaction token using `DELETE /webhooks/<application_id>/<interaction_token>/messages/@original` or `DELETE /webhooks/<application_id>/<interaction_token>/messages/<message_id>`.
Rabbit fact: Bunnies make noises, but they are very quiet. Content rabbits purrrrr by gently grinding their teeth together, and excited rabbits oink
Discord Developers #api-announcements SERVER 9/11/2022 8:24 AM
Automod Regex Support Change Log: https://discord.com/developers/docs/change-log#add-automod-regex-support Automod `KEYWORD` rules now support the ability to catch unwanted messages using regex patterns. This is available through a new `regex_patterns` field within `trigger_metadata` (https://discord.com/developers/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata). Regex patterns are a powerful way to describe many keywords all at once using one expression. Only Rust flavored regex is currently supported, which can be tested in online editors such as https://rustexp.lpil.uk/.
Hippo fact: Hippos can sleep underwater, because they have a natural reflex that lets them come up for air, take a breath, and sink back down without waking up
Discord Developers #api-announcements SERVER 10/11/2022 9:55 AM
Upcoming Change for Age-Restricted Commands Next Wednesday, November 16, we’re making updates to how age-restricted commands appear and are used in Discord. As some may know, commands have accepted an `nsfw` field in the API for some time, and we're ready to release the next part of that feature which will hide those commands from underage users on Discord.
ℹ️ Apps in the directory are unaffected—as a reminder, age-restricted content is not allowed in discoverable apps.
In line with Discord’s other policies on age-restricted content, here’s how commands marked `nsfw` will work. Users who are 18 or older can opt in to age-restricted commands by going to User Settings > Privacy, and enabling the age-restricted commands toggle (which will be turned off by default).

- In servers, these commands will only be visible and usable within age-restricted (`nsfw`) channels
- In DMs, these commands will be visible and usable if

- The user is 18 years or older

- They have turned on age-restricted commands within Discord settings
- Age-restricted commands will not show as popular commands on app profiles

You can see some screenshots of how this will work in the thread attached to this message. In the future, we will also start automatically tagging commands as `nsfw` if they fall within our policy but are not properly flagged. We really appreciate those of you who have been asking for this feature, and your commitment to helping us keep Discord safe Help Center article: https://support.discord.com/hc/en-us/articles/10123937946007 ❓ If you have questions, feel free to ask them in #deleted-channel
Discord Developers #api-announcements SERVER 11/11/2022 5:30 AM
✨ Say hello to the new "Active Developer" badge! ✨ We know you've all been wanting a way to proclaim yourself a Discord Developer - so starting now you can head over to the Developer Portal to grab yours! Here are some quick things to know: This badge is for active developers - all you need in order to qualify for this badge is to have at least 1 app that has had a global application command used in the last 30 days! Note: if you have an 'Early Verified Developer' badge, that is not going away and will remain on your profile. You'll also sign up for our new Developer News feed! This will make it even easier to keep up with the latest news. We'll be sending the first edition out in the next few weeks! You can run this check here: https://discord.com/developers/active-developer. Just select which app you want to get checked from the dropdown! Beaver fact: Beavers secrete castoreum, which is used to bring out flavor in vanilla ice cream and add fruity notes to perfumes (edited)
Discord Developers #api-announcements SERVER 18/11/2022 6:20 AM
Upcoming Change for Command Permissions Based on feedback, we're making some updates to permissions for application commands to simplify permission management and to make command permissions more closely resemble other permissions systems in Discord. Server admins can begin to opt-in to the command permission changes outlined in the change log on a per-server basis starting on December 16, 2022. However, changes will not be applied to all servers until late January or early February.
Change log: http://discord.com/developers/docs/change-log#upcoming-application-command-permission-changes. This includes many more context and details about whether you'll be affected + how to update your app accordingly.
Most apps will be unaffected by this change, but if your app uses the `PUT /applications/<application_id>/guilds/<guild_id>/commands/<command_id>/permissions` endpoint, you may need to make updates.
There are two main changes included: 1️⃣ The logic used to apply permission configurations to a user in a given context within Discord clients. The new command permissions configuration behavior allows command-level permissions, app-level permissions, and `default_member_permissions` to work together rather than independently.

- `default_member_permissions` acts as a “default” that a developer can set when creating or updating a command

- App-level permission configurations (typically set by admins) now act as the "base" configuration

- Command-level permission configurations (typically set by admins) now act as an “override” of the app-level

2️⃣ A new `APPLICATION_COMMAND_PERMISSIONS_V2` guild feature flag to indicate whether that guild is using the old permissions logic or the new (upcoming) logic. And now....a flowchart to help understand and visualize how permissions configurations are used by Discord clients (it's huge, so you might want to click "Open Original" to see all of it) (edited)
Discord Developers #api-announcements SERVER 13/12/2022 4:27 AM
Application Connection Metadata and Linked Roles We're really excited to announce that a new feature called ✨ Linked Roles ✨ is starting to roll out today and will continue to over the next few weeks! Linked Roles allow admins to assign roles automatically based on users' information in 3rd party services (like having a verified account, having certain stats, or having more than a certain number of followers). Apps can plug-in to Linked Roles by configuring new role connection metadata. Read more in the resources below:
Overview page: https://discord.com/build/linked-roles
Documentation: https://discord.com/developers/docs/resources/application-role-connection-metadata
Getting started guide: https://discord.com/developers/docs/tutorials/configuring-app-metadata-for-linked-roles
✍️ Blog post: https://discord.com/blog/connected-accounts-functionality-boost-linked-roles
Along with this rollout, we're adding a new verification tier for apps that want to use Linked Roles in an official capacity. Note that this will be scaling up early next year, so stay tuned to details on how you can make your connections apps official. (edited)
Discord Developers #api-announcements SERVER 21/12/2022 6:19 AM
Stricter Type Enforcement for Falsy Values Starting early next month (January 2023), falsy field values must match that field’s specified type. If your app is not passing correctly-typed falsy values for all API fields, you should update your app or you will begin to encounter new errors. An exception to the new stricter type enforcements is boolean-typed fields, which will accept `0` in addition to `false` (though using `false` is still recommended in most cases). Previous behavior Though the behavior wasn’t documented, some fields previously allowed any type of falsy value and would resolved them all to `null`. For example, an empty string passed in a list-typed field would resolve to `null`. Updating your app If your app is passing any falsy values that do not correspond to that field’s type, update your code so that it matches. For example, if your app is passing an empty list for a string-typed field, update that code to instead pass an empty string.
Reindeer fact: The back feet of reindeer make a clicking noise as they move caused by the friction of their tendons slipping over bone. This click clack lets reindeer stay near their herd even in harsh winter conditions. (bonus fact: reindeer sometimes make a cute yawn and wiggle their chins afterwards )
(edited)
Discord Developers #api-announcements SERVER 10/01/2023 9:42 AM
Thread Member Details and Pagination Support
✍️ Change log: https://discord.com/developers/docs/change-log#thread-member-details-and-pagination
A new `member` field, which contains general user information about a thread member, was added to the thread member object. This field will only be present when the new `with_member` field is set to `true` when calling List Thread Members (`GET /channels/<channel_id>/thread-members`) or Get Thread Member (`GET /channels/<channel_id>/thread-members/<user_id>`). In addition to exposing additional info about a thread member, setting `with_member` will make the results of List Thread Members paginated. You can paginate through the results using the `after` and `limit` fields. Starting in API v11, all results returned by List Thread Members will be paginated. Additional details are in the change log and documentation~
Clownfish fact: Clownfish (or anemonefish) live in colonies with a strict hierarchy, at the top of which is a female. If that female dies, the most dominant male in that colony will transition into female and assume the top of the hierarchy.
Discord Developers #api-announcements SERVER 10/01/2023 2:03 PM
Hi all! Update on stricter type enforcement for falsy values (previously announced in https://discord.com/channels/613425648685547541/697138785317814292/1054837953752486018): This change is beginning to roll out now. If you see any issues with input that you think is correctly typed, let us know in #deleted-channel. Thanks! edit: This is now rolled out. (edited)
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
Discord Developers #api-announcements SERVER 19/01/2023 11:38 AM
New `GUILD_AUDIT_LOG_ENTRY_CREATE` Gateway Event
✍️ Change Log: https://discord.com/developers/docs/change-log#guild-audit-log-events
A new `GUILD_AUDIT_LOG_ENTRY_CREATE` event was added, which is sent when an audit log entry is created in a server. `GUILD_AUDIT_LOG_ENTRY_CREATE` requires the `VIEW_AUDIT_LOG` permission and passing the `GUILD_MODERATION` (`1 << 2`) intent when connecting to the Gateway.
Bee fact: When honey bees find a delectable food source, they communicate the location of it to other colony members by dancing (called a waggle dance). Those members then dance for others, and so on until the entire colony knows of the location.
Discord Developers #api-announcements SERVER 11/02/2023 10:41 AM
Increase Limits for AutoMod Keywords
✍️ Change Log: https://discord.com/developers/docs/change-log#increase-auto-moderation-keyword-limits
Two minor updates for AutoMod: The maximum number of `KEYWORD` rules per guild was increased to 6 (previously 5) The maximum length for `keyword_filter` and `allow_list` fields were increased to 60 (previously 30)
Discord Developers #api-announcements SERVER 14/02/2023 7:32 AM
Hey everyone, we're aware there are some errors with application commands endpoints due to a change we released, we're working on rolling it back ASAP. Edit: The incident should be resolved now. (edited)
Discord Developers #api-announcements SERVER 2/03/2023 10:13 AM
IP Discovery Upcoming Change We recently pushed out a change related to Voice Connections that broke apps sending 70-byte UDP packets to the voice server when using IP Discovery. While the documentation and deprecation were updated in December 2019, there wasn't communication around the the change starting to roll out so we've temporarily reverted the change to give developers more time to handle the breaking change. ️ Starting Thursday, 16 March 2023, all apps with Voice Connections using IP Discovery must send 74-byte UDP packets. IP Discovery requests sending the deprecated 70-byte packet will no longer receive a response. Some 3rd party libraries may be needed to be updated to support this change, so if your app uses Voice Connections and a 3rd party library, check with the maintainer(s) to see if it sends the updated packet and/or whether you need to update the library version you're using. Read the IP Discovery documentation for more information about the UDP packet to send: https://discord.com/developers/docs/topics/voice-connections#ip-discovery
Discord Developers #api-announcements SERVER 8/04/2023 8:01 AM
Update on March Verification Requests Hey everyone , here’s a quick announcement for those of you who hadn’t heard back after applying for bot verification or privileged intents during the month of March 2023. Beginning early last month, there was a bug in our system that may have resulted in tickets not being created after a bot verification form or privileged intent form was filled out. See our previous message here for more details: https://discord.com/channels/613425648685547541/696891424041598978/1086403616904073226, Fortunately, we have since resolved this issue, and new applications for both intents and verification are processing without issue. We unfortunately are unable to recover applications that were lost as a result of this bug. If you applied for verification during March 2023 and you believe you’re impacted, please send in a ticket containing your bot’s ID so we can determine whether or not your ticket was created. You can create a ticket here: https://support-dev.discord.com/hc/en-us/requests/new We apologize for any inconvenience this created and are aiming resolve this as quickly we possibly can. Thanks for your patience and understanding. (edited)
Discord Developers #api-announcements SERVER 15/04/2023 4:46 AM
Bot users added to all new apps
✍️ Change Log: https://discord.com/developers/docs/change-log#bot-users-added-to-all-new-apps
Starting today, bot users will be added to all newly-created apps. Existing apps will not be affected by this change. If your app doesn't need or want a bot user added during installation, you can refrain from using the `bot` scope. Additional details and links to relevant documentation are in the change log entry.
Discord Developers #api-announcements SERVER 21/04/2023 3:29 AM
AutoMod Badge for Apps Since AutoMod launched last year, moderation apps have been integrating with its APIs to create custom moderation experiences for Discord mods and admins. The AutoMod APIs help simplify message scanning by letting developers create custom rules for servers, while improving their users' experience with built-in AutoMod features like moderating messages before they're sent. And today....we're excited to let you know we've released an AutoMod badge to showcase AutoMod-powered apps to Discord users. The badge will appear on a bot's profile when it has created 100+ AutoMod rules. Check out the official blog post about integrating with AutoMod: https://discord.com/blog/supercharge-your-moderation-with-automod-in-your-apps ❓ Or the help center article for more specifics on the badge: https://support-dev.discord.com/hc/en-us/articles/13847462843543 (edited)
Developers, Supercharge Your Moderation with AutoMod
Today, we’re inviting developers on Discord to supercharge their own moderation applications by integrating directly with AutoMod. Read more to learn what the future of moderation apps on Discord holds!
Discord Developers #api-announcements SERVER 28/04/2023 3:10 AM

# Hey DDevs!

Today we are launching expanded markdown (lists, headers, and masked links) to 100% of all guilds and users. You can read more about it here Support Article Not just users but also Apps/Bots/Webhooks can take advantage of this new functionality! As always, everything we do is a work in progress. We are still open to feedback and bug info, and we welcome you to provide both.
Discord Developers #api-announcements SERVER 29/04/2023 7:52 AM
Small update on expanded markdown We had to roll it back yesterday to patch some issues. We will most likely be bringing it back sometime next week. soon Have a good, markdown-less weekend! Animal fact of the week: a group of rhino is called a "crash" (edited)
Discord Developers #api-announcements SERVER 4/05/2023 4:41 AM
Impact of Unique Usernames on Apps and Bots Today we announced that Discord’s username system is changing. Discriminators are being removed and new, unique usernames (`@name`) and display names are being introduced. These changes will make it easier for users to connect with their friends and give more control over identity on Discord. You can visit https://discord.com/blog/usernames to hear from one of our founders about why usernames are changing, or read more details about how changes to the username system affects non-bot users at https://dis.gd/usernames More details for developers (including an FAQ) are in the Help Center article: https://dis.gd/app-usernames Below is an overview of how apps and bots will be affected by the username change. More details for developers, including exact dates, will be communicated soon. Changes to bot users on Discord 1️⃣ We recently made a change to add bot users to all newly-created apps. During the username migration, all apps without a bot user created before April 14 will have a bot user automatically added. If your app doesn’t require a bot user, you can skip adding the `bot` scope during installation. 2️⃣ After migration, developers will no longer be able to directly set bot usernames or bot icons. The bot user’s icon will always be the same as the App Icon. Bot usernames will be determined differently for verified and unverified apps:

- Verified apps: Bot usernames will be determined by the Application Name. When an unverified app goes through the verification process, a username created from the Application Name will be given to the bot user.
- Unverified apps: Bot usernames will be randomized for new and existing unverified apps. This does not affect the Application Name. 3️⃣ Application Names (the `Name` field on the General Overview page within the app’s settings) will be used as the Display Name for an app’s bot user. This means developers cannot manually update the Display Name for a bot user without updating the Application Name. Server nicknames are unaffected by this change. 4️⃣ The Discord client will be updated to only display Application Names in most surfaces, including the bot profile and in the search interface. The client changes will allow all Discord apps, verified and unverified, to use their Application Name as the identity for their app (and bot) across Discord. Migration of verified app usernames

Most verified apps with Application Names which can be automatically migrated to the new username system have been reserved. No user will be able to claim the reserved username, and during migration the reserved name will be automatically given to the app's bot user. Verified apps that cannot be automatically migrated or wish to change their Application Name for another reason will be able to make a one-time change at the time of migration. Identifying migrated users To keep clients backwards-compatible, users that are migrated to the new username system will have a single zero (`#0`) discriminator. This will not appear in the client, but will be in payloads your app receives. After the migration to the new username system is complete, the `0` discriminator will be removed. Preparing your app for username changes

- Remove any logic that depends on discriminators for Discord users. Apps should continue using user IDs to uniquely identify Discord users in their code. Make sure to account for the temporary `#0` discriminator that updated users will have when updating your code.
- Be prepared for your username change. That includes in code, or anywhere else you may reference your bot username.
- If your app is verified, stay tuned for details about migration dates and how to perform a one-time update for your Application Name/bot username.

Discord Developers #api-announcements SERVER 13/05/2023 4:44 AM
Updated max character limit in app names Application names are now limited to 32 characters when you're creating a new app or updating the name of an existing app. This change does not currently affect apps with existing names longer than 32 characters.
*This change is related to upcoming username changes for apps and bots, which you can read more about at https://dis.gd/app-usernames*
Discord Developers #api-announcements SERVER 6/06/2023 4:26 AM
Follow-up on Unique Usernames for Apps Hi everyone, We recently announced upcoming changes to Discord’s username system. While that new system continues to roll out to users, we have updated information to share with you all about the bot side of this transition: application names and bot usernames will remain on the discriminator system. Below are details on how this may simplify things for you and what you still need to know about what is changing. What does this mean?

- Bot usernames and avatars can still be changed independently of app names and icons, using the current system. This may change in the future.
- Bot usernames will not change immediately, and will remain in the Username#1234 format with a discriminator.
- App names and bot usernames will not be required to be unique, even for verified apps.
- Unverified apps will not be assigned randomly generated bot usernames.

Changes that are staying, and looking into the future:

- Bot users will continue to be automatically added to newly-created applications.
- Application names will continue to be limited to 32 characters.
- We will be maintaining a blocklist of some application names that are high-risk for impersonation and abuse.
- In the future, we still plan to use application names as the identity for your app and bot across Discord.

The team is focused on ensuring that the username transition is smooth for all users and will continue to monitor how applications / bots interact with the new system. For more information, refer to the help center article: https://dis.gd/app-usernames
Discord Developers #api-announcements SERVER 29/06/2023 3:46 AM

# Hey DDevs! (again)

- Today we are re-rolling out masked links (as part of the new markdown) to 5% of all guilds, with the intention it will be out to 100% in the coming weeks.

- You can read more about it here Support Article

- We are aware of the security and abuse vectors relating to this feature, and are keeping a close eye on reports. Please report to CX/Support (https://support.discord.com/hc/en-us) if you see any issues.

(edited)
Markdown Text 101 (Chat Formatting: Bold, Italic, Underline)
Want to inject some flavor into your everyday text chat? You're in luck! Discord uses Markdown, a simple plain text formatting system that'll help you make your sentences stand out. Here's how to d...
Discord Developers #api-announcements SERVER 3/08/2023 8:05 AM

# ️ OpenAPI Spec Public Preview

Today, we’re introducing an OpenAPI 3.1 spec in public preview to make it easier and more reliable to develop with the HTTP API. While our current developer documentation requires manual reviews and updates, the OpenAPI spec is generated from the source code which means it better reflects the nooks, crannies, and nuances of the Discord API. You can find details about the spec in the `discord-api-spec` repository on GitHub. You can also explore our Postman collection (which was generated using the spec) to easily discover and test HTTP endpoints.

## What is an OpenAPI specification?

From the OpenAPI Specification website: “The OpenAPI Specification defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection”.

## Why is it in public preview?

While we’re excited to share the spec with the community, we’re still making improvements and refining some technical details in the spec. During the public preview, there may be bugs and unannounced breaking changes. If you see something that looks incorrect or can be improved, open an issue on GitHub.
Discord Developers #api-announcements SERVER 11/08/2023 5:34 AM

# Setting Activity State for Bot Users

The `state` field in activity objects can now be set when you're updating presence for a bot user. When the activity's `type` is Custom (`4`), the value of `state` will become the custom status text for the bot user. For other activity types, it will be displayed as additional data under the activity's name. ✍️ Read the Change Log
Discord Developers #api-announcements SERVER 12/08/2023 6:36 AM

# Embed Debugger ‍

We've released a new Embed Debugger tool that shows you how a URL's metadata will be parsed and rendered as a link embed within the Discord client. Use it to preview your site's embed, or debug why your site's link embed isn't working as expected. (edited)
Discord Developers #api-announcements SERVER 25/08/2023 5:15 AM

# Team Member Roles

You can now select roles other than admin when inviting users or configuring members of a team. There are four role types (`owner`, `admin`, `developer`, or `read-only`) that a team member can now be assigned based on what information and actions they need access to. ✍️ Read details in the Change Log (edited)
Discord Developers #api-announcements SERVER 23/09/2023 6:54 AM

# Default Values for Auto-populated Select Menus

A new `default_values` field was added for user (`5`), role (`6`), mentionable (`7`), and channel (`8`) select menu components. `default_values` is a list of default value objects, which includes an `id` of the user, role, or channel and a corresponding `type`.
ℹ️ The UI updates to support default values in auto-populated select menus are not supported in older client versions, so if you're running into issues try updating your client!
✍️ Read details in the Change Log
Discord Developers #api-announcements SERVER 27/09/2023 4:32 AM

# Premium App Subscriptions Available in the US

Starting today, eligible US-based developers can monetize their verified apps with App Subscriptions. App Subscriptions let you to charge your users for premium functionality with a recurring, monthly subscription. To support App Subscriptions, apps now have access to:

- Manage subscription SKUs in the Developer Portal
- View monetization analytics in the Developer Portal
- Team owners can setup and manage payouts in Developer Portal
- New endpoints for working with SKUs and Entitlements
- New `PREMIUM_REQUIRED (10)` interaction response type is available to prompt users to upgrade
- New `entitlements` field, which is an array of entitlement objects, available in interaction data payloads when receiving and responding to interactions To learn more about eligibility details and how to enable monetization for your app, check out the Monetization Overview. ✍️ Change Log

For a full list of features and API changes, read more details in the Change Log. Feedback & Bug Reports For feedback and bug reports on monetization features, please submit issues on GitHub. (edited)
Discord Developers #api-announcements SERVER 30/09/2023 4:15 AM

# New Authenticated Attachment URL Parameters

To improve security of Discord's CDN, attachment CDN URLs have 3 new URL parameters: `ex`, `is`, and `hm`. Once authentication enforcement begins later this year, links with a given signature (`hm`) will remain valid until the expiration timestamp (`ex`). ️ Attachment CDN URLs have already started following the new pattern, so your app will begin to encounter the new parameters in attachment CDN links, but authentication is not being enforced until later this year. More details about when authentication will start to be enforced will be shared in the upcoming weeks.

## Details about authentication parameters

- `ex`: timestamp indicating when the attachment URL will expire, after which point you'd need to retrieve another URL (by doing something like retrieving a message via HTTP). More details to come about the length of time this will be by default.
- `is`: timestamp indicating when the URL was issued
- `hm`: unique signature that remains valid until `ex`.

## Handling authentication parameters

### When links expire

To access the attachment CDN link after the link expires, your app will need to fetch a new CDN URL. The API will automatically return valid, non-expired URLs when you access resources that contain an attachment CDN URL, like when retrieving a message. The client behavior is not changing and will refresh posted URLs to be automatically valid, so your app doesn't need to worry about refreshing URLs itself if the link was valid at the time of posting.

### In messages your app sends

The behavior in the client will remain the same. Links posted in the client will be automatically updated if the link was valid at the time of posting, so you don't need to update your message's content when it includes an attachment CDN link (in cases like apps reposting images using CDN links).

### If your app needs access to the content

If your app requires access the content from an attachment CDN link, you should fetch the contents from the valid CDN link and upload them to a secure, independent host that your app maintains access to.
Discord Developers #api-announcements SERVER 18/10/2023 9:45 AM

# Global Rate Limit added to `discordapp.com/*`

ℹ️ We have added a global rate limit for API requests made to `discordapp.com/*` and may further restrict requests in the future. To limit impact on your app, please make sure you are making calls to `discord.com/*`. This does not apply for `cdn.discordapp.com`. Refer to the API Reference for more info on which url(s) to use when building on the REST API

- February 14, 2022 Change Log: Requests to v10 and higher will no longer be supported on discordapp.com (this does not affect cdn.discordapp.com)
- May 4, 2020 Change Log https://discord.com/channels/613425648685547541/697138785317814292/706944540971630662

(edited)
Discord Developers #api-announcements SERVER 4/11/2023 2:35 AM

# Fix Interaction Response Permissions

The behavior for message edit interaction response actions like updating interaction responses and sending follow-up messages have been updated to follow a bot user's permissions. Previously, some message edit interaction response actions would use the default permissions rather than a bot user's permissions. ✍️ Read the Change Log
Dino fact: Oviraptor was a Theropod whose name means "egg thief" because its fossils were found around egg nests. But...we eventually learned that the nests belonged to the Oviraptors
Discord Developers #api-announcements SERVER 1/12/2023 9:38 AM

# More Ways to Test Premium App Subscriptions

We've made it easier for developers to test their app subscriptions without having to use real payment methods.

- Team members will automatically receive a 100% discount on a subscription for your app, allowing you to test the end-to-end payment flow
- Developers can create and delete test entitlements to toggle access to an application's premium features Read more about Testing your App Subscriptions Implementation for details. ✍️ Read the Change Log

Discord Developers #api-announcements SERVER 2/12/2023 10:20 AM

# Developer Survey

Calling all developers! Ready to make a difference? We're thrilled to announce that our annual developer survey is live now to gather your valuable feedback and insights. Your opinions matter greatly to us, and we're committed to making our developer offerings even better with your input. ➡️ Log in to your developer portal and find the survey link in the navigation bar. You may also see a special winter surprise! ❄️ It only takes a few minutes to make a big impact! Thanks in advance for completing the survey.
Discord Developers #api-announcements SERVER 6/12/2023 5:18 AM

# Experimenting with End-to-End Encryption for Voice & Video

As outlined in a blog post earlier this year, we are experimenting with end-to-end encryption (e2ee) for voice and video channels. During this testing phase, there is nothing developers need to do to support end-to-end encryption. Voice channels will automatically downgrade to currently documented, non-e2ee protocols when a bot user joins the channel. This is transparent to the connecting client but may result in a slight delay between establishing a connection and receiving audio. We will be continuing our testing and will share updates along with developer documentation and sample code once it is available. ✍️ Read the Change Log
Discord Developers #api-announcements SERVER 9/12/2023 5:06 AM

# Updates to CDN-hosted images on App Directory profiles

Due to upcoming CDN changes, we are making updates to images within App Directory profiles. Going forward, all new and updated URLs for images in App Directory profiles must be hosted outside of Discord’s CDN. This includes images in the Images tab (under Media in your app's settings) and within expanded descriptions.

### If you have images in the Images tab

Previously, using Discord attachment CDN URLs was allowed in the Images tab. To make migration easier, existing Discord CDN-hosted images in the Images tab have been migrated off of the CDN, so no action is needed on your part. Going forward, any Discord attachment CDN URLs will be rejected.

### If you have images in the Expanded Description

Previously, using Discord attachment CDN URLs was allowed in the expanded description. Going forward, they will not be allowed. To continue supporting images in expanded descriptions, non-CDN URLs are supported going forward. ️ By the end of this year, Discord attachment CDN-hosted images in your expanded description should be migrated elsewhere, and their URLs should be updated in your app's settings accordingly. (edited)
Discord Developers #api-announcements SERVER 19/12/2023 6:28 AM

# Developer Survey Closes Friday

Did you see our announcement earlier this month? https://discord.com/channels/613425648685547541/697138785317814292/1180279145515716738 Our annual developer survey is currently live to gather your feedback and insights. It will close this Friday. ➡️ To complete the survey, log in to your developer portal and find the link in the navigation bar. Thank you!
Discord Developers #api-announcements SERVER 20/12/2023 9:07 AM

# Stricter Limit on Number of Embed Fields

Embed objects are now strictly limited to 25 embed fields. If you pass more than 25 fields within an embed's `fields` property, you'll get an error. Previously, only the first 25 embed fields would be displayed within the embed, but no error was returned.
Snowflake fact: The largest flake ever recorded was 15 inches across and 8 inches thick, spotted back in 1887 in Montana (but there isn't much corroborated evidence for it, so take this fun fact with a pinch of salt).
(edited)
Discord Developers #api-announcements SERVER 6/01/2024 7:17 AM
Small update to start off 2024 We've aligned the API's character limit for the Guild `description` field with the app's limit of 120 characters. This change addresses the previous discrepancy where the API allowed bypassing the client's character limit for this field. The new limit is now reflected in our Open API spec.
Discord Developers #api-announcements SERVER 19/01/2024 5:27 AM
Interactions sent with `Transfer-Encoding: chunked` From 13/01/2024 9:17 AM to 19/01/2024 4:30 AM, we erroneously delivered interactions with chunked encoding. This has now been resolved.
Discord Developers #api-announcements SERVER 26/01/2024 6:25 AM

# Authenticated Attachment URL Parameters Update

Hey everyone I'm back (once again), here with some minor updates and clarifications about the authenticated attachment URL parameter change we posted about last year (you can read more in the original and follow-up posts). This post includes some important information and dates, as well as answers some questions we've repeatedly received from developers.

## When is the change going out?

We refined the timeline for the gradual rollout of the URL parameter change: 1️⃣ On 2/02/2024, signature enforcement will begin to be applied for any new attachment uploads to Discord. 2️⃣ On 23/02/2024, we're planning to apply signature enforcement to previously uploaded attachments.

## Update to App Directory CDN Links

Previously, we posted an update that said net-new attachment links in the Images tab and all attachment links in the Expanded Description would no longer be allowed. However, based on your feedback, we've rolled back this change to allow more flexibility for images in the App Directory. Since the change is rolled back, you can use Discord attachment links in your app's Images tab and Expanded Description going forward, and they will be automatically re-signed like other attachment links in the client. Sorry for the confusion, but we believe the end result is a net-positive for developers and Directory pages.

## FAQ

What is the expiration window for attachment links? Initially, URLs will expire after 14 days, and new ones will be issued every 7 days. We've chosen a longer expiration time to simplify the rollout. However, this may be reduced post-launch so you should use continue using the `ex` URL parameter mentioned in the original post to determine when a specific link is expected to expire. Are these dates final? We aim to stick to the above dates, but we'll be closely monitoring the impact on users and developers to ensure a smooth transition. If needed, we might modify the rollout plan, but we would communicate any changes here. How should I handle this change in my app? Please refer to the original post and follow-up post for more information on handling the change for your app.
Discord Developers #api-announcements SERVER 27/01/2024 6:13 AM

# Update to Max Number of Guild Integrations

Guilds can no longer add more than 50 integrations. An error will appear or be returned if you try to add more than the max number of integrations. Guilds that currently have more than 50 integrations are not affected by this change at this time. To see all integrations in a guild, you can view the Integrations tab in Server Settings or use the Get Guild Integrations endpoint. Edit: To clarify, webhooks of any kind are not considered as integrations. (edited)
Discord Developers #api-announcements SERVER 3/02/2024 4:55 AM

# Masked Link Support in Expanded Description

Keep your App Directory page sleek with new masked link support. The Expanded Description field on profile pages now support masked links
Discord Developers #api-announcements SERVER 7/02/2024 10:37 AM

# bots can now have animated avatars

excited to see all the creative and genuinely cool avatars y'all come up with for your bots. please don't do anything too cursed. good luck, have fun! technical notes: just upload an animated avatar through `PATCH /users/@me` like you would a regular avatar. same constraints apply to bots here as they do user accounts w/ nitro.
Discord Developers #api-announcements SERVER 2/03/2024 7:12 AM

# User Interaction Response Deletion

❗ EDIT: due to feedback, this change is being temporarily rolled back.
On desktop and web, Discord users can now delete responses to interactions they initiated. This change isn't available on mobile just yet, but will be included in the next release. (edited)
Discord Developers #api-announcements SERVER 2/03/2024 7:58 AM

# Upcoming Permissions Change for Pruning

Starting on Saturday, 16 March 2024, the Get Guild Prune Count and Begin Guild Prune endpoints will require the `MANAGE_GUILD` permission alongside the existing `KICK_MEMBERS` permission. See the change log PR draft for details.
Discord Developers #api-announcements SERVER 16/03/2024 4:37 AM

# Bot Banners

Hey everyone! Today we’re releasing bot banners! You’re now able to add a banner image (static or gif!) to your bot. You can access editing your banner from the bot tab in the developer portal or the API. Note that animated banners can only be updated through the API at this time. This will appear in your bot profile, mobile, and other new places coming soon! Enjoy! (edited)
Discord Developers #api-announcements SERVER 19/03/2024 4:25 AM

# User-Installed Apps are in Preview

## Apps can now be installed to users

making them easier to install, discover, and access across Discord. By default, user-installed apps can be used across all of a user's servers, within their (G)DMs, and in DMs with an app's bot user. Apps can be updated to support user installation on the new Installation page in your app's settings. During the preview, interaction responses for the user installation context will be forced to be ephemeral in servers with over 25 members. There also may be changes to the new fields discussed in the change log before general availability. ✍️ Read all of the juicy technical details, limitations, and known issues in the change log, or follow the tutorial to get started.
Discord Developers #api-announcements SERVER 19/03/2024 5:19 AM

# Developers can now build Activities!

Activities are interactive, multiplayer experiences that run in an iframe in Discord! Think games or social experiences running right inside of Discord. A few examples you might have already used are Putt Party, Sketch Heads, and Jamspace Whiteboard!

## Developer Preview: Building Activities with the Embedded App SDK

In order to make the communication between your experience and Discord possible, we've introduced the Embedded App SDK to assist in communicating between your app and the Discord client.

- New Discord Activities developer docs with a tutorial, code samples, development guides, and design principles.
- The Embedded App SDK is now available via npm and GitHub.
- The Embedded App SDK Reference is now available.

During the preview, Activities in development can only be launched in servers with fewer than 25 members. See the other public preview limitations here. ✍️ Read all about this developer preview in the change log, or follow the tutorial to get started.
Discord Developers #api-announcements SERVER 22/03/2024 4:16 AM

# Embedded App SDK Hotfix

In the spirit of "move fast and break things" we moved fast, and broke a thing. If you had installed @discord/embedded-app-sdk v1.0.1 please run `npm install @discord/embedded-app-sdk@latest` to update your SDK. More info here.
Discord Developers #api-announcements SERVER 22/03/2024 7:09 AM

# Native Polls Launch

Hi devs! You're hearing it here first: We're excited to announce that native polls are almost here! The experiment has rolled out to a small percentage of users and the full launch is coming soon. We know this may impact how you want to think about your builds.

## API Info

This rollout includes new APIs for developers to build on top of it. More information can be found in the PR here and Help Center article here.

## Questions & Feedback

Drop your questions and feedback in the below thread. Please note that staff replies may be delayed because of the GDC event. Thank you in advance for understanding!
Discord Developers #api-announcements SERVER 3/04/2024 4:12 AM

# CSV Export for Premium App Analytics

Hi everyone! If you have an app with Monetization enabled, we have released the ability to export your SKU analytics to CSV. This will allow you to use your preferred data tools to report on your premium offerings. You can find the export at the bottom of the `Monetization → Analytics` tab of your app to export datapoints such as `sales_count`, `sales_amount`, `sales_currencies`, `cancellation_count`, `refund_amount`, and `refund_count`, aggregated by each of your offerings for the selected month. Happy building!
Discord Developers #api-announcements SERVER 16/04/2024 7:36 AM

# User-Installed Apps Experiment in DDevs

Hi everyone! User-Installed Apps are still in preview, meaning interaction responses are forced to be ephemeral in servers with over 25 members. Today we are lifting this limitation in our Discord Developers server for a limited experiment. (All followup messages will still currently be ephemeral.) Try it out and let us know your feedback in the thread below. Please note that User-Installed Apps are still in preview and are subject to change. Edit: The experiment is off for the weekend but will be back soon! (edited)
Discord Developers #api-announcements SERVER 18/04/2024 6:10 AM
6:10 AM
Wumpus editor's note: Previous message is a sticker showing bot app.
Discord Developers #api-announcements SERVER 19/04/2024 1:38 AM

# Authenticated Attachment URL Parameters Expiration

The expiration time for Attachment URLs will be decreasing from 14 days to 1 day. The rollout will happen gradually on a per-attachment basis, so your app will encounter some attachments with a 1-day expiration, and others with a 14-day expiration. As noted in previous announcements, you should continue using the `ex` URL parameter to determine the expiration time for an attachment URL.
Discord Developers #api-announcements SERVER 25/04/2024 6:48 AM

# Store and One-Time Purchases Launch

Two new features are now available for Premium Apps: One-Time Purchases and Stores.

### One-Time Purchases

- Durable Items: A one-time purchase that is permanent and is not subject to either renewal or consumption, such as lifetime access to an app's premium features.
- Consumable Items: A one-time, non-renewable purchase that provides access, such as a temporary power-up or boost in a game.

Learn more about implementing One-Time Purchases.

### A Store for Your App

To showcase your App Subscriptions and One-Time Purchase items, we have also introduced a Store for your Premium App. You can now create a unique Store page within the developer portal and add your published subscription SKUs or one-time purchase SKUs to your store view, allowing your users to buy these items from your App Directory or Bot User Profile. ✍️ Read more about the developer documentation updates in the change log or learn how to enable monetization for your app in our Monetization Overview.
Discord Developers #api-announcements SERVER 27/04/2024 3:27 AM

# ⏩ Forwarding Coming Soon

Forwarding is coming to Discord soon™️! Forwarding will let you click on any message or piece of media and send it to another place in Discord. It'll show up clearly labeled as "forwarded" with only the content of the message included. We'll launch to a small % of users within the next month and then ramp up from there over time.

## API Info

We're letting you know early as there will be a few changes for apps to "see" forwarded messages and we want you to be able to leverage forwarding for your apps. You can see the updates, subject to change, in the PR here.
Emoji Stealer 27/04/2024 7:58 AM
i can talk here?
1
Discord Developers #api-announcements SERVER 7/05/2024 4:16 AM

# Identity Verification Update

Hi devs! The identity of an owner of a verified app or development team will now need to be re-verified every three years. You may have seen a notice about this in the Developer Portal. Anyone who needs to re-verify their identity at this time will receive an email with more information this week. If it has not yet been three years since you last verified your identity, you will receive an email at a later date when you need to re-verify. We're working on updating related Help Center articles with information and fixing a bug which may cause the button to disappear too quickly in the Developer Portal.
Exported 865 message(s)
Timezone: UTC+10