btrower · HackerTrans

3 năm trướcdiscuss

I liked CamelCase. The brackets are okay. They solve problems, but as you say (or at least imply) they create new problems that can make the code less elegant (IMO). As a user, the brackets are better, but as a programmer it be a headache. We invented, independently, network hyperlinks before the WWW and they were used in our lab, I don't remember how we did the links. The programmer is no longer with us, but I've messaged the person who had them done to see if he remembers. It only worked on our LAN, so amusing, but not as insanely compelling as the WWW. I'm curious to see if either CamelCase or [[]] was that natural a mechanism.

btrower

3 năm trướcdiscuss

We do need c2.com. I was just thinking about wiki because it looks like I'm going to need to train a few people and I was wondering what Ward (not my dad) was running at c2.com I built a bunch of pages there and although perhaps the development ideas are not leading edge (or new?) any more, I at least like to look up the stuff that I wrote there. Also, I don't know who is using what out there, but crucial rules of thumb on that wiki are not followed and the continued fragility of systems is a result. That community was, let's say, idiosyncratic, but all good communities are, IMO. I am still very much hoping that c2.com comes live again, with improvements, and that stuff like federation gets hammered out. There are two things that I liked about wiki: 1) Its elegant, user friendly design/philosophy/ethos. :) 2) Its workingness. :( I am so glad I stumbled on this site. Bookmarking. If anybody cares, the query that got me here was: What is c2.com running? I just wanted to know the OS in case I wanted to send code along. Here is a design improvement I would hack in, just for the insanity of it: Add a Generative Pre-trained Transformer so you could type in ... aw nuts. You could get it to write something for you like this: Automated content generation: You can issue commands to the GPT backend to write about specific topics and have it generate content for the wiki page. This can be useful for quickly populating or updating pages with relevant information.

Collaborative editing: With the GPT backend, you can allow visitors to temporarily rewrite the wiki page to their liking. This enables collaborative editing, where multiple users can contribute and modify the content while ensuring a history of changes is maintained.

Intelligent refutation: You mentioned the ability to issue a disagreement and instruct the system to refute the previous content. By integrating GPT, you can prompt it to generate counter-arguments or provide alternative perspectives to foster a balanced discussion.

Personalization and anticipation: Over time, the GPT backend can learn from user interactions and get to know individuals personally. This can enable it to anticipate their preferences, interests, or even the types of content they are likely to contribute. Such personalization can enhance the user experience.

Aesthetic improvements: You can instruct the GPT backend to optimize or rewrite its own code to make the wiki front end more aesthetically pleasant. This may involve generating CSS styles, layout modifications, or even interactive design elements based on user preferences.

Intelligent linking: By leveraging the GPT backend's language generation capabilities, you can automate the process of hyperlinking important terms, concepts, or keywords in the wiki content. The system can identify relevant sources, explanations, or further reading materials and dynamically add hyperlinks for easy access to additional information.

comments