pull down to refresh
Because you can't really "compress" code much, right? You need to actually re-architect and provide standards relevant to your project.
Or, you need to include more design requirements in your initial plan. If you work too organically, you end up with a mutant creation.
Me, I have a team to make things real. So my vibes live as R&D prototypes, not production code. This way we can encounter all the problems and decisions once before doing it "for real."
IMO be careful with sweeping rules like this, as they naturally conflict with the ai using its own judgment, which improves with every update.
Tip: tell the ai to make the rule for you so you can see how it interprets your desires instead. Just explain what you dont like conversationally.
These rules you listed are way too general imo, which means sometimes they will be the wrong rules.
Also, why not use ai to refactor and rearchitect code you think is slop? If you can define your requirements, ai can help.
Subjectivity is the exact thing the system allows. There is no mention or hint of "absolute truth" in any content I have provided.
You need to think of the graph more like 'the part of the web you can possibly see' and then about how in an open web that means you need some process for reducing the "firehose" down to something drinkable every time you are viewing it.
In the contemporary web, this context is provided by your apps, app settings, and central moderation (for both legality and "the algorithm").
In a p2p web, the users can provide it through context tagging, but it needs to be done across both peers AND content, like URLs, events, locations, etc.
A "territory" here in StackerNews, or a "subreddit" is no different than a tag in the semantic social graph from one key to a post. The tags already are the topics. The tags can also be thread topics, or, you can simply repurpose the primitive of a 'headline' or title for an article with a forum topic. How an app presents the data does not actually require many different data.
Similarly, you can then apply distance filtering across any topic or set of topics, with you at the center, and include the entire firehose if you really want to. There is not a limit to your ability to discover new info, there is only a limit to what any single indexer could include in their graph, same as with Google, or X, etc. But here, the graph data is owned by the users and assembled by the indexers.
Also, don't forget that most people are always connected to many networks, with many sources of new info. Echo chambers only exist for people that create them intentionally, they aren't a phenomenon of tragedy of the commons, or bad design, or something.
We never stopped building, it's just depressing that our peers are sheep that think they are lions, so all we can do is fight each other over nonsense instead of rallying behind what makes sense.
Hmm I wonder if Pubky has a protocol... maybe I should check before I say something ignorant... hmm let's see, oh wtf is this, a whole fukn github org with all the open source code? It has specs? And docs? Oh wow I'feel so retarded right now, what was I thinking?!
well, i do prefer rules like "don't ask the user to do things you can confidently do yourself"