|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Jianshi||1,852||5 years ago||16||apache-2.0||Java|
|A Full-Stack mobile app, including Android & Server, Simple-Poem 简诗. You can write poem in graceful & traditional Chinese style.|
|X Prober||1,280||7 hours ago||107||December 14, 2022||4||gpl-3.0||TypeScript|
|🐘 A probe program for PHP environment (一款精美的 PHP 探針, 又名X探針、劉海探針)|
|Wowsimpleregistration||177||a month ago||16||gpl-3.0||PHP|
|Simple Registration page for TrinityCore/AzerothCore/AshamaneCore/CMangos|
|Lanraragi_cn||121||10 months ago||mit||Perl|
|This repo is a fork of Difegue / LANraragi , those things i've done was to translate this repo into chinese ,and fix chrome browser js problem.|
|Node.js 的 Firewalld 界面化,基于 Node.js 适用于 个人服务器 和 NAS 的 Firewalld(防火墙) 界面化,不需要记忆操作命令,更没有 Firewalld 的区域概念,和 iptables 复杂的 表链结构 .界面上点击创建一些规则就可以达到 自动 屏蔽和放行 IP 的目的.|
|Petgps||72||2 months ago||6||mit||Python|
|A DIY, python-based framework to set up a server and exchange TCP packets with a chinese GPS+SIM (2G) device whose communication protocol is derived from something called GT06|
|Anchordns||57||8 years ago||4||Java|
|A smart DNS server for Chinese|
|Oss Ftp||54||3 years ago||15||mit||Python|
|The ftp proxy for Aliyun OSS.|
|Bjdns||44||4 years ago||gpl-3.0||Python|
|A dns server which can protect yourself against DNS poisoning in China. / 抗污染 带缓存的dns服务器|
|Sql Injection Cheat Sheet Chinese Ver.||23||8 years ago|
|Translate SQL Injection Cheat Sheet(http://ferruh.mavituna.com/sql-injection-cheatsheet-oku/) into Chinese.|
This is a DIY-project to equip my cat (and hopefully, yours) with a small GPS tracker that is fitted with a SIM card to enable real-time location. There are many commercial alternatives to such a project, but they basically all rely on:
These commercial alternatives are absolutely overpriced (device 80 EUR as of today + usually charging a montly service fee, ranging from 3 to 8 EUR). In fact, the design is based on cheap knockoff IoT devices available from a well-known chinese wholesale website. The amount of data used by this kind of tracker is minimal (like, REALLY small, maybe up to 1 or 2 Mb per day of use), and as such, there must be cheaper alternatives to these commercial things... M'kaaaay ?
On the other hand, the chinese alternatives are provided with ugly UI for their ad-hoc services... and I don't want anyone in China to know where my cat goes out!
This repo hosts some developments I have made while using these devices called ZX612 and ZX303 from AliExpress. As of now, it is a complete WIP project, and the code is ugly, but hopefully decently documented. The ultimate goal is to have:
Link for purchasing these devices: ZX612 and ZX303 (The ZX303 has more feature for the same size and I'd go with that one). If you want a battery included, order the versions with small plastic casing.
The protocol documentation for these devices is extremely poorly written. It was sent to me by the seller in the form of a Word document, available in the resources folder. It seems to be derived from the GT06 protocol, also documented in the same directory. I have somewhat re-written the documentation into an Excel document where each column represents a byte, for each kind of packet sent or received by the device.
These devices can be controlled by sending them SMS or data packets in the form of hexadecimal strings. The general format is
7878 XX YY ZZZZ 0D0A
7878: (2 bytes) start bytes
XX: (1 byte) Data length. For some protocol numbers (see
YYthis is not the length but a parameter, e.g. number of SSIDs for WiFi location-based data)
YY: (1 byte) Protocol number (defining what the data will be)
ZZZZ: (varying length) Long chain of hex data that will be interpreted according to the value of
0D0A: (2 bytes) Stop bytes
Your Google Maps API key is strictly private. It should NEVER be shared with anyone, as it enables querying the API without further login. An API key made public exposes you to unauthorized use, breach of Google's API Terms of Services, or massive querying possibly rsulting in you having to pay the bill once free queries have been exhausted. You don't want that to happen, do you ?
dotenv Python library is used to import the content of a
.env file into the environment upon starting the main script. This is convenient to set your private API key in a file that will not make it into the Git repository.
An empty exemple of this file is available here in the Git repository. The .gitignore file from this repository is set to not track the real
.env file. As such, you should add your API key in a local copy of .env derived from the example file, e.g. with:
cp .env.example .env vi .env
Remember to not remove
.env from the
.gitignore file !
The server is set to run on port TCP 5023. Remember to redirect that port towards the machine that will run the server.
After you've created the actual
.env file, you're all set. Just run:
Data should now be coming in.
Ctrl+C twice will kill the current connection and then kill the server.
...to be written here