A free account is an easy way to test out the platform, give it a test ride, see if it works for you. If it does, you can pay for a Pro (or Team) subscription, and you get to use your own domain, and keep all the posts you already made on the free account, with all their comments and replies and whatnots.

Or, if it works out, and you want to self host, you can do that, too!

The difference between write.as and medium and other enshittified things, though, is that write.as is not VC funded, and Matt has no interest in making an “exit”. Even if there are things I disagree on with him (eg, CLAs), I trust Matt to not enshittify write.as anytime soon. He’s been running things for almost a decade now, remarkably well.

It is pretty darn trivial to turn those env vars into a config.ini. But if you don’t want to, my writefreely-docker has you covered. It has been used in production for a couple of hundred writefreely blogs over the past few years.

It’s not. It just doesn’t get enough hits for that 86k to matter. Fun fact: most AI crawlers hit /robots.txt first, they get served a bee movie script, fail to interpret it, and leave, without crawling further. If I’d let them crawl the entire site, that’d result in about two megabytes of traffic. By serving a 86kb file that doesn’t pass as robots.txt and has no links, I actually save bandwidth. Not on a single request, but by preventing a hundred others.

I don’t think serving 86 kilobytes to AI crawlers will make any difference in my bandwidth use :)

That would result in those fediverse servers theoretically requesting 333333 * 114MB = ~38Gigabyte/s.

On the other hand, if the site linked would not serve garbage, and would fit like 1Mb like a normal site, then this would be only ~325mb/s, and while that’s still high, it’s not the end of the world. If it’s a site that actually puts effort into being optimized, and a request fits in ~300kb (still a lot, in my book, for what is essentially a preview, with only tiny parts of the actual content loaded), then we’re looking at 95mb/s.

If said site puts effort into making their previews reasonable, and serve ~30kb, then that’s 9mb/s. It’s 3190 in the Year of Our Lady Discord. A potato can serve that.

I only serve bloat to AI crawlers.

map $http_user_agent $badagent {
  default     0;
  # list of AI crawler user agents in "~crawler 1" format
}

if ($badagent) {
   rewrite ^ /gpt;
}

location /gpt {
  proxy_pass https://courses.cs.washington.edu/courses/cse163/20wi/files/lectures/L04/bee-movie.txt;
}

