The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Https-bot Alternatives
Similar projects and alternatives to https-bot
-
-
distroless
🥑 Language focused docker images, minus the operating system.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
https-everywhere
Discontinued A browser extension that encrypts your communications with many websites that offer HTTPS but still allow unencrypted connections.
-
rofimoji
Emoji, unicode and general character picker for rofi and rofi-likes
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
https-bot reviews and mentions
-
Show HN: I wrote an HN bot to suggest HTTPS url when people post HTTP URLs
It's inspired by this comment I made: https://news.ycombinator.com/item?id=26599746.
I actually saw several comments with HTTP URL posted, and that was the only one I bothered to comment on. So I thought that this is something better suited for bots than human.
I hacked this together over yesterday and today: https://github.com/fishy/https-bot.
Basically it uses the Firebase API (https://github.com/HackerNews/API) to find comments with HTTP URLs in them, try the HTTPS version, compare the contents, post back a comment if the contents are more than 95% similar.
The "95% similar" part was actually the first part I wrote in the code. At first I tried a few existing go packages implementing diff/lcs, but most of them was quite slow and does a lot of allocations when I'm comparing two randomly generated 10KiB blobs, so I wrote my own (https://pkg.go.dev/github.com/fishy/https-bot/similarity), which is optimized for space (it does almost no allocations), and it's also faster because allocations are slow. (I know this is an unfair comparison that most of the existing implementations need to give you an output that can be used to reconstruct the two blobs back, so at least some of their allocations are required and unavoidable)
I also wrote a bug that it would find the same HTTP url in every run and post the same comment over and over again. My apologize to dang or whoever dealt with it (or maybe the system is good enough that it blocked those repetitive comments automatically).
In the end it successfully made 6 comments across ~4 hours (not including the repetitive ones). All of those comments are flagged (likely due to hn policy), https://news.ycombinator.com/item?id=26692588 is the only one that's still visible to other users at the time of writing, if you are curious.
I just killed it completely from the request of dang. Although it only lived for a few hours, it's still a fun exercise. Maybe I'll convert it into a reddit bot next? Who knows.
-
A Mathematical Keyboard Layout (2018)
Thank you for the feedback. I added FAQ to the README and answered this question: https://github.com/fishy/https-bot/blob/main/README.md#this-...
- Show HN: Curated by AI – Virtual Art Space
- Reflections on Relativity
- A Critique of Common Lisp (1984) [pdf]
- Connect with like-minded professionals via audio, video and in-person meetups
- The Simtel CD Collection (1994-2001)
-
A note from our sponsor - WorkOS
workos.com | 18 Apr 2024
Stats
fishy/https-bot is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of https-bot is Starlark.