还要维护一个CDN好烦,于是不做CDN了,ALL IN BOOM!

    / 在文件顶部添加新表结构注释
    /*
    MySQL: 建议增加表
    CREATE TABLE `smtp_send_log` (
      `id` int(11) NOT NULL AUTO_INCREMENT,
      `smtp_user` varchar(255) NOT NULL,
      `send_time` int(11) NOT NULL,
      PRIMARY KEY (`id`),
      KEY `idx_user_time` (`smtp_user`,`send_time`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
    */
    
    // --- 以下是在 LoveKKCommentModify_Plugin::smtp 方法里增加频率校验逻辑 ---
    
    public static function smtp($data) {
        $db = Typecho_Db::get();
        $smtpUser = $data['smtp_user'];
        $now = time();
        $hourAgo = $now - 3600;
    
        // 查询过去 1 小时发送数量
        $count = $db->fetchObject($db->select(array('COUNT(*)'=>'c'))
            ->from('smtp_send_log')
            ->where('smtp_user = ?', $smtpUser)
            ->where('send_time >= ?', $hourAgo)
        )->c;
    
        if ($count >= 50) {
            // 超过频率直接返回错误
            throw new Exception('SMTP发送频率超过限制(每小时最多50封),请稍后再试。');
        }
    
        // 邮件发送逻辑...
        $result = self::realSendMail($data); // 假设这是你的实际邮件发送方法
    
        // 发送成功后入库
        if ($result) {
            $db->query($db->insert('smtp_send_log')->rows(array(
                'smtp_user' => $smtpUser,
                'send_time' => $now
            )));
        }
    
        return $result;
    }
    
    // --- 如果你用的是其他邮件发送入口,请将上述频率判断和日志插入逻辑,放到实际的发送代码前后即可 ---


    应该OK了

    这个bug好像是我内存不够😭

    更新了主题,时光机的bug还是在……

    升级到typecho-v1.2了

    呵呵


    今天上网站一看,字节跳动的CDN又下线了,整个页面样式全乱了,暂时切回本地源了。
    话说腾讯云轻量新加坡100M网络确实不算好,一到晚上就卡顿

    备案的IP不打算续了,CDN域名也关了

    换到腾讯云新加坡了,也是用上锐驰轻量云了

    1. 登录光猫超级管理员后台:192.168.1.1/cu.html,密码默认为CUAdmin (浙江/内蒙/河北: cuadmin辽宁:lnadmin
      青海:qhuniadmin
      湖南:CUAdmin#HGU
      重庆:cqunicom
      北京:123qweasdzxc
      海南:cu@HNunicom黑龙江:8MCU@HLJ
    2. 基本配置中选择上行线路配置,第一个选项选择ipV4/V6,第三个选项连接名称中选中名为x_INTERNET_R_VID_y(Ps: x和y的值每个人可能不一样)的配置信息,尤其是 VLAN ID 值。
    3. 在ipV4/V6下添加一个新的 Bridge 模式的连接,端口绑定选择LAN1(千兆口),其他配置与原来的PPPoE模式下相同,尤其是 VLAN ID 值。
      。 删除原来的x_INTERNET_R_VID_y连接,至于x_TR069_R_VID_y连接,据说是留给运营商进行远程控制路由器配置的,删除后超密或其他参数就不会被远程更改。理论上很长一段时间不会有问题。但是也有网友反应,删除后,联通下发了一些配置,你的猫会因为收不到这些下发的新参数,导致某些功能不能使用。不过也没关系,遇到这个情况,联系管片客服,让他们上门或者其他方式,做一下数据即可。
    4. 对 IPTV、VoIP 有需求的同学可以根据参考资料1进行相应设置。
    5. 接下来便可以使用路由器按原来的宽带账号密码拨号上网即可。

    后续

    以上密码已经失效了, [](http://192.168.1.1/backupsettings.conf) 也是404,除了[](http://192.168.1.1/hidden_version_switch.html)中切回默认版本使用默认密码登录外,最为快捷的还是去淘宝闲鱼花几块钱去买密码。应该从2023年初开始时使用随机密码,只有后台能看到,并且会定期更新。

    分形工艺R6


    标签机

    REF

    Here is a link to the official Docker documentation for proxy HTTP: https://docs.docker.com/config/daemon/systemd/#httphttps-proxy

    A quick outline:

    First, create a systemd drop-in directory for the Docker service:

    mkdir /etc/systemd/system/docker.service.d

    Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY and HTTPS_PROXY environment variables:

    [Service]
    Environment="HTTP_PROXY=http://proxy.example.com:80/"
    Environment="HTTPS_PROXY=http://proxy.example.com:80/"

    If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable:

    Environment="HTTP_PROXY=http://proxy.example.com:80/"
    Environment="HTTPS_PROXY=http://proxy.example.com:80/"
    Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com"

    Flush changes:

    $ sudo systemctl daemon-reload

    Verify that the configuration has been loaded:

    $ sudo systemctl show --property Environment docker
    Environment=HTTP_PROXY=http://proxy.example.com:80/
    Environment=HTTPS_PROXY=http://proxy.example.com:80/

    Restart Docker:

    $ sudo systemctl restart docker

    Footnote regarding HTTP_PROXY vs. HTTPS_PROXY: for a long time, setting HTTP_PROXY alone has been good enough. But with version 20.10.8, Docker has moved on to Go 1.16, which changes the semantics of this variable: https://golang.org/doc/go1.16#net/http
    For https:// URLs, the proxy is now determined by the HTTPS_PROXY variable, with no fallback on HTTP_PROXY.

    rikka@aml-s812 % udevadm info  -n /dev/bus/usb/001/004                                         ~
    P: /devices/platform/soc/c9040000.usb/usb1/1-1
    M: 1-1
    R: 1
    U: usb
    T: usb_device
    D: c 189:3
    N: bus/usb/001/004
    L: 0
    V: usb
    E: DEVPATH=/devices/platform/soc/c9040000.usb/usb1/1-1
    E: DEVNAME=/dev/bus/usb/001/004
    E: DEVTYPE=usb_device
    E: DRIVER=usb
    E: PRODUCT=51d/2/1
    E: TYPE=0/0/0
    E: BUSNUM=001
    E: DEVNUM=004
    E: MAJOR=189
    E: MINOR=3
    E: SUBSYSTEM=usb
    E: USEC_INITIALIZED=17111111955
    E: ID_BUS=usb
    E: ID_MODEL=Back-UPS_BK650M2_CH
    E: ID_MODEL_ENC=Back-UPS\x20BK650M2_CH
    E: ID_MODEL_ID=0002
    E: ID_SERIAL=American_Power_Conversion_Back-UPS_BK650M2_CH_912101A11361
    E: ID_SERIAL_SHORT=911111111111
    E: ID_VENDOR=American_Power_Conversion
    E: ID_VENDOR_ENC=American\x20Power\x20Conversion
    E: ID_VENDOR_ID=051d
    E: ID_REVISION=0001
    E: ID_USB_MODEL=Back-UPS_BK650M2_CH
    E: ID_USB_MODEL_ENC=Back-UPS\x20BK650M2_CH
    E: ID_USB_MODEL_ID=0002
    E: ID_USB_SERIAL=American_Power_Conversion_Back-UPS_BK650M2_CH_9B1111111161
    E: ID_USB_SERIAL_SHORT=9B1111111161
    E: ID_USB_VENDOR=American_Power_Conversion
    E: ID_USB_VENDOR_ENC=American\x20Power\x20Conversion
    E: ID_USB_VENDOR_ID=051d
    E: ID_USB_REVISION=0001
    E: ID_USB_INTERFACES=:030000:
    E: ID_VENDOR_FROM_DATABASE=American Power Conversion
    E: ID_MODEL_FROM_DATABASE=Uninterruptible Power Supply
    E: ID_PATH=platform-c9040000.usb-usb-0:1
    E: ID_PATH_TAG=platform-c9040000_usb-usb-0_1
    E: ID_FOR_SEAT=usb-platform-c9040000_usb-usb-0_1
    E: TAGS=:seat:
    E: CURRENT_TAGS=:seat: