social.coop

0 posts0 participants0 posts today

jbobH@sunbeam.city saw some mentions from you on my old account on the <a href="http://social.coop" rel="nofollow noopener noreferrer" target="_blank">social.coop</a> instance, this is the current one :) I’ve been making slow but steady progress on <a class="hashtag" href="https://antisocial.2soc.net/tag/rainpsc" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> but mostly on the software side, in fact yesterday I started a new project that ties a number of efforts together. I’ll have a blog post about it soon. <a class="u-url mention" href="https://mastodon.social/@vertigo" rel="nofollow noopener noreferrer" target="_blank">@vertigo</a>

jbobMy <a class="hashtag" href="https://antisocial.2soc.net/tag/rainpsc" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> project got kind of stalled when I got focused on how to finish the control panel in a "non-one-off" way. Ironically the complexity of producing PCB's that met the needs snowballed into a bigger project than I had time for and the whole project got hung-up. Recently I started getting into "freeform" electronics and it got me thinking about what I could apply that style to. Yesterday it occurred to me that maybe I could get RAIN moving again if I looked at the panel as a freeform circuit design exercise instead of something I could "mass" produce. So now I'm noodling on how I might "charlieplex" the entire panel and use a single MCU to drive it from the head node instead of making a separate interface for each node. If I can make this work, it simplifies things a *lot*. Of course that means a lot of point-to-point wiring, and it's completely impractical for building more than one or two machines, but if it gets the working machine on my desk sooner, it's probably the way to go.

jbobRan across this yesterday, might be a handy way to add some (large) mass storage to <a class="hashtag" href="https://antisocial.2soc.net/tag/rainpsc" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> <a href="https://ameridroid.com/products/odroid-hc1" rel="nofollow noopener noreferrer" target="_blank">https://ameridroid.com/products/odroid-hc1</a>

jbob<a class="u-url mention" href="https://toot-lab.reclaim.technology/@djsundog" rel="nofollow noopener noreferrer" target="_blank">@djsundog</a> let me know what you think of the Rock; I’m considering upgrading the front-end node of <a class="hashtag" href="https://antisocial.2soc.net/tag/rainpsc" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> if only to get some more massive mass storage.

