DN42 access 本服务为那些无法轻松访问自身网络的用户以及希望体验 dn42 但又不想承担维护自有网络成本的用户提供 dn42 连接 默认情况下，地址从/96地址块中分配，如果您希望租用独立的/96前缀或更大的地址空间，请按照联系方式联系我 所有公开的PoP均已屏蔽来自中国境内的 IP 地址。如果您确实需要dn42 access，请与我联系并提供合理的理由 该服务由AS4242423377提供 - - - - - - - The service provides DN42 connectivity to members who cannot easily access their own networks, as well as to those who would like to explore DN42 without the overhead of maintaining their own network. By default, addresses are allocated from a /96 block. If you wish to lease a dedicated /96 prefix or a larger address space, please contact me using the methods provided in the contact information. All publicly accessible PoP are blocked for IPs originating from within China. DN42 access from within China is not publicly available. If you genuinely require access, please contact me and provide a valid justification. Hosted by AS4242423377. Policy 本服务需要花费时间和金钱才能运行，但为了您的利益，我们免费提供。使用本服务是一种特权，而非权利。您必须合理使用本服务，以确保其他用户也能继续享受同样的便利。任何滥用、误用或干扰服务或其他用户的行为都可能导致您的访问权限立即被暂停或终止。 滥用行为包括但不限于： - 过度使用资源 - 黑客攻击、病毒、木马等，或任何其他可能损害服务或对服务及其用户造成风险的干扰行为 - 传播可能导致民事或刑事责任的不良内容 - - - - - - - This service require real time and financial resources to operate, yet are provided free of charge for your benefit. Access to the services is a privilege, not a right. You must use the services responsibly and considerately to ensure that other users can continue to enjoy the same opportunities. Any misuse, abuse, or activities that disrupt the service or other users may result in immediate suspension or termination of access. Abuse could include, but is not limited to: - Excessive use of resources - Hacking, viruses, trojans etc or any other disruption that could harm or create risk to the services or its users - Distribution of objectional content that could create a civil or criminal liability PoP ## Toronto, Canada Prefix: fdb6:fc6a:e66c:724f:fad1:d2cf::/96 Zerotier: 4753cf475f65b0fb ## Los Angeles, USA coming soon #announcement#service
Hashtags
搜索 #banwarnbot
@luckydonaldsbots · Post #256 · 2020/07/08 23:11
New feature I forgot to write about, @BanWarnBot will now also notice you if a user which already has gotten warns joins back into your group. #update#BanWarnBot.
Hashtags
@luckydonaldsbots · Post #138 · 2018/07/05 20:26
Updated @BanWarnBot to no longer kick people when revoking warns. The technical details: Telegrams unbanChatMember API method is actually is a kick+unban, which isn't documented anywhere. It will now check first if the user is not member of the group, being kicked (=banned) or the user left the group (or "was forcefully left by admins"). Else it will not attempting to unban the use as that would kick, too. #update#BanWarnBot
Hashtags
@luckydonaldsbots · Post #133 · 2018/07/04 11:17
@BanWarnBot now allows to revoke warnings by clicking on a button right under it. #update#BanWarnBot
Hashtags
@luckydonaldsbots · Post #300 · 2025/11/12 07:19
Experienced another way how the disk can run full, deleted 100 GB of ancient pending RabbitMQ tasks and set a message TTL as well as a maximum queue length. With that the bots are back online. #JoinCaptchaBot #BanWarnBot
Hashtags
@luckydonaldsbots · Post #299 · 2024/06/05 22:18
Some bots were down again, which was caused by the disk running full. Deleted 460 GB of log files and restored the services. Bots will process all pending updates normally. #JoinCaptchaBot#BanWarnBot
Hashtags
@luckydonaldsbots · Post #252 · 2020/07/04 15:57
@BanWarnBot is nowsuccessfully back up and running the newest version: Here's a list of what's new: New /kick and /ban commands: Just like the /warn one, but immediately removes the user from the chat, either once or permanently. You can specify a reason for why you kicked/banned someone after the command. Those kicks count into the normal warn count, because they are kinda like special warns. Those 3 commands, /warn, /kick and /ban now also allow the first thing after the command to be the id of a user, in the format of #1234, or a user mention. This can come in handy if you don't have a message to reply to. Overhaul of the warning lists: Now the list of /listwarnings and /listallwarnings will link you to the message warn message, if you press the date stamp. Also support for distinguishing automatic kicks/bans and manual kicks/bans has been added. #update#BanWarnBot#resolved
Hashtags
@luckydonaldsbots · Post #251 · 2020/07/04 14:51
Maintenance: Moving @BanWarnBot to the new server. Okey going through the same procedure for @BanWarnBot now, hopefully without the database breaking this time. Turning the bot off for moving the database, so any /warns send in the meantime shouldn't get lost. As soon as it's on the new server it should pick up those, and carry out the needed actions. I'll take @BanWarnBot down in 10 minutes. Other bots should not be affected. #maintenance#downtime#BanWarnBot
Hashtags
@luckydonaldsbots · Post #295 · 2021/12/15 23:01
It was brought to attention that with some bots admin commands were no longer working. That was happining for the bots migrated yesterday, because of the new bot API version. This is #fixed now. Thanks for letting me know, A. A.! #BanWarnBot#RulesRulesBot#JoinCaptchaBot
@luckydonaldsbots · Post #232 · 2020/03/24 10:45
I will soon migrage some services onto a new server. Therefore those services will be unavailable for the next two hours: @JoinCaptchaBot@BanWarnBot@RulesRulesBot and @ForwardWhitelistBot. #downtime #JoinCaptchaBot#BanWarnBot#RulesRulesBot#ForwardWhitelistBot
@luckydonaldsbots · Post #230 · 2020/03/23 11:24
I will definitely work hard to keep the most important group management services stable, including: @JoinCaptchaBot, @RulesRulesBot, @BanWarnBot, and @HeyAdminBot. And for now also the less important @NoServiceBot. #PermalinkBot#NoServiceBot#RulesRulesBot, #BanWarnBot#HeyAdminBot #ongoing#issue