# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 193911
# self = https://watcher.sour.is?offset=191991
# next = https://watcher.sour.is?offset=192091
# prev = https://watcher.sour.is?offset=191891
Exigimos ao governo de Portugal o mínimo. Que:
1. Condene a agressão ilegal ao Irão por parte de Israel e dos Estados Unidos da América;
2. Proíba o uso de infraestruturas e do espaço aéreo português para qualquer tipo de apoio aos ataques;
3. Aplique sanções ao Estado de Israel pelas suas consecutivas violações do Direito Internacional e pelo genocídio em curso na Palestina;
4. Reconheça de imediato o Estado da Palestina.
Assina-se aqui: https://actionnetwork.org/forms/parar-a-guerra/
#Portugal #Israel #petição
Exigimos ao governo de Portugal o mínimo. Que:
1. Condene a agressão ilegal ao Irão por parte de Israel e dos Estados Unidos da América;
2. Proíba o uso de infraestruturas e do espaço aéreo português para qualquer tipo de apoio aos ataques;
3. Aplique sanções ao Estado de Israel pelas suas consecutivas violações do Direito Internacional e pelo genocídio em curso na Palestina;
4. Reconheça de imediato o Estado da Palestina.
Assina-se aqui: https://actionnetwork.org/forms/parar-a-guerra/
#Portugal #Israel #petição
What ChatGPT cannot give you is that short moment, when you put down the pen, look at the written words, and have those peaceful seconds of silence in your head.
[47°09′49″S, 126°43′56″W] --white noise--
[47°09′30″S, 126°43′23″W] 4449 days without news from Herve
#MaradoWeekly #WeeklyPlant Week 25 
Blackberries going from red to black
#MaradoWeekly #WeeklyPlant Week 25 Blackberries going from red to black
#MaradoWeekly #WeeklyPlant Week 25 Blackberries going from red to black
@lyse Multi-Threading. Is. Hard. 🤯 And yes, that blog is great. 👌
@lyse Multi-Threading. Is. Hard. 🤯 And yes, that blog is great. 👌
On today's research journey on pledge(…)/unveil(…)/landlock/capabilities I came across the great EWONTFIX blog, in particular this article here: https://ewontfix.com/17/ Super interesting.
[47°09′23″S, 126°43′28″W] Saalmi, retransmit, please
Welcome Gopher - Welcome HOME !
Oh lovely, the spam bot found my blog, I guess. Until now I only flagged spam, I guess I'll have to switch to auto delete now 🙄
[47°09′10″S, 126°43′24″W] Transfer 99% complete...
❤️ 🎶: A Handwritten Letter by Jung Seo Joo
[47°09′04″S, 126°43′58″W] Transponder still failing -- switching to analog communication
🧮 USERS:1 FEEDS:2 TWTS:1380 ARCHIVED:87754 CACHE:2699 FOLLOWERS:22 FOLLOWING:14
bought the new server that'll replace my optiplex 780 woooo!!! new server is a lenovo thinkstation P520
bought the new server that'll replace my optiplex 780 woooo!!! new server is a lenovo thinkstation P520
He agregado un hilo sobre RISC a nuestro BBJ!
I was this 🤏 close to buying a couple of baby-cactus plants but, I couldn't ... I still have to save up for that _future_ screen printing project. 🥲
Visit the Rabbit Hole - telnet to woofer.v6.rocks:9999
Greetings from Mt. Healthy, Ohio
[47°09′33″S, 126°43′21″W] Transponder malfunction
❤️ 🎶: BamBamBam by RESCENE
[47°09′12″S, 126°43′23″W] Transfer aborted
❤️ 🎶: Because of You (Female ver.)（《我心深触》电视剧插曲） by KLANG
No Kings! No Leaders! No Oligarchs!
I just released a hotfix for the Komments plugin you should install asap:- It prevents that malicious characters in the comment text are saved and can lead to problems- It prevents that comments are not saved in certain setups with the new avatar service#komments #getkirby #kirbycmshttps://maurice-renck.de/en/notes/2025/komments-hotfix
[47°09′39″S, 126°43′13″W] Bad satellite signal -- switching to analog communication
[47°09′09″S, 126°43′02″W] Transfer completed
@andros U2FsdGVkX1+wW86OnF/lYcTVjdFNiZVxOk+cLn+R9x4/bYvi6/7CvZo0gZvfUeQDxZpv1hOLg5J5kgSLsnK8bg==
[47°09′18″S, 126°43′39″W] Transfer 75% complete...
For Gopher:// exist a lot bunch solutions for Windows, stop raping Internet Explorer :)
🧮 USERS:1 FEEDS:2 TWTS:1379 ARCHIVED:87753 CACHE:2701 FOLLOWERS:22 FOLLOWING:14
@andros U2FsdGVkX1/5aYInTCCOWUN6v2vxQ7GpiHsg3ajd5U1dznWOrBNYAnOhyd+s96ckC/pYkSPTu/lZsMPQLmhXsA==
@lyse lol – I explicitly kept them in there so that the code is easier to understand for non-Rust people 🤪😂
@lyse lol – I explicitly kept them in there so that the code is easier to understand for non-Rust people 🤪😂
[47°09′47″S, 126°43′13″W] Transfer 50% complete...
@prologic Bon voyage! I hope you'll find some well-needed rest.
@movq All the returns tell me that you're not a real Rust programmer. :-D Personally, I would never omit them either. They make code 100 times more readable.
@movq Yeah, not too bad. I completely agree with you on completeness. Also, I hate complexity without having to learn that during on-calls. :-)
Finally, the two drawers are mounted on the workbench. Some kind of a lid board on top to keep the dust out is still missing. I also gotta build the drawer inserts for the saws.
I upcycled decades old table football aluminium pipes to become my handles. The spacers are made from the inner tube. Two minutes of handsanding with 400 grit sandpaper polished it up nicely.
Drawers on the workbench
https://lyse.isobeef.org/tmp/hobelbankschubladen/
[47°09′22″S, 126°43′15″W] Transfer 25% complete...
❤️ 🎶: We Were So Beautiful by J-Cera
❤️ 🎶: Rest In You by YUJU
❤️ 🎶: NAL BEO RIN NAM JA by Oh YooJin
❤️ 🎶: Kotoba by Rimi Natsukawa
Someone has an iMac? I think they have all gone because of keypad problems.
❤️ 🎶: With Your Love by HYNN
I only have internet explorer 6. Therein gopher not blocked.
[47°09′13″S, 126°43′15″W] Waiting for carrier
@prologic I’d say: Yes, because in Go it’s easier to ignore errors.
We’re talking about this pattern, right?
f, err := os.Open("filename.ext")
if err != nil {
log.Fatal(err)
}
Nothing stops you from leaving out the if, right? 🤔
@prologic I’d say: Yes, because in Go it’s easier to ignore errors.
We’re talking about this pattern, right?
f, err := os.Open("filename.ext")
if err != nil {
log.Fatal(err)
}
Nothing stops you from leaving out the if, right? 🤔
@movq I'm feeling SO dumb right now 😅 I used to think !! was a sudo argument and never used it out of that context! Thanks for the $(!!) tip 🤘
@movq Is this much different to Go's error handling as values though really? 🧐🤣😈
(Of course, if we’re talking about a project you’re doing for a customer and the customer keeps asking for new stuff, then you’re never done, and you have to think ahead and expect changes. Is that what they mean? 🤔)
(Of course, if we’re talking about a project you’re doing for a customer and the customer keeps asking for new stuff, then you’re never done, and you have to think ahead and expect changes. Is that what they mean? 🤔)
Saw this on Mastodon:
https://racingbunny.com/@mookie/114718466149264471
> 18 rules of Software Engineering
>
> 0. You will regret complexity when on-call
> 1. Stop falling in love with your own code
> 2. Everything is a trade-off. There's no "best" 3. Every line of code you write is a liability 4. Document your decisions and designs
> 5. Everyone hates code they didn’t write
> 6. Don't use unnecessary dependencies
> 7. Coding standards prevent arguments
> 8. Write meaningful commit messages
> 9. Don't ever stop learning new things
> 10. Code reviews spread knowledge
> 11. Always build for maintainability
> 12. Ask for help when you’re stuck
> 13. Fix root causes, not symptoms
> 14. Software is never completed
> 15. Estimates are not promises
> 16. Ship early, iterate often
> 17. Keep. It. Simple.
Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.
Saw this on Mastodon:
https://racingbunny.com/@mookie/114718466149264471
> 18 rules of Software Engineering
>
> 0. You will regret complexity when on-call
> 1. Stop falling in love with your own code
> 2. Everything is a trade-off. There's no "best" 3. Every line of code you write is a liability 4. Document your decisions and designs
> 5. Everyone hates code they didn’t write
> 6. Don't use unnecessary dependencies
> 7. Coding standards prevent arguments
> 8. Write meaningful commit messages
> 9. Don't ever stop learning new things
> 10. Code reviews spread knowledge
> 11. Always build for maintainability
> 12. Ask for help when you’re stuck
> 13. Fix root causes, not symptoms
> 14. Software is never completed
> 15. Estimates are not promises
> 16. Ship early, iterate often
> 17. Keep. It. Simple.
Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.
Okay, here’s a thing I like about Rust: Returning things as Option and error handling. (Or the more complex Result, but it’s easier to explain with Option.)
fn mydiv(num: f64, denom: f64) -> Option {
// (Let’s ignore precision issues for a second.)
if denom 0.0 {
return None;
} else {
return Some(num / denom);
}
}
fn main() {
// Explicit, verbose version:
let num: f64 = 123.0;
let denom: f64 = 456.0;
let wrapped_res = mydiv(num, denom);
if wrapped_res.is_some() {
println!("Unwrapped result: {}", wrapped_res.unwrap());
}
// Shorter version using "if let":
if let Some(res) = mydiv(123.0, 456.0) {
println!("Here’s a result: {}", res);
}
if let Some(res) = mydiv(123.0, 0.0) {
println!("Huh, we divided by zero? This never happens. {}", res);
}
}
You can’t divide by zero, so the function returns an “error” in that case. (Option isn’t really used for errors, IIUC, but the basic idea is the same for Result.)
`Option` is an enum. It can have the value Some or None. In the case of Some, *you can attach additional data* to the enum. In this case, we are attaching a floating point value.
The caller then has to decide: Is the value None or Some? Did the function succeed or not? If it is Some, the caller can do .unwrap() on this enum to get the inner value (the floating point value). If you do .unwrap() on a None value, the program will panic and die.
The if let version using destructuring is much shorter and, once you got used to it, actually quite nice.
Now the trick is that you *must* somehow handle these two cases. You *must* either call something like .unwrap() or do destructuring or something, otherwise you can’t access the attached value at all. As I understand it, it is impossible to just completely ignore error cases. And *the compiler enforces it*.
(In case of Result, the compiler would warn you if you ignore the return value entirely. So something like doing write() and then ignoring the return value would be caught as well.)=
Okay, here’s a thing I like about Rust: Returning things as Option and error handling. (Or the more complex Result, but it’s easier to explain with Option.)
fn mydiv(num: f64, denom: f64) -> Option {
// (Let’s ignore precision issues for a second.)
if denom 0.0 {
return None;
} else {
return Some(num / denom);
}
}
fn main() {
// Explicit, verbose version:
let num: f64 = 123.0;
let denom: f64 = 456.0;
let wrapped_res = mydiv(num, denom);
if wrapped_res.is_some() {
println!("Unwrapped result: {}", wrapped_res.unwrap());
}
// Shorter version using "if let":
if let Some(res) = mydiv(123.0, 456.0) {
println!("Here’s a result: {}", res);
}
if let Some(res) = mydiv(123.0, 0.0) {
println!("Huh, we divided by zero? This never happens. {}", res);
}
}
You can’t divide by zero, so the function returns an “error” in that case. (Option isn’t really used for errors, IIUC, but the basic idea is the same for Result.)
`Option` is an enum. It can have the value Some or None. In the case of Some, *you can attach additional data* to the enum. In this case, we are attaching a floating point value.
The caller then has to decide: Is the value None or Some? Did the function succeed or not? If it is Some, the caller can do .unwrap() on this enum to get the inner value (the floating point value). If you do .unwrap() on a None value, the program will panic and die.
The if let version using destructuring is much shorter and, once you got used to it, actually quite nice.
Now the trick is that you *must* somehow handle these two cases. You *must* either call something like .unwrap() or do destructuring or something, otherwise you can’t access the attached value at all. As I understand it, it is impossible to just completely ignore error cases. And *the compiler enforces it*.
(In case of Result, the compiler would warn you if you ignore the return value entirely. So something like doing write() and then ignoring the return value would be caught as well.)=
[47°09′23″S, 126°43′06″W] Sample analyzing complete -- starting transfer
[47°09′21″S, 126°43′33″W] Not enough data -- sampling finished
/https://duque-terron.cat/media/photos/IMG_4752.jpeg) #catsoftwtxt