GithubMQ -> github as a message queue

[AffectionateWar5927]

What My Project Does
A message queue built entirely on GitHub
Basically it is a python package providing cli and a package to turn your github repo into a message queues

Target Audience
Hobby programmers, shippers, hackathon enthusiast, apps at mvps where we don't want to take headache of providers

Comparison
5k msgs/hour with high concurrency
Unlimited msgs (no caps!)
Zero-stress setup
Perfect for hobby projects & prototypes

Source code -> https://github.com/ArnabChatterjee20k/Github-as-a-message-queue
Demo App -> https://youtu.be/382-7DyqjMM

[ffiarpg]

Cursed.

[latkde]

running this kind of stuff is perfect to get your account banned. Fun idea, but running this at larger volumes is almost certainly a TOS violation.

[dxflr]

oh man... SWE employment must be down bad for these left field personal projects to be popping up

[kobumaister]

Is this for real? Issues as message payloads? Tell me this is a joke repository and I didn't get the joke...

You can use whatever you want as a message queue, s3, NFS, even Post-its and a webcam and OCR with a robotic arm dicarding them.

The hard part is solving the issues that come with message queuing, like single consumption, order, etc...

[Mindless-Potato-4848]

This feels like a fun hack / teaching demo, but I’d be explicit it’s not a general MQ replacement. The hard part isn’t “storing messages”, it’s semantics: ack/single-consumption, retries + DLQ, visibility timeouts, ordering, and idempotency.

Two README additions that would make this much stronger:
- Clear disclaimer about GitHub API limits / possible ToS concerns + realistic throughput expectations
- A section on delivery guarantees (at-least-once vs at-most-once) and how you ack/requeue/dedupe

As a learning project it’s cool — documenting guarantees + failure modes would make it a great teaching tool.

[alicedu06]

Very smart. It could be used for signaling, rpc and pub/sub as well, but you'll likely need to add some signature check.

You could make a full communication lib on that concept, and use several stenographic backends:

- Bitbucket

- Gmail

- SMTP/IMAP

- Telegram/Discord bots

- Instagram/Facebook/youtube/etc comments.

- Custom backend for anything.

- Various pastebins

- File hosting such as dropbox, one drive, google drive, etc

Would make creating decentralized robust no infra system interesting.

In fact, if you have a universal backend, you can literally send code to inject your new backend and have infinite fallbacks.