Same. I'm horrified, but also not surprised.
HN user
prologic
"Problems are Solved by Method"
Website: https://prologic.dev/ Twtxt: https://twtxt.net/~prologic Blog: https://prologic.blog/ Git: https://git.mills.io/prologic
wut da actual fuq?!
The Irony here is what Hacker News did to this page. 503 Service Unavailable :D
Not really. Like you I also started coding in BASIC at an early age, though I'm 10 years behind you in "age" but probably 10 years ahead of you, only because I grew up in a 3rd-world country where we ourselves were behind the rest of the 1st/2nd nations
That being said however, no, i don't feel like I've lost the "spark" at all. Sure, I no longer care that much about the "writing of the code" itself, but you just end up shifting your focus to the creative side of thigns, content creating and driving.
That's still interesting. AI can't (yet?) replace this.
I just compared this Rust implementation against the original C sources. Some ~50k SLOC (Rust) compared to maybe ~8-12k SLOC of C (depending on if you count headers). Why is the Rust implementation so much more complex and onerous?
Let me know how it goes! I have 3 quite successful aps built and in production using Swag now and it's pretty great DX (DevEx) and UX.
Hah! Thanks for whomever posted this. This is my little baby/project and I'd like to share a little about it... Quite some years ago (before all this AI Hype) I ventured on trying to deeply understand how Linux containers worked. At first I built a shell script called `box` that used the Busybox `unshare` utility to create little isolated namespaces/cgroups where you could "box" your little program on the root file-system. Later on I decided to write box in Go.
box now is basically a fully capable lightweight daemon-less container runtime, much like podman (but no rootless, not yet). Along with another project I also wrote called sshbox that is basically an SSH reverse prox; are what powered mbox.blue
mbox.blue is basically an experimental shared Linux system based around the core idea of persisetnt containers. All home grown.
I always thought this was WASM "value add" -- The "virtual machine" of the browser (although we had this back in the day with Shockwave, Flash and Java applets too hmmm :D)
This kind of reminds me of the days when Java™ was popular. I agree, if we're pushing to build software to target another machine (WASI) have we really improved anything?
I'm one of those people. I think it comes down to the intent. There is an implicit good will of those that do this that the data isn't abused or the infrastructure behind it overwhelmed (self-hosting). "Big Tech" just make this worse, because their motivations aren't the same as ours (small web).
Not yet unfortunately. But if you're interested, please reach out! I currently run it in a 3-region GeoDNS setup with my self-hosted infra.
I was planning on building a Caddy module for Anubis actually. Is anyone else interested in this?
I would be interested to hear of any other solutions that guarantee to either identity or block non-Human traffic. In the "small web" and self-hosting, we typically don't really want Crawlers, and other similar software hitting our services, because often the software is either buggy in the first place (Example: Runaway Claude Bot) or you don't want your sites indexed by them in the first place.
This is true. I had some bad actors from the ComCast Network at one point. And unfortunately also valid human users of some of my "things". So I opted not to block the ComCast ASN at that point.
Which arguably they should let go of
I don't distinguish actually. There are two things I do normally:
- Block Bad Bots. There's a simple text file called `bad_bots.txt` - Block Bad ASNs. There's a simple text file called `bad_asns.txt`
There's also another for blocking IP(s) and IP-ranges called `bad_ips.txt` but it's often more effective to block an much larger range of IPs (At the ASN level).
To give you an concrete idea, here's some examples:
$ cat etc/caddy/waf/bad_asns.txt # CHINANET-BACKBONE No.31,Jin-rong Street, CN # Why: DDoS 4134
# CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN # Why: DDoS 4837
# CHINAMOBILE-CN China Mobile Communications Group Co., Ltd., CN # Why: DDoS 9808
# FACEBOOK, US # Why: Bad Bots 32934
# Alibaba, CN # Why: Bad Bots 45102
# Why: Bad Bots 28573
I've read about Anubis, cool project! Unfortunately, as pointed out in the comments, requires your site's visitors to have Javascript™ enabled. This is totally fine for sites that require Javascript™ anyway to enhance the user experience, but not so great for static sites and such that require no JS at all.
I built my own solution that effectively blocks these "Bad Bots" at the network level. I effectively block the entirety of several large "Big Tech / Big LLM" networks entirely at the ASN (BGP) by utilizing MaxMind's database and a custom WAF and Reverse Proxy I put together.
Yeah sure, but as I said the community is actually much larger. It is also very hard to measure because Twtxt/Yarn is what I call, "truly decentralised". However you are right, the search engine/crawler puts the active feeds at around ~1000 or so. So orders of magnitude smaller than any "big tech" social ecosystem, but that's kind of the appeal really.
The Twtxt/Yarn community is larger than you think. As the founder of Yarn.social[1] (which itself uses the Twtxt spec and extensions[2]) and operator of the "flagship" instance twtxt.net[3] I often interact with around ~70 folks (_not including news feeds_).
[1] https://yarn.social [2]: https://twtxt.net [3]: https://twtxt.net
Alright. I'll comment. -- I find it interesting to learn just how much the Go compiler can "optimize your code away". That's both good and bad.
The point on benchmarking the right thing is 100% spot on, same goes for testing too. The optimization problem however is a bit too contrived IMO. When would you possible write code (aside from very trivial things) where the compiler would optimize all your code away, thus making your benchmarking invalid? I want to see a real-world example of where someone has been caught out by this?
Yarn.social (https://yarn.social) and Salty.im (https://salty.im) are both projects of mine making $0/month (community driven and will stay that way). Yarn.social is the oldest now at around ~2.5yrs
Author of the Salty IM Spec here and currently working on a reference client and broker (`saltyd1) implementations called Salty Chat (`salty-chat` CLI and TUI) and a PWA (Progressive Web App)
Thanks for posting this! Happy to answer any questions! The project is in rapid development and has only been alive for ~2 weeks or so.
So far most things are working nicely, docs could be better (of course) and we finally have the Mobile/Desktop/Web (PWA) App in a working state (UX issues aside).
Anyone have any contacts in Apple or know how to file a bug report with Apple that won't just get lost in the ether?!
This is a question I had been asking for several years until I came across Twtxt (the spec/format originally created by Felix, @buckket, read about it at https://twtxt.readthedocs.org) -- When I came across it I saw a bit more potential so I created (what is effectively) a multi-user client also called Twtxt over at https://twtxt.net (launched in Aug 2020). Since then we've also created a Mobile App (Goryon) available in the App Store (iOS) and Play Store (Android), we also offer free (at this time) hosting of pods (individual instances) at https://twt.social/ -- Today we have a dozen pods/instances and some ~300 users. My own pod (twtxt.net) sees around ~4M hits/month :O
Is there an issue that I call the backend (codename) the smae thing? @buckket I _assume_ yu're okay with this, although we haven't spoken much...
Of course for many things, microblogging is too short
the software behind twtxt.net is quite flexible and configurable. An operator can choose to increase the MaxTwtlength limit by configuration.
Between instances of twtxt.net I actually plan to do this. I'm working on more "federation" features that allow users to be spread out over multiple twtxt.net instances.
Of course this doesn't for folks in the twtxt community that just host a twtxt.txt file, but that's okay.
Looks interesting. Similar ideas :) I have a bit of a different focus though; mine is more focused on self-host ability.
:O That's a pretty deceptive way to get people to use your thing eh? NOt sure I want to do that ;)
Thanks! I will :) v0.0.8 (https://github.com/prologic/twtxt/releases/tag/0.0.8) is out nw with pre-built binaries and some nice new features!