# 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 235518
# self = https://watcher.sour.is?offset=230136
# next = https://watcher.sour.is?offset=230236
# prev = https://watcher.sour.is?offset=230036
May be no joke chronically ill...fascinating
🧮 USERS:1 FEEDS:2 TWTS:1222 ARCHIVED:84353 CACHE:2826 FOLLOWERS:17 FOLLOWING:14
Sagem - My Dual Radio 700 - hat wieder Sender Einfach, weil es so schön ist.
@lyse Die meisten Hersteller von Internetradios (Sony, Denon, Marantz, ...) binden einen externen Dienstleister (vTuner) fest(!) in ihre Geräte ein, damit die Nutzer sich durch eine große große Liste von weltweiten Internetradio-Stationen hören können.
Nun hat vTuner seit ca. 2020 sein Geschäftsmodell geändert. Man darf da nun für jedes Gerät (MAC-Adresse) bezahlen. Die Kosten steigen auch von $3 auf $7 pro Jahr. Die Hersteller zucken einfach mit den Schultern. Im schlimmsten Fall schaltet vTuner einfach die Domain ab und dann steht man da - wie bei mir: http://sagem.vtuner.com
Der XML-Parser von der alten Sagem-Huddel verlangt zeilenweise Einträge ohne Einzüge. Vielleicht standest Du mit Deinem Parser ja Pate!? 😉
@arne Hahaha, vor Dekaden hab ich auch mal einen „XML“-„Parser“ selbst gebaut. Der wollte dann pro Zeile entweder einen öffnenden oder einen schließenden Tag oder aber einen Wert haben. :-O Ganz übel, aber für den damaligen Anwendungsfall hat's gelangt. War halt bloß kein XML. :-D
Was konkret war dann das Problem von dem zu sauberen XML in Deinem Fall? Und schön zu hören, dass Du das Gerät vor dem vorzeitigen Elektroschrotttod bewahrt bekommen hast. :-)
Zum Abschluss noch ne ganz doofe Frage, ganz offensichtlich hab ich von Radios keinen blassen Schimmer. Wieso muss denn das Ding überhaupt mit XML rumfuhrwerken? O_o
LECK MICH FETT!
Das Küchenradio (Sagem - My Dual Radio 700) gibt wieder Töne von sich! Der XML-Parser von dem Ding ist sowas von hinüber. Die "Fertiglösungen" YCast und YTuner haben ein zu ordentliches XML erstellt. Per Trial and Error habe ich dann die Formatierung gefunden, die die olle Kiste braucht. 🥳
@lyse i trusted all pods yesterday and now when i pull it up they are all untrusted.
@xuu The Pod.LastSeen and Pod.LastUpdated fields are only ever updated in the Cache.DetectPodFromUserAgent(…) function as far as I can tell. This function is called in Cache.DetectClientFromRequest(…) and Cache.DetectClientFromResponse(…).
Cache.DetectClientFromRequest(…) is only invoked when the twtxt.txt is requested and looks at the User-Agent HTTP request header.
Cache.DetectClientFromResponse(…) is only called in Cache.FetchFeeds(…) and looks at the Powered-By HTTP response header. This header would be set in twtxt.txt HTTP responses from yarnd. A bunch of places invoke Cache.FetchFeeds(…), including a periodic job (UpdateFeedsJob.Run()). Maybe something is iffy around these locations.
@movq It's an old, cheap Optus without any model information on it. It was maybe 180DM or so in a discounter 25, 30 years ago. Its main job is to collect dust, can't even remember its last use. That must have been easily 15 years ago I reckon. Thus, absolutely no surprise. Maybe I'll just take it apart and see what I can see as the week progresses.
did I just break something else? 😅🤣
@lyse @prologic 😆 There was something weird going on with my #Timeline instance, the text input box was visible even though I was logged out and I was able to twt from it ... It has to do with cache because it wouldn't disappear unless I whip my website's cache from the browser.
Poke @sorenpeter and @eapl.me I have no Idea how to reproduce this.
@lyse @prologic 😆 There was something weird going on with my #Timeline instance, the text input box was visible even though I was logged out and I was able to twt from it ... It has to do with cache because it wouldn't disappear unless I whip my website's cache from the browser.
Poke @sorenpeter and @eapl.me I have no Idea how to reproduce this.
Recovery run: 3.11 miles, 00:10:52 average pace, 00:33:47 duration
#running #treadmill
Recovery run: 3.11 miles, 00:10:52 average pace, 00:33:47 duration
#running #treadmill
Recovery run: 3.11 miles, 00:10:52 average pace, 00:33:47 duration
#running #treadmill
[47°09′48″S, 126°43′38″W] Working impossible due to heavy rain
@lyse Oh no. 🥴 What kind of telescope have you got?
@lyse Oh no. 🥴 What kind of telescope have you got?
@lyse Oh no. 🥴 What kind of telescope have you got?
@lyse Oh no. 🥴 What kind of telescope have you got?
I'm rather frozen after half an hour looking at Venus and Saturn through the telescope outside. I couldn't see any rings around Saturn. Disappointing. It also appeared rather dark. The very bright Venus on the other hand told me that there is something growing inside the scope. :-( Or maybe there is dust.
[47°09′41″S, 126°43′01″W] Wind speed: 107kph -- batteries low
I'm gonna listen to Cigarettes After Sex all day if I get a GF
It's nice to see we're all largely thinking along the same lines. e.g: Salty.im 😅
It's nice to see we're all largely thinking along the same lines. e.g: Salty.im 😅
@eapl.me Yeah this is true. Previously RSA and AES were more common. These days Salsa and Chacha and Curve are fairly prevalent. For example all the Wireguard stuff uses Curve25519 / Ed25519 crypto. Signal uses very similar crypto too, but with some very nice double ratcheting 3DH.
@eapl.me Yeah this is true. Previously RSA and AES were more common. These days Salsa and Chacha and Curve are fairly prevalent. For example all the Wireguard stuff uses Curve25519 / Ed25519 crypto. Signal uses very similar crypto too, but with some very nice double ratcheting 3DH.
@eapl.me I _-think_ we've gotten use to it somewhat 🤣
@eapl.me I _-think_ we've gotten use to it somewhat 🤣
a year ago I had a struggle to find documentation about it and now it seems there are more examples, cool!
I agree 🙂, although it's easy to lose comments over time and are not so grouped by topic, it's not so easy to vote or make a survey about it...
I prefer a forum for that 😊
I made a draft of an "encrypted public messenger", which was basically a Feed for an address derivate from the public ket, let's say 'abcd..eaea'
Anyone could check, "are there any messages for my address?" and you get a whole list of timestamps and encrypted stuff.
Inside the encrypted message is a signature from the sender. That way you 'could' block spam.
Only the owner of the private key could see who sent what, and so...
And even with that my concussion was that users expectations for a private IM might be far away from my experiment.
@doesnm whilst technically true, expensive and unnecessary.
@doesnm whilst technically true, expensive and unnecessary.
Again: if you *can* decrypt - it's for you
@johanbove Easier said than done. Couldn’t believe my eyes this morning.
@johanbove Easier said than done. Couldn’t believe my eyes this morning.
@johanbove Easier said than done. Couldn’t believe my eyes this morning.
@johanbove Easier said than done. Couldn’t believe my eyes this morning.
Donc, si je comprends bien, nextcloudcmd /mon/dossier https://gnagna.tld, ça ne synchronise pas tout? Il faut avoir déjà fait un upload auparavant???
Donc, si je comprends bien, nextcloudcmd /mon/dossier https://gnagna.tld, ça ne synchronise pas tout? Il faut avoir déjà fait un upload auparavant???
[47°09′37″S, 126°43′16″W] Wind speed: 58kph
It is not possible to remove it, otherwise you do not know that the message is for you. With that information you can't decrypt.
It is not possible to remove it, otherwise you do not know that the message is for you. With that information you can't decrypt.
Can you share summary after meeting?
@prologic @lyse First, please leave me your comments on the repository! Even if it's just to give your opinion on what shouldn't be included. The more variety, the better.
Second, I'm going to try to do tests with Elliptic keys and base64. Thanks for the advice @eapl
Finally, I'd like to give my opinion. Secure direct messages are a feature that ActivityPub and Mastodon don't have, to give an example. By including it as an extension, we're already taking a significant leap forward from the competition. Does it make sense to include it in a public feed? In fact, we're already doing that. When we reply to a user, mentioning them at the beginning of the message, it's already a direct message. The message is within a thread, perhaps breaking the conversation. Direct messages would help isolate conversations between 2 users, as well as keeping a thread cleaner and maintaining privacy. I insist, it's optional, it doesn't break compatibility with any client and implementing it isn't complex. If you don't like it, you're free to not use it. If you don't have a public key, no one can send you direct messages.
@prologic @lyse First, please leave me your comments on the repository! Even if it's just to give your opinion on what shouldn't be included. The more variety, the better.
Second, I'm going to try to do tests with Elliptic keys and base64. Thanks for the advice @eapl
Finally, I'd like to give my opinion. Secure direct messages are a feature that ActivityPub and Mastodon don't have, to give an example. By including it as an extension, we're already taking a significant leap forward from the competition. Does it make sense to include it in a public feed? In fact, we're already doing that. When we reply to a user, mentioning them at the beginning of the message, it's already a direct message. The message is within a thread, perhaps breaking the conversation. Direct messages would help isolate conversations between 2 users, as well as keeping a thread cleaner and maintaining privacy. I insist, it's optional, it doesn't break compatibility with any client and implementing it isn't complex. If you don't like it, you're free to not use it. If you don't have a public key, no one can send you direct messages.
Keep breathing and stay cool.
Keep breathing and stay cool.
👋👋 Reminders that this weekend our monthly Yarn.social online meetup. Who's coming? 🤔 Some possible topics:
- Direct Messaging for Twtxt
- @prologic 's new EdgeGuard services 🤣
- What's the weather like? 👍
Details:
- When: 25th Jan 2025 at 12:00PM UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
👋👋 Reminders that this weekend our monthly Yarn.social online meetup. Who's coming? 🤔 Some possible topics:
- Direct Messaging for Twtxt
- @prologic 's new EdgeGuard services 🤣
- What's the weather like? 👍
Details:
- When: 25th Jan 2025 at 12:00PM UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
While the US politicians and tech billionaires are going full-on fascist mode, here is a reminder that there are European alternatives for many well known digital and online services: https://european-alternatives.eu
While the US politicians and tech billionaires are going full-on fascist mode, here is a reminder that there are European alternatives for many well known digital and online services: https://european-alternatives.eu
Simplifying my online presence further by removing my Known site. Goodbye social.johanbove.info - it was sometimes a little fun.
Simplifying my online presence further by removing my Known site. Goodbye social.johanbove.info - it was sometimes a little fun.
@xuu Is this because there's a bug in persisting trusted peers? 🤔
@xuu Is this because there's a bug in persisting trusted peers? 🤔
@lyse This is a good point.
@lyse This is a good point.
@doesnm That's _actually_ not true, because you'd have to know the target you're interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you _may_ know your own inbox address, etc, I (_as an arbitrary bad actor_) wouldn't easily be able to guess (_let alone brute force_) my way to another inbox address of an interested party.
@doesnm That's _actually_ not true, because you'd have to know the target you're interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you _may_ know your own inbox address, etc, I (_as an arbitrary bad actor_) wouldn't easily be able to guess (_let alone brute force_) my way to another inbox address of an interested party.
It's ok for most encrypted protocols (In salty you can fetch other messages but can't decrypt). Btw i think recipient can be removed so if someone seen message they tried to decypt, if can't - its not message to you
thinking about l-systems again, maybe a morse beacon #coding #sound #radio #halfbaked
[47°09′26″S, 126°43′41″W] Wind speed: N/A -- Cannot comunicate
[47°09′25″S, 126°43′54″W] Wind speed: 99kph -- batteries low
I remember starting that one.. it was a bit gratuitous for me to get past the first few episodes.
and yes.. these all come with satisfying endings across multiple seasons.
my goto's are the Expanse, the Magicians, XFiles, House, Umbrella Academy, Orphan Black, 12 Monkeys, the star treks (DS9 especially)
i have probably watched through them a half dozen times each. some more :D
It seems related to us poor single user pods not getting the trust to share twts.. which it seems to still untrust on restart for me.
@movq, @prologic when navigating to a Yarn. If the head twt is missing then the whole thread is not accessible. It only returns an error. so i have no way to view any of the replies within the thread other than the end twt.
@xuu Can you elaborate in textual form for the poor vision impaired developer 🤣 🙏
@xuu Can you elaborate in textual form for the poor vision impaired developer 🤣 🙏