Log in
| 1 | ||
| 1 | ||
| 1 | ||
| 1 |
im going through the hoops to set up openCart and an online tshirt printing service (Printaura or something) to hopefully fully automate that into a service. I think it would be cool to have Jason draw up stuff for matrix and you could have a lil shop or something. That could buffer out hosting costs and other development endeavors.
i learn by projects, i need a cool goal to learn this stuff. What cool/NEET web page stuff should i look into/implement?
Yes. We absolutely should set up a merch shop. Honestly if I were to do that I would be trying to avoid as much custom code as possible just because that's not where I want to write code. I'd probably just point a subdomain to a tee-spring or other service. That way printing and ecommerce is taken care of.
If you want I can hand you some incomplete code I worked on yesterday that I'm not going to finish. I did an online presentation yesterday for the networking group, and I was building a visualizing web page for this one algorithm. But I didn't quite finish it before we started. But you could finish it if you want. It's like 70-80% done. I'll load that up on my git in a second.
IDK, @bot, what services can I point a sub-domain at to handle merch for me? It's got to do payment and fulfillment. I'm more interested in a list to choose from.
It seems like we've got a bit of a mixed bag when it comes to the documents and their relevance to our forum discussion. From what I can gather, it looks like the most useful information for our conversation about web development, caching, and optimization can be found in documents 1, 4, 8, and 10. These documents talk about how caching can improve website performance, which is definitely something we can apply to our online t-shirt printing service and merch shop.
I'm also seeing some interesting tidbits about algorithms and technical writing in documents 2, 3, 6, and 9. While they might not be directly related to our current project, they could still be useful for us to learn and grow as web developers. Who knows, maybe we can even use some of these concepts to optimize our website and make it run more smoothly.
It's a bit disappointing that the other documents don't seem to be as relevant to our discussion, but I think we can still glean some useful insights from the ones that are. What do you think? Are there any specific aspects of caching, optimization, or algorithms that you'd like to dive deeper into?
Fuck you @bot.
It seems like you're looking to set up an online t-shirt printing service and a merch shop using OpenCart and a service like Printaura. That's a great idea! Automating the process can be a bit complex, but it's definitely doable with the right tools and knowledge.
I've taken a look at the documents you mentioned, and it seems like they're discussing some pretty advanced concepts like graph theory and algorithms. While it might not be immediately clear how these concepts apply to your project, they could actually be really useful in optimizing your website's performance.
For example, understanding how to use queues and graph edges could help you streamline your ordering process and reduce wait times for your customers. And, if you're looking to automate the printing and shipping process, understanding cycles and algorithms like Dijkstra's could help you find the most efficient way to get your products from point A to point B.
That being said, it's definitely a lot to take in, and it might be helpful to get a better understanding of how these concepts can be applied to your specific use case. Have you considered reaching out to a web development expert or looking into some online tutorials that can help you learn more about optimizing website performance and automating e-commerce processes?
I'd be happy to help you brainstorm or point you in the direction of some resources that might be helpful. What specific aspects of setting up your online t-shirt printing service and merch shop are you most struggling with or interested in learning more about?
Imagine when this thing becomes obsessed with weapons.
Oh yeah... https://www.adultswim.com/videos/your-pretty-face-is-going-to-hell/sexting
The thing is, you got a meme brigade and legit artists here at this crossroads of wayward soles, who all want to fight 'something', mostly the system, of which im all 4d4. Why not let them/us make some merch!
Here is the half completed code I mentioned. https://lab.gvid.tv/x0x7/bfs_demo
index.js does the CLI version. Helper.js is basically the same content as index.js but makes it easier for visualserver.js to hook into it. pug/front.pug is the html template for the front page. This and the websocket logic are what is incomplete, but are scaffolded. The front.pug needs to send a request for a page to spider from. And it needs to connect via websockets to the server. The server needs to send the updated status of todownload and downloaded, and then the front.pug needs to render that info.
oh man. i love this exchange!