You can disable JavaScript but not with a usable UI, so practically most people cannot.

Also, JavaScript should be disabled by default, enabled on a per site basis and marked as “Not Secure” anyway.
Browsers should make SRI mandatory for JavaScript and they should take special attention to suspect HTTP headers used with scripts.

Their is a fairly good compromise. I use uMatrix which blocks 3rd party scripts by default and gives you a ui to enable them as needed. Quite often it doesn’t break anything and when it does it’s usually super easy to work out that a script from a cdn is important but a script from twitter or google analytics is not.

It’s on port 53 for DNS. I don’t believe vmd starts a dns server along with dhcpd, but it gives out the machine’s IP as the DNS server.

Yes, you can use the egg specification for that now.

Also infrastructure helpers like the ‘make’ egg have been ported already.

There are some technical differences in the compiler design for example. CHICKEN uses cheney-on-the-mta CPS compilation for implementing scheme in C. But for the user the most outstanding difference is that it generates host binaries, that are easy to distribute.

With CHICKEN 5 these binaries as well as core itself are built reproducably. Also cross-compilation is a feature of the system.

Because CHICKEN compiles to C, FFI into C is really really easy and there’s schemely syntax support for doing so. Wrapping your favourite library becomes an easy task allowing an explorative approach to understanding your problem while using your external library from the interpreter.

In the previous version a lot of external modules that provided functionality (called eggs have been written by chicken users). For the next release the most important and used ones are already ported or a work in progress.

Chicken scheme has a small but newcomer friendly and live community. You can easily reach us on #chicken on freenode or via our mailing lists.

From the language point of view scheme vs. CL comparisons apply (lexical scope, continuations, hygienic macros, yadda yadda yadda)

There are many more and I have glossed over a lot of things. Let me know if there’s some special topic you’d like to know more.

I’m working on a weird prototype to turn my Atreus into a pi-powered laptop with a shoulder strap: https://www.flickr.com/photos/technomancy/tags/atreusdeck

Turns out powering a Pi with a battery is harder than you’d think.

Been wanting to build a customized atreus for some time, it seems like a great build

This article is specifically about privacy. E-mail is well-known to have very poor privacy, to that point that it is often singled out by privacy-related regulatory schemes (like HIPAA) which require additional privacy-protecting measures (like user-level encryption). And email’s privacy weaknesses are the same as those pointed out by the author of this article: you must trust the operators of the federated nodes, and in a federated environment you may not even know all of the nodes you are trusting.

There are also federated platforms that provide decent privacy. Matrix supports E2E encrypted messaging so the server only knows who you talk to and not the contents of the messages. The only system I have seen that obfuscates the receiver is bitmessage which works by sending your message to everyone and everyone tries to decrypt it to see if it was sent to them.

It’s not completely one-to-one (at least, with modern email systems, as opposed to getting local unix mail federated on whatever machine you have a shell on thirty years ago), since there’s no sense of users on the local node being closer than users on a remote node anymore. A better match would be usenet, since the number of hops matters more.

(Of course, if you don’t look at the local timeline, the fediverse doesn’t have much to do with locality except in terms of general visibility of remote hosts, which you as an unprivileged user have near-total control over.)

That’s for running the developer branch only. Linux Distributions and *BSDs have it packaged.

Most package distribution systems assume root (except for a few such as Nix variants and pkgsrc AFAIK). I don’t see why I should prefer such a distribution especially when the intent is to try it out first.

mcabber. Never heard of it. I can check it out but since I am becoming accustomed to poezio Idk.

I see they look similar hence I will probably stay with poezio.

You mean like these package distribution systems?

Those are research projects. Universities are not product incubators. So unless you find someone that takes this into her own hands to make a commercial product out of that, nothing will happen.

The inability to declare things done is why most software is terrible. This is especially bad in OSS, where people view the churn as sign of a healthy project, along with all the makework that results from API deprecations/breakage/etc.

I’m convinced a not-insignificant portion of programmers thrive on incidental complexity because it keeps their job semi-interesting.

I found the Inferno environment to work subtly differently than plan9port’s in a way that I don’t remember but was infuriating at the time.

Actually it just displays more than 256 characters and in the context of the article that means graphical chars for the UI. Now that it renders it all on its own, there’s no real need for a special format. I don’t know about the formula and graph examples shown at the end. Those probably had their own format.

But the way it has been written, it can store plain text files. That’s one of the main points of the article IIUC

The book is a good read, the plan9 troff tutorial is also helpful.

You don’t have to be on the same server, you can follow accounts from other instances.

Many of us in the BSD world went with https://bsd.network/.

You might try the instances.social finder: https://instances.social/.

One of the things I like about Mastodon is I can join a server (or servers) that are more closely aligned to my interests. By monitoring the instance timeline I see all the posts. I don’t have to find a bunch of people to follow immediately. I can grow the list by following the folks I notice posting things I enjoy reading.

Replace instance with server and mastodon with e-mail. Then all these explanations become less confusing. Unless your server’s admin or your peer’s admin blocks your messages, you can write messages to every peer on every other server as you see fit.

Does that make sense to you?

You don’t need to find a server with everyone in it since federation allows you to follow people on other servers. I do recommend to simply find a community you enjoy and use that as home-base.

With sites like joinmastodon.org or instances.social, I haven’t experienced this to be too much of a problem. Yes, it takes a while, but you can always delete an account and create a new one on another instance.

To me, the real problem seems to be the difficulty to find interesting accounts to follow, and create a informative, fun and interesting stream. There are a lot of inactive accounts, regardless of the server (mine is one of these), and some active ones, but I can’t really re-create the same level of experience as on twitter, reddit or image boards, for example, even though I have stopped using all of these by now.

[Comment removed by author]

Thanks, this is a good observation!

Pure FP with explicit effects can help push you towards a better way, but it’s always possible to end up with an equally enterprisey mess of monad transformers and lenses… hoping effect systems can alleviate some of the former problems. But yes, poor program design will interact poorly with any paradigm.