Hey author here. AMA (about the book). I know there are many books to read out there so let me add the book has at least one positive review by Poul-Henning Kamp of Varnish-Cache and FreeBSD fame:

> You don't need to be stuck on a bus between Oslo and Göteborg to enjoy reading this book: [...] Much interesting stuff to think about for the thinking and practicing programmer.

https://toot.community/@bsdphk@fosstodon.org/109829843037038...

But that's enabled by the DNS MX record. There isn't anything like that for social AFAIK, so if you wanted to do the same with your mastodon account you are hosed. Some people are saying once you have million followers on mastdon.social, you are not going to restart from zero on mastodon.net. You can, but it's hard. So centralized or federated, without handle portability, it's not very different. You are stuck. It seems to me federated mail and federated social are similar for people who don't own their DNS entry (gmail addresses), but for people like you, that's a substantial difference. You'd have to run your own instance to have your own social handle, and that isn't portability, that's DIY. It only works for a small number of techies, you have to have an instance and a domain.

> so if you wanted to do the same with your mastodon account you are hosed

I don't believe that's true:

https://blog.maartenballiauw.be/post/2022/11/05/mastodon-own...

Also https://masto.host/how/ and https://simonwillison.net/2022/Nov/8/mastodon-is-just-blogs/

> Some people are saying once you have million followers on mastdon.social, you are not going to restart from zero on mastodon.net.

i think we should have learned by now that when “some people are saying…” we should be very skeptical if those claims are based in reality.

in this case, they’re not. if you wish to move from .social to .net you move your account and your million followers go with you.

> anything like that for social

If I understand correctly, /.well-known/webfinger should do the trick.

I’m “at” the same long term domain in several protocols—

  @name@mydomain # ActivityPub
  @name:mydomain # Matrix
  name@mydomain # Email

—and none of those services are actually run by the server behind the A record.

How about the web-of-trust a la freenet https://github.com/freenet/plugin-WebOfTrust?

You lose all your followers. It's like going from blacklight@aol.com to blacklight@gmail.com. It's on you to go to you 1M followers and beg them to refollow you. The goal is to go from tmobile to verizon and your grandma can just call you.

On Mastodon people who see your old profile would get a screen like "this profile has moved here".

Ok, it's still on them to follow you on your new profile, but it's not like you have no connection between the old and new profile.

And I'm among those who want to improve this feature, so actual data exchange (followers and posts) can happen before the two instances during the migration.

Can anyone name a well-known important software project (say linux, python, tensorflow, angular) that was delivered via Agile/Scum? And some of you may enjoy this linkblog https://againstscrum.tumblr.com/

What are the shortcomings of Wordpress, Tumblr etc and how did you address them? Thanks

And when a post starts by lying by a factor close to 2 about the rate of obesity (42% 2018-2019 per CDC as opposed to 71%) what else in this post is trustworthy?

FYI, Ozonetel bid successfully for the top line ad in my google search [ozonetel], dialpad taking second. You don't get there if you don't bid.

I am not sure that's what he or she was trying to say. Agree with everything you said about native apps. The question for me is if it's necessary for every page to run javascript, even if it doesn't have any app-like features, even if it's just a document. I would love to be able to turn off javascript and be able to browse the document-web without everything being broken. In the specific cases where I need dynamic or app-like behavior, then I can use javascript, or maybe even a separate app browser. https://www.wired.com/2015/11/i-turned-off-javascript-for-a-...

It seems to me the authors make three main points 1) Pay-per-action confuses correlation (action when seeing ad) with causation (action because of seeing ad). Hence click-through-rate maximizes correlation instead of causation. Google knows you were going to buy anyway, thus serves you an ad. 2) Marketers and ad networks interests' are aligned in that they want to maximize advertisement budgets. Hence marketers will ignore randomized studies showing ads of some type are not effective. 3) Even when these studies are performed, even major sample sizes are insufficient to support any conclusion