driusan.net

Technology (Page 1 of 6)



2024-05-25T02:36:52.294Z (Technology)
By @driusan@doomscroller.social at Sat May 25, 2024 at 02:36:52AM GMT

I almost hacked up my webfs enough to open a websocket connection to ws://echo.websocket.org but I don't know if I'll be able to finish it because webfs isn't really intended to be full duplex and I don't know how to write to the connection after opening it.


2024-04-27T00:07:36.525Z (Technology)
By @driusan@doomscroller.social at Sat April 27, 2024 at 00:07:36AM GMT

What alternatives are there to vultr for hosting? The last week or two the network has been.. not great, but only for my 9front server. This one has been fine.



2024-03-14T13:00:16.620Z (Technology)
By @driusan@doomscroller.social at Thu March 14, 2024 at 13:00:16PM GMT

what are the options for writing a simple blog that's hosted over rc-httpd? Requirements are rss feed and content written in markdown. Doesn't need to be dynamic or include comments. The only one I can think of is werc. Is there anything else?



(Technology)
By @moody@hj.9fs.net at Sat February 3, 2024 at 20:20:59PM GMT
snac2 works pretty well with , just keep your password in factotum. Mothra and hpost both work without having to login every time, webfs takes care of all of that.

2024-01-18T19:27:36.079Z (Technology)
By @driusan@doomscroller.social at Thu January 18, 2024 at 19:27:36PM GMT

I turned it off for security reasons, but I shall now consider my proof-of-concept rcpu over websocket implementation conceptually proven.


2024-01-08T00:34:15.050Z (Technology)
By @driusan@doomscroller.social at Mon January 8, 2024 at 00:34:15AM GMT

I'm probably getting ahead of myself, but I wrote a simple cloning protocol for my experimental bug tracker / source control thing and some documentation. Since the cloning protocol is written in rc, it can bootstrap the system. If you're a or user I'd be interested in feedback.

The install documentation is at
http://code.driusan.net/pq. The usage documentation is in the man page pq(1) after installing.

The general concept is described in the link above, but basically:
1. The source control history based on bugs and patches, not trees and commits messages.
2. The system tracks bugs
3. A try is an attempt to fix a bug, described in terms of a patch
4. Every commit is associated with a bug/try and has a snapshot attached

It's currently only really useful for single-user work/management, but it's bootstrapping itself pretty well and I'm pretty happy with it as a user, but I'm also biased, so I'd be interested in having some other developer(s) play with it and give feedback.