sudo cast
48 subscribers
498 photos
12 videos
16 files
1.54K links
v2 @sudo_recast

casted something nice or not

v1 / cast / channel / telegram / sudo

more @sudo_radio
email telegram@gadflysu.com
Download Telegram
Gmail 支持在地址任意位置插入「.」字符或者在末尾附加「+」字符及任意字符串来达到 alias 的效果,即上述地址变换后 email 仍可递送到对方邮箱。

iCloud Mail 则仅支持后者,即支持在末尾附加「+」及任意字符串实现 alias 效果。

Outlook Mail 则两者均不支持,但你可以添加自定义 alias,且可以从自定义的不同 alias 发送邮件。

#email #alias
.COM Domain - Exabytes

$0.99 (On Sale – Save 37%, 2-year purchase required, 2nd year billed at $16)
Promo code: COM-99CENTS

https://www.exabytes.com/promo
无类别域间路由:如果我们指定一个 CIDR 块为 10.10.1.32/27,则根据 CIDR 比特位比较,10.10.1.44 是属于该块,但 10.10.1.90 则不是。 - #wikipedia
Forwarded from 舊音
水了一篇。好歹三月了,咸鱼太久(
LGTM = looks good to me
ACK = acknowledgement
NACK/NAK = negative acknowledgement
RFC = request for comments
WIP = work in progress
AFAIK/AFAICT = as far as I know / can tell
IIRC = if I recall correctly
IANAL = I am not a lawyer


#abbr
我现在很想看一遍 Telegram Bot API 然后顺手翻译成中文。我疯了吗?
https://burns.gadflysu.com/

用 kchown 的项目搭建了一个简单的阅后即焚服务。
To GitHub Help:

Hello,

My GitHub Pages got down on HTTPS. The "Enforce HTTPS" option also got grey.

I've setup GitHub Pages with HTTPS on my domain (blog.gadflysu.com) around 3 months ago. (Yes, I succeeded.) I'm using Let's Encrypt with certbot. Auto-renew is setup via cron on my server, such that if the certificate would be expired in 30 days, certbot would renew it, which is for gadflysu.com and *.gadflysu.com (wildcard).

So, as expected, the program provided by Let's Encrypt had renewed my certificate, which I got in Dec 2018. Now my certificate is valid between Mar and Jun 2019. However, I can't visit blog.gadflysu.com since yesterday afternoon (specifically the time my FIRST certificate expired), and the "Enforce HTTPS" option in my repo also got grey. After I disable proxy by Cloudflare (and I had to set the "crypto" option to "Full" (but not "Full (strict)")), I *found* the certificate showed in my browser is valid between Dec 2018 and Mar 2019 (What?! That certificate I've abandoned ONE MONTH ago?) In a world, GitHub Pages seems won't check websites' certificate changes. This caused my page down.

What should I do to setup HTTPS (enforced) for my GitHub Pages with my new certificate? Unless I change the strategy on Cloudflare CDN, my website would have been down for nearly 18 hours.

Please help me. Thank you very much.