…is a wonderful thing to put in my nginx config. (you can try curl -Is -H "User-Agent: GPTBot" https://chronicles.mad-scientist.club/robots.txt | grep content-length: to see it in action ;))

…and here I am, running a blog that if it gets 15k hits a second, it won’t even bat an eye, and I could run it on a potato. Probably because I don’t serve hundreds of megabytes of garbage to visitors. (The preview image is also controllable iirc, so just, like, set it to something reasonably sized.)

It’s about 5 times longer than previous releases were maintained for, and is an experiment. If there’s a need for a longer term support branch, there will be one. It’s pointless to start maintaining an 5+ year branch with 0 users and a handful of volunteers, none of whom are paid for doing the maintenance.

So yes, in that context, 15 months is long.

/forˈd͡ʒe.jo/

Ah! My bad.

mumbles something about big corps choosing way too generic names for their stuff

Threads does not interact with the Fediverse in its current form. It’s a horn blasting into the fediverse at best. It’s not participating in the fediverse, it’s shouting into it. As such, it’s correct to not report on how thredsizens participate in the fediverse - they do not, not at this time.

Or one could buy any of the existing pre-built splits. Which might be more expensive, but it does not involve something one very explicitly said they don’t want to do.

I’d rather spend twice as much on a well built keyboard with warranty than trying to solder one together myself and botch it up, and then it suddenly costs more than if I just bought a pre-built one.

There’s a very easy solution that lets you rest easy that your instance is how you want it to be: don’t do open registration. Vet the people you invite, and job done. If you want to be even safer, don’t post publicly - followers only. If you require follower approval, you can do some basic checks to see that whoever sends a follow request is someone you’re okay interacting with. This works on the microblogging side of the Fediverse quite well, today.

What I’m trying to say is that with registrations requiring admin approval gets you 99% of the way there, without needing anything more complex than that.

…and you think 14-17 year olds won’t circumvent this in mere seconds? Like, they’d just sign up at an instance that doesn’t implement these labels, or doesn’t care about them, or use their parents accounts, or ask them, or an older friend to sign them up, and so on. Even if age verification would be widespread and legally mandated, I highly doubt any sufficiently determined 14-17 year old would have any trouble getting past it.

Yes.

Forgejo has no official Windows builds, and since it is not tested on windows at all, it’s not guaranteed to work.

Fair bias notice: I am a Forgejo contributor.

I switched from Gitea to Forgejo when Forgejo was announced, and it was as simple as changing the binary/docker image. It remains that simple today, and will remain that simple for the foreseeable future, because Forgejo cherry picks most of the changes in Gitea on a weekly basis. Until the codebases diverge, that will remain the case, and Forgejo will remain a drop-in replacement until such time comes that we decide not to pick a feature or change. If you’re not reliant on said feature, it’s still a drop-in replacement. (So far, we have a few things that are implemented differently in Forgejo, but still in a compatible way).

Let me offer a few reasons to switch:

• Forgejo - as of today, and for the foreseeable future - includes everything in Gitea, but with more tests, and more features on top. A few features Forgejo has that Gitea does not:
  • Forgejo makes it possible to have any signed in user edit Wikis (like GitHub), Gitea restricts it to collaborators only. (Forgejo defaults to that too, but the default can be changed). Mind you, this is not in a Forgejo release yet, it will be coming in the next release probably in April.
  • Gitea has support for showing an Action status badge. Forgejo has badges for action statuses, stars, forks, issues, pull requests.
  • …there are numerous other features being developed for Forgejo that will not make it into Gitea unless they cherry pick it (they don’t do that), or reimplement it (wasting a lot of time, and potentially introducing bugs).
• Forgejo puts a lot of effort into testing. Every feature developed for Forgejo needs to have a reasonable amount of tests. Most of the things we cherry pick for Gitea, we write tests for if they don’t have any (we write plenty of tests for stuff originating from Gitea).
• Forgejo is developed in the open, using free tools: we use Forgejo to host the code, issues and releases, Forgejo Actions for CI, and Weblate for translations. Gitea uses GitHub to host the code, issues and releases, uses GitHub CI, and CrowdIn for translations (all of them proprietary platforms).
• Forgejo accepts contributions without requiring copyright assignment, Gitea does not.
• Forgejo routinely cherry picks from Gitea, Gitea does not cherry pick from Forgejo (they do tend to reimplement things we’ve done, though, a huge waste of time if you ask me).
• Forgejo isn’t going anywhere anytime soon, see the sustainability repo. There are people committed to working on it, there are people paid to work on it, and there’s a fairly healthy community around it already.

Nevertheless, as Bluesky grows, there are likely to be multiple professionally-run indexers for various purposes. For example, a company that performs sentiment analysis on social media activity about brands could easily create a whole-network index that provides insights to their clients.

(source)

Is that supposed to be a selling point? Because I’d like to stay far, far away from that, thank you very much.

https://deskthority.net/wiki/IBM_Adjustable_Keyboard maybe, or https://deskthority.net/wiki/Cherry_G80-5000? Something along those lines?

I use a keyboard with 64 keys (Keyboardio Model 100), with a layout that would likely drive any normal person mad: there are no numbers on the base layer, and all modifiers are on the thumb cluster. My top row is shifted symbols like @*$^%!&. I love it. I can reach every key without moving my hand, which helped tremendously with my RSI. With clever use of layers, one-shot modifiers & layers (where one-shot means that you press and release a modifier, and it remains active for the next keypress only), I have access to every symbol available on a traditional layout and more, without having to move my hand or do weird finger gymnastics.

It’s not a keyboard I’d normally carry (it’s heavy, split, and takes up more space than a traditional full-size one), that’s not why I like it small. I like it small because I don’t need to move my hand to reach all the keys, and that increases my typing comfort a lot. I have no use for a dedicated numpad: I can just press my right palm key and turn that half of my keyboard into a numpad. If I’m typing a single digit, I don’t even need to hold the palm key. If I’m typing a longer number, I can double tap the palm key to toggle the numpad layer on, and tap it a third time once I’m done. I don’t need cursor keys, because I can tap the left palm key to turn the keyboard into navigation mode: the right side controls the text cursor (ie, arrow keys, page up/down, home/end), and the left side controls the mouse. Most of the time, I don’t even need a mouse, because I can control the pointer from the comfort of my keyboard. I do have a trackball placed inbetween the two halves for the rare cases where I require more mousing than what is comfortable with keys, but… that’s not used all that often.

So, in short, the reason I prefer small and split is because they let me type without moving my hand, or stretching my fingers uncomfortably, and I still have convenient access to every symbol I need. I might need to do a bit more “work” to type certain things, but that’s a small price to pay for the comfort I gain by not having to move my hands.

I can write at ~120WPM with this setup (but I normally don’t need to, my normal typing speed is closer to ~60WPM, because my speed is limited by thinking speed, not my typing speed), I write code with this, I write prose in both English and Hungarian, and I even play some games with it! (Most games I play with a controller though, because I can do that from the couch.)

Just because it is small doesn’t mean it can’t do everything a full-sized keyboard can. I just do the same things in a different way, with different compromises. With a full-sized one, if you want to type numbers, you either have to move your hand to the numpad, or use two hands to type something like 1994. I can type that number with one hand, without moving my hand: instead of moving hands, I switch layers. With a full-sized keyboard, if you need Home, End, PageUp, PageDown or the like, you either need to move your hand, or you need whatever program you’re using to have different bindings for the same functionality. I can just press a key to go into navigation mode, and move the cursor whatever way I like, without moving my hands, or finding an alternative binding - works in every program, anywhere - instead of moving hands, I press an extra key. I found that pressing an extra key (especially if I don’t need to hold it) is more comfortable than moving hands. I also found that not moving my hands increased my accuracy, because I don’t need to find the home position when moving my hand back: it never moved in the first place.