I've been reading the "garage door open" posts here on hacker news, and figured others might be interested in this project. The project is just the examples in "c programming language" by Kernighan and Ritchie written in library form. I reviewed some github repos that other people have posted here on hackernews and tried to copy their style. Rather than putting "main.c" in the top directory, I put the library in the top directory, and tests with main functions just use the library. Everything in the book is likely already in <stdlib.h>, <stdio.h> or <string.h>, but it is useful to go through to see how the underlying functions work. While going through the book, I've been inspired to create a few other projects using the functions from libkr as the base. You can see those here: https://dmillerfork.codeberg.page
Technologies: HTML, C, React, JavaScript, TypeScript, Node.js, Express, CSS, Claude, Bash, AWS, career in patents, but looking to branch out; specialization in finding white papers and related documents on any topic
Resume:
- Examiner at USPTO (9/14/2020 - Present)
- Software Dev at Structure.io (5/21/2020 - 9/11/2020)
- Student Founder at Startup School (8/20/2018 - 11/5/2018)
- Associate at Hickman Palermo, LLP (6/02/2014 - 1/1/2017)
- Associate at Mitchell + Company (5/22/2013 - 5/30/2014)
- Law Student at Golden Gate University School of Law (9/1/2010-5/1/2013)
- MSE Student at Georgia Institute of Technology (9/1/2004-5/1/2009)
I love this as a concept. The wander button is great, but it still needs some curating to decide what pages you like, and getting to the actual content. I guess I'd like to know the workflow moving forward? Just re-download the repo every couple weeks, and diff to see what new sites are on the list?
Thank you for taking a look at this project. I'm glad you like the concept. I am not sure I have understood your question accurately, but let me attempt a response anyway. If I get it wrong, please feel free to correct me or ask me again.
There is no need to re-download https://codeberg.org/susam/wander every few weeks. The setup is a one-time activity. From that repository, you copy exactly two files (index.html and wander.js) and place them on your web server, preferably within a /wander/ directory. After that, you only maintain the wander.js file.
You curate your own links and choose which other Wander consoles to link to as neighbours. The contents of wander.js are entirely yours to define. There is no need to diff or compare it with the version in the repository.
In fact, if you do not care about updating or curating links often, you can leave both files untouched indefinitely. The only downside is that some links may eventually succumb to link rot, which could affect the wandering experience. So it may help to review your links occasionally and remove dead ones, but beyond that no ongoing maintenance is required.
I get that, but right now, if you traverse each "console", you end up with a list of 28 trusted "small web" links. The project grows in value if that list gets bigger over time either by you personally adding nodes or the community adding nodes. I don't really have a way of knowing if you are intending to add more links to your console (thus growing the project) or this is a one and done type of system.
> I get that, but right now, if you traverse each "console", you end up with a list of 28 trusted "small web" links. The project grows in value if that list gets bigger over time either by you personally adding nodes or the community adding nodes.
Yes, all of this makes sense.
> I don't really have a way of knowing if you are intending to add more links to your console (thus growing the project) or this is a one and done type of system.
I personally do not plan to add too many page links to my console. However, I will add more console links, which has the effect of expanding my console neighbourhood and thereby increasing the pool of recommendations.
That said, I am not sure why it matters whether I add more links to my console specifically. In my opinion, any single Wander instance should not matter much on its own. What matters more is whether the network as a whole grows, that is, more consoles being set up and more of them linking to each other.
One of my design goals has been to avoid giving any particular console a special status. All consoles are equal participants in the network from a technical perspective. You should be able to pick any console from the network, perhaps one belonging to your favourite blogger, perhaps even your own and explore the neighbourhood from there. Yes, the neighbourhood would look different from each console but that's pretty much the point of this project. As long as the overall graph of consoles is connected, you could in theory reach any community recommendation from any starting point. Even if the graph is not fully connected, I do not see that as a significant issue. It just reflects how connections tend to form in a decentralised system. Please let me know if you think I have missed your point again.
I like what the article is going for, but I would prefer to have the actual const { parentPort } = require("worker_threads") code and everything below it at the top. Everything else is fluff.
I built a tool to do this and supported it for 6 months, but I couldn't really find users. The basic idea was a web page that you could collaboratively work on through a server running socket.io, which included editing css, fonts, and the content of the website. The collaborative idea sounds cool, but in practice, it seemed easier to have a team pair program on a zoom call and edit a page live with google dev tools. Is there a reason this solution doesn't work for you?
The first site looks prettier, but the newer site actually explains the concept. You still need to work on your copy. "Point out in the description what you could do for the advertiser and how the advertiser would benefit in choosing your team" -> what? Could be a lot easier to understand. How about "Request sponsorship for your team or event"
Thanks for the feedback! We are looking for more info on user needs in this space. Sounds like you currently use Alteryx + Snowflake. Any additional information you could provide about your use case/needs would be helpful. Seems like some people are more interested in open source tools that can be run on their own computer (like DBT) while others are looking for more of an enterprise use case. What about you?
Demo looks great and I really like the user interface. Nice and clean. I went looking for pricing however and did not see anything on your website nor did I see anything indicating your are in beta. Is this a paid service and if so what is your pricing structure?
Hi Replwoacause! Do you have any additional information on what your individual needs might be? It would be very helpful to us to know what tools you currently use, and why those tools are useful to you. We have received a lot of positive feedback and some feature requests, so we are trying to group feature requests by common use cases.
