rosco_m68k VS matrix-js-sdk

Nice! I’d be interested to see how it handles https://github.com/rosco-m68k/rosco_m68k , it’s a mixed software / hardware repo, with a lot of code in assembler and C (for an old platform). Might be a challenge?

Probably not exactly what you’re looking for (since you mention “outdated”) but there are similar projects with 16 and 32 bit architectures, e.g. https://github.com/rosco-m68k/rosco_m68k

(Disclosure: I’m the designer and lead developer on that project).

Maybe the rosco-m68k computer kit would be up your alley. If you want to stay in z80 land, there's the omega MSX2 clone but I don't see any kits, so you'd have to get the boards and parts yourself.

Hi. The 68000 is an "old school CPU", like the 6502 and has no programmable memory inside the chip itself. To operate a 68000 system there generally needs to be some external ROM and RAM chips (and the type can vary). However, the same as with Ben Eater's 6502 and 8-bit kits, the TL866-II will likely be useful to program EPROMs and GALs on a 68000 setup also (it sure has been on the 68000 single board computer I have been tinkering with recently).

I am working on a similar project Xosera, aimed at adding video to a 68000 era home-brew system (the rosco_m68k). It is basically all working and there is a prototype PCB made. I am just finalizing "blitter" unit design and hopefully I'll have room for some "Amiga style" audio.

I'd quite like some more high level documentation for the Matrix JS SDK (https://github.com/matrix-org/matrix-js-sdk). I've been looking at it for quite some time and still don't understand how timelines work.

Currently we don't force TURN, so in practice this means that voice packets go direct between the clients if possible, and so the IP addresses of the clients are necessarily exposed to each other.

However, this is utterly trivial to fix: matrix-js-sdk already exposes https://github.com/matrix-org/matrix-js-sdk/blob/96ba061732b... and we simply haven't exposed it as a setting in Element Call yet. I've filed a bug for it at https://github.com/vector-im/element-call/issues/251 - thanks for bringing it up!

In terms of moderation: this is no different to moderation in Matrix as a whole, where we're already busy working on shared greylists (MSC2313 and friends) - https://matrix.org/blog/2020/10/19/combating-abuse-in-matrix... has more details at the end.

We expect to turn it on in the next few weeks - the problem we were debugging that we meant it was turned off looks to be fixed. https://github.com/matrix-org/matrix-js-sdk/pull/2002 is the PR that will need to merge to enable it ftr.

Unlike any open source projects to which I've contributed, this project involves 2 other repos, matrix-react-sdk and matrix-js-sdk. As explained in the Development guide in the element-web repo, I need those 2 SDKs in order to build Element successfully for code contribution.