jbobStill trying to figure out everything that this device does, but for $12 it might be a low-risk (har har har) way to start playing with RISC-V (and potentially have utility in the ML-related workloads I'm experimenting with on <a class="hashtag" href="https://antisocial.2soc.net/tag/rainpsc" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a>): <a href="https://www.seeedstudio.com/Sipeed-MAix-BiT-for-RISC-V-AI-IoT.html" rel="nofollow noopener noreferrer" target="_blank">https://www.seeedstudio.com/Sipeed-MAix-BiT-for-RISC-V-AI-IoT.html</a>

jjgFirst post in a series in which Jason learns how to use a <a href="https://sunbeam.city/tags/bigdata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bigdata</a> / <a href="https://sunbeam.city/tags/ml" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ml</a> framework:<a href="https://jasongullickson.com/posts/learning-spark/" rel="nofollow noopener noreferrer" target="_blank">https://jasongullickson.com/posts/learning-spark/</a>(don't tell them, but as soon as I know this stuff I'm going to use it to empower the proletariat...)<a href="https://sunbeam.city/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a>

jjgWorking on a new chassis for <a href="https://sunbeam.city/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a>. Needed something simpler to get the cluster operational sooner now that I have some specific applications to run and not just benchmarks.

jjgConsidering developing an sbc-oriented HPC linux distro.Something to make building & operating ARM/etc. based clusters that seem to be becoming more common. I need this for <a href="https://sunbeam.city/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> anyway, and it's in-line with my mission of making HPC more accessible.The idea is to make setup & config easier & standardized (akin to what ROCKS does for Intel clusters), deals with some of the SBC-specific oddities and provides some built-in frameworks, languages & tools for HPC & cluster computing (as well as examples & benchmarking tools).sound useful?

jjg<a href="https://hackers.town/@sundog" class="u-url mention">@sundog</a> coincidentally, <a href="https://social.coop/tags/rainpsc" class="mention hashtag" rel="tag">#rainpsc</a> was designed to replace a stack of 8 DL380 G5’s of my own.I’d be happy to give you some for parts if you’re willing to pick them up 😁

@h<a href="https://freeradical.zone/@CharredStencil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@CharredStencil</a> If you're interested, you can read more about these projects under the <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kestrel</a> and <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> hashtags. Also isee <a href="https://mastodon.social/@vertigo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vertigo</a>'s and <a href="https://social.coop/@jjg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jjg</a> 's blogs. I don't blog (much yet) because I suck at it. I'll eventually become a better blogger, when I'e upped he quality of my output, and I have something real to show.

@h<a href="https://freeradical.zone/@CharredStencil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@CharredStencil</a> Not exactly, the yet inexistent TerminaThing project is a non-web libre hypermedia terminal project. Both hardware and software-only implememtations will be specified and built. Apart from that, I've been coming up with the idea of potentially hookiing up the TerminalThing with <a href="https://mastodon.social/@vertigo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vertigo</a> 's free/open <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kestrel</a> computer, and <a href="https://social.coop/@jjg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jjg</a> 's <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> high performance computing cluster. All aimiing to be as free as realistically possible. No timeframes can be predicted for availability yet.

@h<a href="https://nerdculture.de/@kragen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kragen</a> If no data is ever sent back to the main controlling computer, nothing is ever sent back to the main controlling computer. Therefore nothing <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> or terminalthing can do can ever affect <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a> if set up that way.The problem I do envision is the other one I mentioned in a separate toot, which is in cases where terminalthing or rainpsc have to send data back to <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a>. For example, the HPC component has to send back the results of a compute-intensive cryptographic service.

@hWhen payload is send by <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a> to <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> to perform a job, and the result of that job is sent directly to terminalthing without any of it touching Kestrel again (say rainpsc decoding an x.265 video and TT displaying it) that can never present a security problem. Other than seeing something you didn't want to see, security is never compromised. The problem is when <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> and <a href="https://mastodon.social/tags/terminalthing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#terminalthing</a> need to send data back to the controlling computer (<a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a>)

@hK+R+TT problem pending:- terminalthing and <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> will depend on some non-free hardware, so they will be considered untrusted by default. - terminalthing will provide authentication services so the user never touches the main controlling computer (<a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a>) before being authenticated. - rainpsc can provide compute-intensive cryptography and RNG to <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a> and TTDevising ways to vouch for data originated from an external system (like the internets) is going to take extra thinking.

@hIf TileLink were to be used as the bus to send memory updates between <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a>, <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kestrel</a> and terminalthing, imagine a scenario where Kestrel would be commanding terminalthing to create a new GUI window, send an encoded x.265 video to rainpsc, with rainpsc decompressing the video, and refreshing the frame inside the terminalthing window that kestrel controls.<a href="https://mastodon.social/@vertigo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vertigo</a> <a href="https://social.coop/@jjg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jjg</a>

@hEssentially, hypermedia terminalthing is going to be a software-only reference implementation being developed in parallel with the hardware terminalthing. The hardware terminalthing may have to depend on some components that aren't fully free yet, but as the state of the art progresses, those will be eventually replaced with free parts (like the HD+ VGA subsystem that could potentially work in tandem as a video adapter for a free computer like <a href="https://mastodon.social/@vertigo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vertigo</a>'s, <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kestrel</a> and <a href="https://social.coop/@jjg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jjg</a>'s <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a>

Vertigo<a href="https://wandering.shop/@hummingrain" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hummingrain</a> <a href="https://icosahedron.website/@mona" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mona</a> Thankfully, there are a number of different FOSS/FOSH computer projects that agree wholeheartedly with your analysis, many of their creators are here in the Fediverse. There's <a href="https://social.coop/@jjg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jjg</a> who is working on <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a>, a personal super-computer design. My own project, <a href="https://mastodon.social/tags/kestrel3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kestrel3</a>, aims to fill that niche right in between a Commodore 64 and an Atari ST; a 64-bit RISC-V processor that boots into a Forth environment, and with hardware that will be fully open and documented.

jjgFeeling confident enough with <a href="https://social.coop/tags/fossil" class="mention hashtag" rel="tag">#fossil</a> to try using it for a real project (<a href="https://social.coop/tags/rainpsc" class="mention hashtag" rel="tag">#rainpsc</a>):<a href="https://fossil.2soc.net/cgi-bin/repo/rain/dir?ci=tip" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://fossil.2soc.net/cgi-bin/repo/rain/dir?ci=tip</a>So far the only problem I've found is the links in my README are broken :)Cool thing is that if things work out and I decide to make the switch permanent, it's pretty easy to synchronize with a git repo should someone need to interact with the project that way.<a href="https://fossil-scm.org/index.html/doc/trunk/www/inout.wiki" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://fossil-scm.org/index.html/doc/trunk/www/inout.wiki</a>

@hApart from the obvious duties of a graphical display device, TerminalThing would also be useful from the point of view of dystems security, authenticating users on behalf of the main CPU (<a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kestrel</a> or others). Only after the user is authenticated will TerminalThing be allowed to send data to or request data from the main computer component. For example, there will be no way that TThing can send mouse or keyboard input to <a href="https://mastodon.social/tags/kestrel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kestrel</a> or <a href="https://mastodon.social/tags/rainpsc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rainpsc</a> before a user is authenticated.

jjg<a href="https://mastodon.social/@vertigo" class="u-url mention">@vertigo</a> <a href="https://mastodon.social/@haitch" class="u-url mention">@haitch</a> Even with funding I think the "when it's done" approach is preferred. I'm sure we've all experienced what happens when a project is accelerated by throwing money at it...I'm in a similar boat in that I'm using ARM in <a href="https://social.coop/tags/rainpsc" class="mention hashtag" rel="tag">#rainpsc</a> until alternatives are ready. That way I'm not blocked and can let alternatives evolve at their own pace.For me the key is modularity, with a focus on quality interfaces that could work with future configurations.

Recent searches

Search options

Administered by:

Server stats:

#rainpsc