honestly, if the end result is public ownership, I don’t particularly care how it is achieved. With the number of infrastructural issues and the catastrophic loss of potable water as a result, any means is appropriate. Money is constructable, life is finite.

GEKOLONISEERD

Unfortunately, the US is taking advantage of this axiom. Their unfettered drive of “influential” content amounts to, essentially, an undeclared cultural invasion.

Sadly, just one lemmy instance doing this won’t change much. The US has been invested in destroying my country since the 1970’s.

I can’t say that Russia or China are any better, before anyone asks.

It almost certainly is designed to run indefinitely, this exact same coffee maker has been in production since the nineties or so. the only addition is the timer circuit, which is very clearly a much later addition, as the supporting structure is markedly different tk the rest of the device.

Anyway, a 240v switch is in order, I think. Fortunately we still have Farnell here in the UK, I shouldn’t like to pay international shipping fees for a single switch from china.

ah, I should have cottoned on in my first reply. the reason it switches off is EU regulation, not for any safety reasons. The machine otherwise looks exactly the same as any kther coffee maker in the world.

The fire hazard is no greater for removing the timer, there’s a bimetallic strip in there that will detach from circuit if the thing gets over 90ish degrees. It’ll just keep cycling like that. Microwaving coffee tastes, in my opinion, worse.

I suspect that the IC is the eight-pin thing I saw in the top left. It appears to be the only one there tbh, but it has a coating over it to hide the labeling for some inane reason. Bah.

I habitually use a clean install whenever I move OS - so much so that I’ve been buying new storage drives for the sake thereof. I actually have one ready to go for Trixie, once I finish a current project.

clipboard…

This just sounds bothersome. A clipboard should really be machine-wide, that’s the purpose of it. Although I can understand the reticence there, what with password managers. I would argue that, to achieve that sort of security, there should be a separate, “secure” clipboard that only enrolled applications can access - and enrollment should be left up to the user, not the application developer.

RDP

How do you approach RDP? Do you have multiple monitors at all? Is your approach scriptable? The reason I ask is because I can easily access my machines like so:

exec xfreerdp3 /u:<user> /p:<pass> /v:<address> +f +clipboard /drive:/home/<user>>,Z: /drive:/,Y: -grab-keyboard /monitors:0,1 /multimon

This can be added to a script that also checks the state of the target machine, and boots it via my IPMI console if necessary, waiting until the machine is ready to login. And, as you’ll note, I can specify which monitors I would like to provide for the connection. grab-keyboard allows me to set a keyboard shortcut that minimises the remote session, and you’ll note the mapped drives also. This is pretty much the lowest level of functionality I’m after. If that can be replicated on Wayland, that’s at least one hurdle down.

On the contrary, they provided a piece of information that I’m very interested in. They’re hardly shilling.

Oh, no, sorry. I mean that I can’t appear to get any posts from mastodonapp.uk, whether by relay or federation

fedibuzz alleges that you can follow a single specific instance with their relay, and I see nothing to suggest that I can’t use it better federate with mastodonapp.

I did note, though, that both my instance and mastodonapp are connected to relay.intahnet.co.uk - and whilst it has a few issues in the logs, it has none since i reset the instance again after attempting limited federation mode.

But ruby is so hard :(

I come from c# land and my skills are soft and squishy

You don’t need something huge. Remove the DVD drive and the old mechanical drive from a USFF machine, stick a pair of 4TB drives in it, and put a basic debian image on it. Configure SMB with a shared folder or two, and voila: you now have a comfortable NAS for maybe £20 plus drives. Add in a sata pcie card if you can find a decent low-profile one, and that’s an extra four or even six drives. It won’t give you the cream of top performance, but it will be perfectly serviceable for a homelab.

Hmm. Git is far too organised for my play style. I may take photographs at some point, assuming I can actually find components (and learn how to do… well, any of this).

After a night’s thought, this might be an interesting idea. Although I’d need to figure out how to add a programmable interface to it.

Neither. This is a purely personal project, and I’m using as much off-the-shelf as possible. The dac itself doesn’t have to be top of the line, just decent. The PCB itself I’ll probably just have printed, rather than trying to breadboard it or make some ungodly wire mess.

Some stuff I can get for almost pennies, like a USB-C controller and the actual sockets and plugs, so this is a non-concern. The actual dac chip though, I’m expecting (or at least hoping) to find something around the £30-£40 mark, although this may well be aspirational. That said, this is something I can theoretically transplant to my next device, and the next after that, assuming I create custom housings for them.

I’ve put some thought into it, but realistically I lack the experience to flesh out the idea.

I’ve seen a few small DAC concepts out there, like https://www.elektroda.com/rtvforum/topic4091483.html or that iPhone modification that Strange Parts did a few years ago, but none of these really 100% match my needs. As for the sizing, the only real answer I have for you is “small” - whilst it is intended for integration into a phone, I’m going to be building a housing for that phone from scratch, so the size requirements are somewhat led by the dac itself. I had a few ideas about using a flexi-strip in place of a solid PCB too, but I think that’s aiming too high for my non-existent skillset. Instead, I have no problem redesigning the board to be long and thin if necessary, or squat and fat in the alternate. Realistically, it’s probably going to be somewhat L-shaped, but there’s a good two inches or more of width and something like six inches of height to work with - minus the PCB of the phone, that is.

The actual handset it will be accompanying is a Sony Xperia 1 IV, but that’s largely meaningless as we can add pretty much any additional size to it up to a reasonably large handset within the last ten years (preferably with an OLED display, but I’ll be somewhat limited in terms of compatibility anyway and might have to end up running the screen in an alternate fashion somehow, I haven’t thought too hard about that side of things because the project is useless if I can’t design a DAC inthe first place).

The heatsink stuff was really just a suggestion, I’m not actually sure if it will be necessary, but it’s good to have the option.

Specifications wise, it essentially needs to do four things:

• Pass any connected headset microphone through to the handset
• Run an EQ that is addressable and configurable from the handset
• Have a volume ceiling at least comparable to a fifth-gen iPod video (i.e. a wolfson chip)
• Take power from, and pass data and power through to, the existing USB-C socket on the handset.

The bit that I’m stuck on, really, is the addressable EQ. I could possibly go with some sort of Arduino-esque solution, but that’s a lot of lifting for a single-purpose device. I have no idea where else to start looking - I know there are RISC chips out there that run on nothing but a button cell, but again I’m clueless as to whether or not this is a good idea.

I’ve looked at these, but they lack the integrated amplifier (afaik) and the configurable equaliser. Those are two super important features that pretty much break the idea for me.