Every time I hear the name Rumsfeld, I am reminded of the time when, for over 10 minutes, he refused to deny being a lizard:
1,334 karma · joined November 6, 2013
Edit: In fact, you can partly use the same system with pen and paper:
Prioritizing a task when adding it is way less stressful than deciding which one to do just before doing it.
Jeremy Lyon gave a very good 101 explanation about the concepts and thought process:
The content creator/moderator knows that if the hosting service starts acting iffy, he exports everything to a different host, keeps the same domain, no one knows he even moved. Much smoother.
The problem with federation is not the technology, is that the technology is packaged as a platform.
(1) Content hosting (2) Content browsing
This way, the /r/BikeShedding community can buy a domain, say, BikeShedding.gg, and connect it to a content hosting platform that delivers a standard API + web UI. This is (1).
Users will have an app, let's call it FrontPage, in which they can put it a domain to subscribe to, or pick from a list, exactly like we can use podcasts app today to either add a manual RSS feed or choose from the library of feeds an app offers.
Podcasts are the pinnacle of decentralization yet I haven't heard once the word "federation" or had to choose an "instance".
If someone wants to talk about this more, email to anything at weedon and scott [dot] com. I did apply to YC with this, but it got rejected -- maybe the time is ripe.
Edit: Important to note that this works for all platform overreach cases -- Avoiding YouTube censorship, exiting Twitter's echo chamber, and yes, for Reddit as well.
The problem with federated platforms like mastodon is that they are still platforms, and platforms suck. You replace horses with cars, not with slightly better horses.
I wrote a booklet about avoiding common pitfalls a few years back[0], and really the approach of the business is the most important thing after employee compatibility.
The current (semi-implemented) design is that each file or collection of files can be assigned a step in a pipeline and version controlled separately, and steps can be defined as dependencies of one another.
This makes it possible to add "compute" steps that do not track any file but instead run a task, achieving a similar goal.
> ...Even in the desktop version, Firefox's sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn't happening for their Android browser yet.
Apple doesn't care about it because their customers don't care about it. Stop buying and they start caring.
It all started with the sudden (obvious, I may be slow) realization that dating apps only have "dating app people" (DAP) on them. This leads to an inherent flaw in dating apps. If all or most of the ideal matches of a person that's on an app are _not_ DAP, well, apps will always be detrimental to that person. Not only will it be impossible to find true matches there, the matches that are found are just a waste of time.
This main problem is accompanied by many other problems -- lack of chemistry judgement, profiles doctored to change the person (naturally), and more.
The solution? A magic wand that when you wave it you start randomly bumping into your ideal matches wherever you go. Barring that solution, we must rely on "selective friends transitivity".
Friends transitivity means that if A and B are friends, and B and C are friends, A and C are also friends. This is surely false. However, I bet it is selectively true. If A and B are friends, both A and B know which of their other friends will be liked by the other.
Which brings us to Eventful. Eventful is an app that allows people to create and be invited to real life events. It then facilitates sharing invites to that events in a way that promotes selective transitivity, and not only in dating. This is true to any kind of gathering where meeting new people is desirable, say weekly basketball neighborhood games. Those people you meet will surely connect you will more people outside of Eventful.
A host can decide "how deep" of an invitee can still invite, all while Eventful makes sure not to overflow the venue, and to let an automatic waitlist know when a place had opened up. This kind of event accounting is impossible to do by hand with something like Instagram or WhatsApp.
I wrote more than I planned, hopefully it was interesting to read.
* Released just a couple days ago, very usable but a little buggy. Update comes up these next couple of days that solves most of them!
I hope in the coming few months to release the "ready-made" solution for that, at which point there will be what to show on the home page.
The lack of productivity comes from the methodology those tools implement. Their methodologies contributed a whole lot but by now we are used to that contribution, and so we must advance it.
Nestful implements a methodology I call "spontaneous productivity". In which there is no planning. Nestful will tell you what is the next thing you need to do, and that is it. Currently you have to know the methodology very well and "do it by hand", but I am very close for a smooth UX.
Either way, my point is that improving upon Trello or Asana is like honing a sharp sword. At some point, we need to switch to a gun.