Discussion
@central @SinclairSpeccy for me an MSX here in the Netherlands, but maybe that qualifies more as a computer. But for me it was a console with its cassette tapes etc.
@colorcoded @central An MSX in the Netherlands makes a lot of sense with Philips making so many of them. If it played the role of a console for you then I reckon it counts
@clacke Nice! Tip for next time: treat the tent's person number as a max. With kids plus gear, size up one (a 3-person for two adults is roomy) and use the vestibule for boots and bags.
Yeah, we had space for 5-6 people in two tents.
https://whatarepasskeys.info/ conveniently leaves out the mention of the freaken remote attestation, doesn't it
Do people clean horses?
@startrekgifs Future Tense
That is not correct @darth_hideout
[w]
So when I added support for Loops to https://columnly.social, I had to refactor quite a bit to abstract MastoAPI routes and entities properly.
Not only did that open the door to supporting other software more properly, but also inspired me to look into ATProto support so you could combine all your social web accounts in one beautiful client.
No promises, but I do look forward to implementing this when I have time!
I estimate it would take a few weeks of full time development, and once I get caught up with Pixelfed, I plan to tackle this as long as it doesn't interfere with my other obligations.
The social web should be more interconnected, and I'd love to help improve that. ❤️
Or, taking a step back, even: what if I want to construct a report entirely on the Roto side?
record Config {
whatever: String,
}
fn compile_configuration() -> Result[Config, Report] {
let whatever = blabla("hello world")?;
Ok(Config { whatever: whatever })
}
fn blabla(msg: String) -> Result[String, Report] {
Err(???)
}
What goes inside Err(???)? And what should it output?
(As a side note: the working name of the Report type on the Rust side is SafeWord)
Posted in
Fediverse
After 15+ years writing software
You keep mentioning that. Do you have anything you can show off from that time?
For that matter, I also noticed no actual entity, person, name, company etc. is mentioned anywhere on your service. Not even a wider pseudonym of yours, or any way to reach you outside emailing the domain or your account on this new service.
I really wish I'd seen this stuff before! https://www.reddit.com/r/NameCheap/comments/1x493px/will_all_users_be_required_to_undergo_identity/ https://www.reddit.com/r/NameCheap/comments/1x5x6t5/account_locked_be_careful_or_arbitrary_account/
Seriously, get the fuck away from #NameCheap asap.
@neil @feff
You can use Curve in the UK - details at https://shkspr.mobi/blog/2025/06/contactless-payments-with-grapheneos/
Most of my banking apps work (not Halifax / Lloyd's though).
Okay, lets brainstorm a bit about error handling! The two places where I expect errors to happen are configuration processing, and matcher instantiation.
In the former case, I want to report errors that point to the right place in the configuration. In the matcher instantiation case... a matcher may or may not be related to any configuration item, so I need to think about both cases.
For simplicity's sake, lets consider the case when no configuration is in play. Something like:
![Another reply by "waterppk", 25 days ago:
FWIW I replied to their e-mail within 8 minutes and they took exactly 3 days to get back to me, their reply (which didn't actually confirm it wasn't a phishing message and just told me to go to the website for live chat) appears to reset the 72 hour counter:
***
Hello [name],
We apologize for the delay in replying.
If you have any doubts regarding its legitimacy, we suggest contacting us directly via the official website using online chat/email for confirmation. Additionally, the account has been locked pending this verification.
We look forward to hearing from you within the next 72 hours. Otherwise, we will be forced to suspend/cancel your services.
***](https://mastodon-usw-cache.b-cdn.net/media_attachments/files/117/573/641/842/731/704/original/d6c531cba8dbcc23.png)
record Config {
whatever: matchers.Patterns,
}
fn compile_configuration() -> Result[Config, Report] {
let whatever = matchers.Patterns.new(["foo", "bar"])?;
Ok(Config { whatever: whatever })
}
If Patterns.new() fails, what should the error report look like?
(Also, ignore that the code mentions configuration - there's no user config processing going on, it's just the framework I'll eventually arrive to.)
Or, taking a step back, even: what if I want to construct a report entirely on the Roto side?
record Config {
whatever: String,
}
fn compile_configuration() -> Result[Config, Report] {
let whatever = blabla("hello world")?;
Ok(Config { whatever: whatever })
}
fn blabla(msg: String) -> Result[String, Report] {
Err(???)
}
What goes inside Err(???)? And what should it output?
Stepped offline to play some OoT, and came back to $620 more in donations! ♥ Thank you so much, everyone, for helping fight this monstrosity of an initiative, and to speak up against hate.
@central @SinclairSpeccy I had a Pong game that hooked up to the black and white TV set. The cat would bap at the “ball” as it bounced around the screen.
@mithriltabby @central The cat trying to bap the ball is the best detail in this whole thread. Sounds like the cat got as much use out of that Pong game as you did
Paradoxalement, ne rien faire exige une énergie folle. Il faut en connaître bien peu de la mécanique intérieure pour croire qu’une personne qui ne fait rien ne fait rien.
So when I added support for Loops to https://columnly.social, I had to refactor quite a bit to abstract MastoAPI routes and entities properly.
Not only did that open the door to supporting other software more properly, but also inspired me to look into ATProto support so you could combine all your social web accounts in one beautiful client.
No promises, but I do look forward to implementing this when I have time!
RE: https://universeodon.com/@UncleDuke1969/117570062345689500
I was just talking with somebody last night about a venue in Vegas which had horse shows, and how she'd shared an elevator with a horse....
@danlyke that's better than making them take the pferdetreppe.
Recommended read - for practical reasons it is very hard to make a TCP connection to port 0, or to run a client on port 0. Yet, when acidvegas scanned the internet on port 0, they found a lot of interesting stuff:
https://acid.vegas/blog/the-port-that-does-not-exist/
@SinclairSpeccy @central there was PC gaming in between, but that is not a console so I left it out 😅
On the other hand, if I keep them fallible, that means one can - in the future - use fallible functions within them, should they wish to. If they don't, then all the fallibility requires is a -> Result[String, Report] signature, and an Ok(decision) in the end. That's very little boilerplate.
Okay, lets brainstorm a bit about error handling! The two places where I expect errors to happen are configuration processing, and matcher instantiation.
In the former case, I want to report errors that point to the right place in the configuration. In the matcher instantiation case... a matcher may or may not be related to any configuration item, so I need to think about both cases.
For simplicity's sake, lets consider the case when no configuration is in play. Something like:
record Config {
whatever: matchers.Patterns,
}
fn compile_configuration() -> Result[Config, Report] {
let whatever = matchers.Patterns.new(["foo", "bar"])?;
Ok(Config { whatever: whatever })
}
If Patterns.new() fails, what should the error report look like?
(Also, ignore that the code mentions configuration - there's no user config processing going on, it's just the framework I'll eventually arrive to.)
Feel bad about hoarding RAM that could be used by Sam? No worries, I just launched https://uploadyourram.org/ so you can give your RAM to those in need
Sorry, the app encountered an unexpected error
