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
搜索 #resolved
@luckydonaldsbots · Post #220 · 2020/01/15 22:43
A few minutes ago I had a networking issue, making my server unreachable for a bit more than 5 minutes. Got that resolved and the services are responsive again. It may have happen that some messages got processed twice in that unstable period, which is due to how telegram sends updates. I appologize for any inconvenience. The server is now back to operating normal. #resolved
Hashtags
@luckydonaldsbots · Post #205 · 2019/06/15 13:50
All updates are processed, it is as responsive as ever. Carry on. #resolved
Hashtags
@luckydonaldsbots · Post #254 · 2020/07/05 14:07
Fixed a bug where @RulesRules would hang on processing a special type of message. Should now be responsive again. #update#resolved
@luckydonaldsbots · Post #125 · 2018/02/01 17:47
17:46 UTC @BanWarnBot and @RulesRulesBot are back up. 17:50 UTC @HeyAdminBot is back up. 18:00 UTC @moustache_bot is back up. 18:25 UTC finally @StickerTagBot is back up. A file went missing, so not all code to run was there. Basic operation is back. 19:16 UTC @LangInfoBot is back up. 19:26 UTC @BassBoostBot is back up. Lol, as if anyone missed that bot. 19:34 UTC @bonbot is back up soon. Currently fighting with API rate limiting. 19:37 UTC @travis_cibot is back up. 19:45 UTC and the health checks are all good now. #resolved#update
@luckydonaldsbots · Post #193 · 2019/02/24 02:39
#downtime#resolved
@luckydonaldsbots · Post #250 · 2020/07/02 20:32
Everything is back up and running again. With that @RulesRulesBot now finally is on the fast new server. #resolved#RulesRulesBot
Hashtags
@luckydonaldsbots · Post #278 · 2021/03/27 16:48
The worker node of @JoinCaptchaBot just restarted ungreacefully, in some cases causing up to 6 times the same messages. The good news is, while it happend multiple times in the same second, any missed out kicks were now processed as well (6 times). The issue has been identified and will be resolved soon. Sorry for your inconvinience. #resolved#JoinCaptchaBot
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 #246 · 2020/06/20 01:55
Fixed @HeyAdminBot getting stuck on some special message types and becoming unresponsive. #resolved#HeyAdminBot
Hashtags
@luckydonaldsbots · Post #218 · 2019/09/08 19:48
Updated @HeyAdminBot: - Improved handling of private groups, will now export the join link if the bot has the rights for that - Added a direct link to the message ("requested") - Randomizing order of admins called so it's not always the same one being the first to respond. - Fixed bug where the first admin would receive the messages meant for the other admins as well. #update#resolved#HeyAdminBot
Hashtags