@fossham I honestly think the most unique and interesting thing about doing this at all is that it is in fact inspired directly by Twtxt / Yarn.social itself -- That is to say, I am confident I can do this in such a way as to be "truly decentralised", no inter-networking like ActivityPub, no centraised forges like Github or Codeberg. You run your instance, I run mine, we just are able to collaborate. Think exchanging patches over Email, just without all the hard-to-learn ways to do that (enough though it's not hard for some of us, but still).

@itsericwoodward Dropped you en Email 📧

@david heads up 👋 that verification code never reached you — outbound email was broken on my end (my mail relay was rejecting twtxt.net senders 🤦‍♂️). Fixed + deployed now 🥳 give the hosted feed another go, it'll land this time 🤞

@balloon-fu-sen Thank you for reaching out 👌 I had alraedy done so via Email too a few days back and she upgraded her Pod to yarnd/0.16.x 🎉

@david Well... I can't! becuase the email supplied was nobody@invalid or some shit™ 💩

@GabesArcade LOL You can Email me, hit me up on Signal, orc IRC. Take ya pick I'm around 😅

@GabesArcade by asking me nicely 🤣 Which you just did! If you either provide me a desired username and password and secure medium to give this to you I can do that easily, or alternative a desired username and email address (never stored, only hashed), after which you can "Reset password".

The auDA, and some 3rd-party identify service and my Registrar are a joke!

WOW! I just had to share this little story I ran into today.

I tried to register a .AU Domain the other day, only for it to instantly fail.

I emailed support, which took several days to respond, only for them to respond by saying (paraphased):

We're sorry, but the identify checks failed. The 3rd-aprty service doesn't tell us why, But, please make sure that the ID you used matches the Full Name, including any Middle name(s).

I used my Passport number. Which of course has my First, Middle and Last Name.

I can only assume at this point that the checks failed on the missing "Middle name". Why? Because the Registrar I use has a database and user interface for "contacts" that only have support for First name and Last name. NO Middle Name.

🤦‍♂️ This is basically stupid at this point. Systems cannot be trusted at the most fundamental level, no matter how good they are.

Until we figure out how to build a system that allows an individual to prove to another entity that they are who they say they are without a shred of doubt (i.e: cryptographically), we're stuffed.

There is literally nothing I can do in this case. The auDA are at fault. The 3rd-party identify service (unknown) are at fault. The registrar are at fault. Hell, even the Passport office are at fault for even bothering to or requiring a Middle name.

How has "identity" come to this?

I'm building a service that lets you:

create and manage disposable, brandable email aliases so you can track leaks, forward important messages, and keep your real inbox clean.

I've just finishing building it for the most part, and have cut a v0.1.0 release. It's currently closed source (to be decided later) and now open to beta testers. cc @bender 🙏 I fully intend to monetize and offer this as a paid service in teh coming weeks/months, but beta/invite-only testers and early adopters/users first 🤟

I keep getting this email occadionally:

Your iCloud storage is almost full

Now for various reasons, I don't want my children to be using iCloud to store data, files, photos or any of the sort. They're free to use iMessages, and other Apple services like the App Store, etc, but not storage.

So I've set about blocking iCloud Storage API(s) via AdGuard Home tonight as well as ensuring that my local network (client users) cannot bypass DNS policies and get out other sneaky ways, because some applications will just use other DNS servers, or DOH or DOT.

Just like we don't write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our twtxt.txt feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience

Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation