PRIMARY USER
Sam
@samcity
Currenty seeking more exciting trials and tribulations to assign DNS records to
and hands on directly with the backend.
DIRECTORY :: Spectrumcore
You are here:
@spectrumcore-node.uk
Project Spectrumcore is an independently hosted Matrix homeserver. Progression has moved past the initial goal. Feel free to dig around. Real updates ought to be made clear from fantasy elements and flavour text.
AuxSpec: Wavar Grid
CH. 07.22c
MODEHeartbeat Tracing
SOURCEPassive Monitoring
STATEOFF (503: Service Unavailable)
01 / SERIOUS TALK
Spectrumcore-node.uk
Matrix came before the domain as a solution for my disabled parents to have a clean and easy communication platform. Beforehand, comms within the family involved a lot of shouting up and down.
The homeserver went live once learning about Matrix during a search for a fresh messaging application. Comms were improved.
But wait? Why not use other established internet messaging apps? Um.. Passwords. (Mainly me ol' man)
Once setting up docker, synapse was deployed, IP was made static. Then my dad leaves the house to get shopping. Oops, we cant reach him.
Did I have to convert our lil' local synapse messaging to a proper internet based domain? There was certainly a good reason to. Why did I do it? Plain sick of Fluffychat for my phone being REAL picky because we lack https.
Looking back, think I did it for fun. Could have easily abandoned it. But pshh, the rabbithole was deep and I knew I had tumbled before I had even started the local setup.
Now I'm here, maintaining the node and ensuring it remains a reliable space for comms. Best part? My Mum liked "x" matrix platform, my Dad could use "y" platform. I was able to use Fluffychat, Element, and despite our differences, even Thunderbird mail.
You're now here, reading this and I'm sure I have plenty of stories to tell you. Allow me instead to get started on working a forum for this website, directly on this website, lookin' snazzy. I'll update and fill in what else came next, what I'm working on, and...
I'm totally allowing the forum space to be public. I'll be keen to see you there!
P.S. This domain is, and will be used for further online platforms. Dedicated Minecraft IP? Solved. Personal Cloud? On the way. Need a NAS.
Look forward.
02 / MATRIX
WE HAVE DISCORD AT HOME
I didn't make Matrix itself, I have to respect the rules of E2EE and security of info.
The Spectrumcore homeserver provides accounts and community rooms through the open Matrix protocol. Joining starts with a conversation, so new members know who runs the space and what to expect.
How the server works and how to join ↗- Homeserver
- @spectrumcore-node.uk
- Stewardship
- Independent
- Joining
- Talk to an operator
- Protocol
- Matrix
03 / OPERATORS
People behind the node.
Apart from myself, I have a single trusted operator running the social space with me.
ADMINISTRATOR & SOCIAL RELATIONS
CloudyWindz
@cloudywindz
Same power. CloudyWindz is a pillar of the journey. Happy to help, primarily Matrix focused.
SERVICE IDENTITY
Admin account
Administrative use
Master handle. Inquiry processing.
⋯⋯⋯
Everything beyond this point is mostly proof of concept, playful experimentation, and the occasional “weee”.
04 / SIGNAL LAB
Band monitor | Loss rate | Ping vs Feed
These instruments are visual sketches, not server monitoring. That distinction is part of the design.
Band MonitorSignal / Modulation Layer
Carrier drift, modulation bloom, and the faint suggestion of a locked signal behind the public feed.
NODE TREEModel: PingPong
Node Mapping: Station Ping Response & Tower Metrics
OFF AIR
AUXILIARY SPECTRUM
Last Uptime (DDMMYYYY): 080326
Auxiliary Spectrum comes from an unknown broadcast. Partnered with LFSS, signals are recorded from a dish array. When a ping is received, operators at LFSS will aim the array to align with the ping origin point.
After first receiving from 2019, the signal was put through multiple processing methods. Only to be decoded by an anonymous user once the files were published. Decoding was never required, anonymous user slowed down the audio.
Formula: raw signal duration = slowed duration × (1 + slowdown ÷ 100).
Example: 9:21 = 561 seconds; 561 × 8.22 = 4610.82 seconds, or about 76 minutes 51 seconds. So every 1 second of the broadcast before processing is actually 8.22 seconds when played back at normal speed.