@bender I think that's where it sends the capture verification requests. It's based on PoW, so it has to perform validation somehow. It actually looks pretty decent as far as a way to prevent spam/abuse of forms on the open web (e.g: Waitlist on SnipMail).

Scheduling the next Yarn.social Call for next month, a month in advance. Hope y'all can make the next one 🤞

👋 Reminder that we're starting up our social calls again (monthly), RSVP here 🤟 It starts in 13h27m 😅 Hope to see some/all of you there 👌

I had a looksie (just to be sure) at the database, and they were thankfully legit test events. But this did spark/trigger me to make sure I have some form of anti-spam measures in place. So I added some per-event / per-rsvp rate-limiting and honeypot(s).

@prologic so far, yup. I recommend to make the event banner bigger. I almost missed the details of it, as the text is quite tiny.

So just @bender and I attending our monly call eh?

@movq This is actually a good positive change I think!

Personally, I’ll probably stretch it out over 24 days. Giving myself more time to solve each puzzle and I really want this event to last the entire month. 😅

I might even do AoC this year with the elevated stress/pressure! -- The last few times I've tried, I've always felt far too much pressure and felt like a failure 😞 (mostly ya know because of my vision impairment, I couldn't keep up!)

Reminder, kick-starting our monthly social call! 📞 Please RSVP if you can make it!

Hey all 👋 Starring up the monthly social call we used to have 🤞 Please RSVP here if you can make it! 🙏

One of the nicest things about Go is the language itself, comparing Go to other popular languages in terms of the complexity to learn to be proficient in:

• Go: 25 keywords (Stack Overflow); CSP-style concurrency (goroutines & channels)
• Python 2: 30 keywords (TutorialsPoint); GIL-bound threads & multiprocessing (Wikipedia)
• Python 3: 35 keywords (Initial Commit); GIL-bound threads, asyncio & multiprocessing (Wikipedia, DEV Community)
• Java: 50 keywords (Stack Overflow); threads + java.util.concurrent (Wikipedia)
• C++: 82 keywords (Stack Overflow); std::thread, atomics & futures (en.cppreference.com)
• JavaScript: 38 keywords (Stack Overflow); single-threaded event loop & async/await, Web Workers (Wikipedia)
• Ruby: 42 keywords (Stack Overflow); GIL-bound threads (MRI), fibers & processes (Wikipedia)

@bender Well... I don't believe it's possible to prevent or avoid all system accidents. However, managing system safety and putting in control structures goes a long way 👌

About the nuclear power plant on the Moon, they are beating us. There was a time we were ahead, but I understand nothing lasts forever. Now, being a world power for only one hundred and twenty some years, and a super power for around seventy sure is a record (as in short-lived). The Roman Empire lasted over 500 years!

@kat Ahh my vision impairment (blind) would prevent me from even appreciating anything in paper form 😢

This expands the usefulness of Twtxt / Yarn.social to:

• Sharing small posts
• Sharing links
• Sharing media
• Having long conversations
• Voting on topics, opinions or decisions
• RSVPing to virtual or physical events

#event:abc123 RSVP: yes +1

#event:abc123 Go Meetup – Sat Apr 27, 3pm @ Darling Harbour

💡 I had this crazy idea (or is it?) last night while thinking about Twtxt and Yarn.social 😅 There are two things I think that could be really useful additions to the yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:

• Voting -- a way to cast, collect a vote on a decision, topic or opinion.
• RSVP -- a way to "rsvp" to a virtual (pr physical) event.

Both would use "plain text" on top of the way we already use Twtxt today and clients would render an appropriate UI/UX.

I do want to improve the feeds.twtxt.net service one day (soon™) with features like this. But first I'll have to prevent spammers from abusing it by introducing IndieAuth as an authentication layer.

@lyse I'm open to other suggestions 🤣 But hopefully both adding the additional prompt, not allowing it to enter shell history and removing from my shell history prevents me from doing such silly things in haste by pressing ^R and using fuzzy search which if you type fast you sometimes get wrong 😑

do you mind sharing a picture ?

I can't find something similar here, but my wife gave this one last year, and I've been using it a bit. I'd say it's useful as you've shared.

We also have a shared calendar in the kitchen for family events, and it's working great.

@eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN So instead of @eapl.me@eapl.me it will just be @eapl.me

And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)

#event Upcomming Meetup in Copennhagen: algolab(the_art_of_live_coding) @ Støberiet / Computer Klub

#event Tomorrow, Saturday October 2nd, I'm gonna be hosting a workshop at Processing Community Day CPH about Live Coding Visuals in Improviz. Only 5 spots left, so sign up now at: https://pcdcph.com

#event Upcoming Workshop / algolab: Music and Live Coding @ CPH Music Maker Space / facebook event

#event Upcoming Workshop / algolab: Visuals and Live Coding @ CPH Music Maker Space / facebook event