# 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=231634
# next = https://watcher.sour.is?offset=231734
# prev = https://watcher.sour.is?offset=231534
Added support for uploading images to to #Timeline
Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.
When washing the dishes at the scouts I cut my hand open on the ladle. That piece of shit has a terrible burr.
@lyse Bur I can't think of what's changed to cause this? 🧐
@lyse Bur I can't think of what's changed to cause this? 🧐
[47°09′12″S, 126°43′50″W] Transfer 25% complete...
What exact feeds are we talking about that uses spaces instead of tabs or the T's in timestamp?
What exact feeds are we talking about that uses spaces instead of tabs or the T's in timestamp?
What exact feeds are we talking about that uses spaces instead of tabs or the T's in timestamp?
What exact feeds are we talking about that uses spaces instead of tabs or the T's in timestamp?
Non en fait, archivebox, c'est des dépendances dont je ne veux pas (chromium...)
Non en fait, archivebox, c'est des dépendances dont je ne veux pas (chromium...)
Yes, it looks like some users are not lucky to be Dildo agents here ...
On a vu The Brutalist hier soir. Je suis très surpris de ne voir aucun commentaire nulle part sur la toute fin du film, la dernière image, presque subliminale. Elle résonne pourtant si fort avec la dernière phrase du film, l'interrogatoire du début, la photo de l'entracte et bien d'autres éléments... Peut-être que je me trompe #cine #film
On a vu The Brutalist hier soir. Je suis très surpris de ne voir aucun commentaire nulle part sur la toute fin du film, la dernière image, presque subliminale. Elle résonne pourtant si fort avec la dernière phrase du film, l'interrogatoire du début, la photo de l'entracte et bien d'autres éléments... Peut-être que je me trompe #cine #film
@prologic Of course you don't notice it when yarnd only shows at most the last n messages of a feed. As an example, check out mckinley's message from 2023-01-09T22:42:37Z. It has "[Scheduled][Scheduled][Scheduled]"… in it. This text in square brackets is repeated numerous times. If you search his feed for closing square bracket followed by an opening square bracket (][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I've explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.
@prologic Of course you don't notice it when yarnd only shows at most the last n messages of a feed. As an example, check out mckinley's message from 2023-01-09T22:42:37Z. It has "\n\n\n"… in it. This text in square brackets is repeated numerous times. If you search his feed for closing square bracket followed by an opening square bracket (][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I've explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.
[47°09′06″S, 126°43′05″W] Bad satellite signal -- switching to analog communication
is the whole chat about dildos? D:
[47°09′11″S, 126°43′19″W] Raw reading: 0x67B02D61, offset +/-5
Does Dildo browser support the DICT protocol?
@lyse Duplicates again where two days ago? I don't see this anywhere (_unless I'm blind!_)
@lyse Duplicates again where two days ago? I don't see this anywhere (_unless I'm blind!_)
@lyse Agree. I'm not sure we should lax the timestamp format at all IMO. What @xuu has found is kind of nuts haha 😆 However I do think we should relax the \\t separator between <timestamp> and <content>. Let users use _any_ valid whitespace here that isn't a newline or carriage return.
@lyse Agree. I'm not sure we should lax the timestamp format at all IMO. What @xuu has found is kind of nuts haha 😆 However I do think we should relax the \t separator between <timestamp> and <content>. Let users use _any_ valid whitespace here that isn't a newline or carriage return.
@lyse Agree. I'm not sure we should lax the timestamp format at all IMO. What @xuu has found is kind of nuts haha 😆 However I do think we should relax the \t separator between <timestamp> and <content>. Let users use _any_ valid whitespace here that isn't a newline or carriage return.
I _think_ the author is a bit out of their depth here. A linear feed isn't quite what the author seems to be modelling in their view of the problems they observe and describe. A linear feed has a beginning and an end. You can (_ideally client-side_) sort it by Date, or by Subject like we do with our Twtxt clients. A Tree-structure isn't what the author thinks either, this is more the structure that forms after you introducing some kind of "threading model". The main problem with any kind of information system that tries to figure out algorithmically what you want to "see" is that type of interface has no start and no end. SO you end up with a "scroll of doom".
I _think_ the author is a bit out of their depth here. A linear feed isn't quite what the author seems to be modelling in their view of the problems they observe and describe. A linear feed has a beginning and an end. You can (_ideally client-side_) sort it by Date, or by Subject like we do with our Twtxt clients. A Tree-structure isn't what the author thinks either, this is more the structure that forms after you introducing some kind of "threading model". The main problem with any kind of information system that tries to figure out algorithmically what you want to "see" is that type of interface has no start and no end. SO you end up with a "scroll of doom".
it's ok, you can confess to us, we don't know your identity!
🧮 USERS:1 FEEDS:2 TWTS:1248 ARCHIVED:84769 CACHE:2799 FOLLOWERS:18 FOLLOWING:14
The article discusses the challenges posed by linear social media feeds, which often lead to disengagement and difficulty in prioritizing content from friends due to constant scrolling. The author proposes an alternative approach using a daily feed structure per day, which organizes posts by date, allowing for easier prioritization and reducing mindless scrolling.
Key Points:
1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends' content. This can lead to addiction and disengagement.
2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.
3. Mastodon Experience: The author's experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
4. Challenges and Considerations:
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
- Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
- Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.
6. Future Directions: The author hopes for improvements in alternative platforms' feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.
In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed
The article discusses the challenges posed by linear social media feeds, which often lead to disengagement and difficulty in prioritizing content from friends due to constant scrolling. The author proposes an alternative approach using a daily feed structure per day, which organizes posts by date, allowing for easier prioritization and reducing mindless scrolling.
Key Points:
1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends' content. This can lead to addiction and disengagement.
2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.
3. Mastodon Experience: The author's experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
4. Challenges and Considerations:
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
- Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
- Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.
6. Future Directions: The author hopes for improvements in alternative platforms' feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.
In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed
What exactly is a linear feed? 🤔
What exactly is a linear feed? 🤔
This year for #ilovefs I also want to thank @lenovous@lenovous for selling Laptops with GNU/Linux in Portugal!
This year for #ilovefs I also want to thank @lenovous@lenovous for selling Laptops with GNU/Linux in Portugal!
@eapl.me I like this idea. Another option would be to show a limited number of posts, with an option to see the omitted ones by user. Either way, I wonder how well that works with threading.
[47°09′30″S, 126°43′40″W] --interrupted--
@andros … I hope they pay you enough for this horrible task. 😂
@andros … I hope they pay you enough for this horrible task. 😂
@andros … I hope they pay you enough for this horrible task. 😂
@andros … I hope they pay you enough for this horrible task. 😂
@movq Ja, völlig behämmert. Schade, vertane Chance für einen „Doch“-Knopf.
@lyse Ja, nein, abbrechen? Wie, was? Was machen Sachen? 😂
@lyse Ja, nein, abbrechen? Wie, was? Was machen Sachen? 😂
@lyse Ja, nein, abbrechen? Wie, was? Was machen Sachen? 😂
@lyse Ja, nein, abbrechen? Wie, was? Was machen Sachen? 😂
Je recherche un outil qui me permettrait d'obtenir des snapshots de page web, un peu comme le fait archive.org. J'ai le sentiment et l'envie d'archiver pour la postérité, avant la disparition inopinée de ressources de valeur. Vous auriez des conseils? script avec #curl? Truc en #auto-hébergement?
Je recherche un outil qui me permettrait d'obtenir des snapshots de page web, un peu comme le fait archive.org. J'ai le sentiment et l'envie d'archiver pour la postérité, avant la disparition inopinée de ressources de valeur. Vous auriez des conseils? script avec #curl? Truc en #auto-hébergement?
Boah, jetzt mal ernsthaft, was ist denn das für ein Dialog bittesehr!?
Wer hat sich zu dieser Meldung diese Knopfauswahl überlegt und dann auch noch die Icons dazu ausgedacht? Und warum hat's das Zertifikat überhaupt schon wieder zerlegt? Und wieso kommt der Dialog direkt wieder in ner Endlosschleife hoch, wenn ich abbreche? Komplettversagen nach Strich und Faden an allen Enden. Allen. Grrr, so viel Hass! Ich schalt besser die Büchse aus.
@prologic Tolerant yes, but in the right places. This is just encouraging people to not properly care. The extreme end is HTML where parsers basically accept any input. I'm not a fan of that. Whatever.
@prologic The issue is that all bracketed text in the entire feed has been duplicated again two days ago. The bug is not fixed. Or it's a new one.
Now I just have to remember to tag people in replays ✍
... And, HOLLY!! infinite scrolling is real!! 👀
@movq I can relate to that. :-/
[47°09′29″S, 126°43′23″W] Dosimeter fixed
I just did and things are working wonderfully well now and I'm in love with how profile views are layed out! 👌 Thank you!
ok, sounds like a 'large' project to me.
Is it more an API (more oriented to developers), more oriented to UI/UX/Frontend? Perhaps both?
I'd go with prologic's advice of measuring and prioritizing. Perhaps you have a budget or at least something like "let's see how far can we reach in 6 months", and possibly you won't finish in the time you have (just guessing).
Something that has helped me was defining "Why do you we want to refactor this project?".
Could it be to make it compile on newer versions, or making it easier to grow and scale, or perhaps they are trying to sell that product to another company. Every reason has a different path, IMO.
Ouiiii, je suis liiiibre, mes corrections sont terminées! 😌
Ouiiii, je suis liiiibre, mes corrections sont terminées! 😌
Mes élèves n'imaginent pas l'impact positif de SOAD dans mes oreilles lorsque je corrige...
Mes élèves n'imaginent pas l'impact positif de SOAD dans mes oreilles lorsque je corrige...
I've learned that I can live without @kde@kde but I'm not able to live without #konsole, so... my first ❤️ of this year's #ilovefs goes to the lovely Konsole and specially The Konsole Developers!
https://konsole.kde.org/ 
A screenshot of Konsole where `figlet -c \#ILOVEFS` has been executed, and so it shows that hashtag in an ASCII drawing.
I've learned that I can live without @kde@kde but I'm not able to live without #konsole, so... my first ❤️ of this year's #ilovefs goes to the lovely Konsole and specially The Konsole Developers!
https://konsole.kde.org/ A screenshot of Konsole where `figlet -c \#ILOVEFS` has been executed, and so it shows that hashtag in an ASCII drawing.
@andros My first point of advice is to stop everything and measure all the important critical user journeys. Design and Build Service Level Objectives for each and every part of the system you can find that _any_ user cares about.
@andros My first point of advice is to stop everything and measure all the important critical user journeys. Design and Build Service Level Objectives for each and every part of the system you can find that _any_ user cares about.
[47°09′54″S, 126°43′34″W] Resetting dosimeter
2024-08-04T11:24:34Z was the last occurrence of this.
2024-08-04T11:24:34Z was the last occurrence of this.
@bender @lyse This bug was fixed back in September last year. But the brackets still appear in my current feed. is that what the issue is? 🤔
@bender @lyse This bug was fixed back in September last year. But the brackets still appear in my current feed. is that what the issue is? 🤔
@lyse @andros Are we talking about yarnd here? Hmm? 🤔 I've _thought_ about a "read flag" but I just haven't bothered so far...
@lyse @andros Are we talking about yarnd here? Hmm? 🤔 I've _thought_ about a "read flag" but I just haven't bothered so far...