2xsaiko

Here’s a demo one that works on rooted Android: https://github.com/Hirohumi/RustyRcs/

(Also iOS 18+ Messages lol)

It’s not RCS’s fault Google locks down the API on their OS.

No it’s not. Get the spec here: https://www.gsma.com/solutions-and-impact/technologies/networks/rcs/universal-profile/#download

deleted by creator

Don’t use passwords for public SSH in the first place. Disable password authentication and use pubkeys.

Not an app, but one thing I can recommend that is pretty much “for free” is to turn on iCloud Advanced Data Protection, that gets you end-to-end encryption for pretty much all iCloud storage (photos and so on).

Everything else I would recommend is probably not going to happen (such as deleting Discord) or of questionable benefits (such as using the web version of Discord instead of what is probably the app) :^)

Looking it up, seems like it’s something you will only find on original UNIX. So probably nothing you have to worry about in reality tbh.

Registrars (or DNS providers if you don’t use the one that comes with your registrar) worth using have an API to manage DNS entries. That’s basically all there is to DynDNS.

Keep in mind that some killall implementations do not take arguments and instead literally kills all processes. You might want to use pkill instead.

Are they implying the police are accountable for anything?

It would need some sort of way to hook into the compositor. PowerToys has it easy because they can just add the necessary APIs to the Windows compositor if it doesn’t already have them. And I feel like compositors would just implement it directly instead of designing an API for it because that’s less complex.

Rewriting huge parts of the IDL compiler for Nucom, my implementation of Microsoft’s COM binary interface standard and (in the future) network protocol. The original version was hacked together with a lot of assumptions made in the parser and isn’t very extensible, and I do need to extend it now.

(Nucom is another way to have a stable ABI for Rust, e.g. for a plugin interface, and for Rust/C++ (and more OOP-style C) interop, based on objects with vtable pointers. And hopefully sometime in the future, transparent IPC and networking so you don’t have to load plugins into your process’s memory space if they don’t need to be there, with it working the same as if it were direct calls. All of this I assume you can already do on Windows with the windows-rs crate but it’s obviously Windows-only.)

I do have to say though, I need a better way of transforming my syntax tree. Right now I’m just copying the struct definitions over and over for each compile stage and manually writing code to copy everything instead of just the parts I’m actually transforming, and it just seems like there has to be a better way. I might want another proc macro for this.

Someone else who has the Omnia! I agree, it’s a great router.

It offers no practical benefit to small networks at the moment.

The internet is not a “small network”, and I assume your small network is connected to it. You need local IPv6 routing to have access to IPv6-only hosts which are becoming more and more because it’s reasonable in terms of price to get an IPv6 block unlike IPv4 blocks which are being auctioned for tens of thousands of dollars at this point (!!!).

Also restoring global addressing is a huge benefit. P2P communications in IPv4 has become an insane mess of workarounds due to lack of addresses and this becomes worse the more layers of NAT you stick behind each other to try to save your ass from the rising tide.

I’m really sick of hearing these idiotic excuses over and over, “it’s hard” this, “it’s unsafe” that, “it’s expensive”, “understanding the eldritch secrets of IPv6 has driven 5 of my colleagues into madness” skill issue. THERE ARE NO MORE IPV4 ADDRESSES. So unless your network is so fucked that you haven’t managed to fix it in 26 years, since IPv6 has been standardized, or it really is just an internal network with no outward facing services where it doesn’t matter when someone who just has IPv6 can’t access it because they wouldn’t be able to access it anyway, and you’re not some kind of ISP, you have no reason not to have support for it at this point and you absolutely never have a reason to tell people it’s not “useful” because that is straight up wrong in the general case even if it might be true for your situation.

This is an old one (like around 2010), but Street Gears. It was an inline skating MMORPG that I spent a lot of time in when I was young but it eventually got shut down. I loved it and there hasn’t been anything like it since.

Traits like std::io::Write are essentially Strategy pattern. Take a look at how that’s used. You’re doing it mostly how I would, except for the Box<dyn T>. Generally it’s preferred to use generic functions/types in Rust instead of dynamic dispatch, i.e. have a fn do_something<T: MyTrait>(imp: T) instead of a fn do_something(imp: &dyn MyTrait).

They’re FIDO keys but bad.

Here’s a great blog post from someone who knows what they’re talking about: https://fy.blackhats.net.au/blog/2024-04-26-passkeys-a-shattered-dream/

I don’t know if there’s anything ready for use, there’s a library and demo app here: https://github.com/Hirohumi/rust-rcs-client

RCS is a carrier protocol, like SMS

Oooh, saving this for potential D&D games or other storytelling purposes. Thanks!

Borg is great and I use it myself but afaik there is no Windows version and there is only remote support over SSH, not HTTPS.