# 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 196325
# self = https://watcher.sour.is?offset=143125
# next = https://watcher.sour.is?offset=143225
# prev = https://watcher.sour.is?offset=143025
Yeah it's something on my radar of things to do one day.
One of my use cases is to tag our growing photo library.
Yeah it's something on my radar of things to do one day.
One of my use cases is to tag our growing photo library.
Yeah it's something on my radar of things to do one day.
One of my use cases is to tag our growing photo library.
@lyse Id I had to guess, the fees is old and contains no new Twts and so never get an entry in the cache so therefore no Last Modified header to send.
@lyse Id I had to guess, the fees is old and contains no new Twts and so never get an entry in the cache so therefore no Last Modified header to send.
@lyse Id I had to guess, the fees is old and contains no new Twts and so never get an entry in the cache so therefore no Last Modified header to send.
@lyse Bahahahahaha 😆🤣 I guess I'll to figure something out
@lyse Bahahahahaha 😆🤣 I guess I'll to figure something out
@lyse Bahahahahaha 😆🤣 I guess I'll to figure something out
@lyse Same! 😆 And it works quite well 😉
@lyse Same! 😆 And it works quite well 😉
@lyse Same! 😆 And it works quite well 😉
Some good points guys 👌 Thanks! 🙇♂️
Some good points guys 👌 Thanks! 🙇♂️
Some good points guys 👌 Thanks! 🙇♂️
Gah apparently I've gone and finally caught the wretched COVID virus 😢
Gah apparently I've gone and finally caught the wretched COVID virus 😢
Gah apparently I've gone and finally caught the wretched COVID virus 😢
🧮 USERS:1 FEEDS:2 TWTS:574 ARCHIVED:63652 CACHE:2218 FOLLOWERS:13 FOLLOWING:14
@prologic I’m very ambivalent on this. At the same time, I’m exhausted from work and life in general. 😅 I can’t form coherent thoughts at the moment. Maybe tomorrow. Or at the weekend.
@prologic I’m very ambivalent on this. At the same time, I’m exhausted from work and life in general. 😅 I can’t form coherent thoughts at the moment. Maybe tomorrow. Or at the weekend.
@prologic I’m very ambivalent on this. At the same time, I’m exhausted from work and life in general. 😅 I can’t form coherent thoughts at the moment. Maybe tomorrow. Or at the weekend.
@xuu @prologic Yarn.social without threading (as it would be the case in a “truncated” feed) does not make sense to me.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.
@xuu @prologic Yarn.social without threading (as it would be the case in a “truncated” feed) does not make sense to me.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.
@xuu @prologic Yarn.social without threading (as it would be the case in a “truncated” feed) does not make sense to me.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.
@prologic It did not crash today (after it did earlier today), I now compiled and updated to latest, I'll let you know if it happens again.
[47°09′32″S, 126°43′34″W] Reading: 1.66000 PPM
@xuu @prologic I will never give up threading! It's a very vital civil achievement.
@prologic I only suggested to change the info page, not the user agent. ;-)
Stop Goodharting yourself! Stop Goodharting yourself!
Stop Goodharting yourself! Stop Goodharting yourself!
@prologic Ah, I see! But why are there no caching request headers sent along (judging by HTTP 200 instead of 304)?
[47°09′21″S, 126°43′50″W] Dosimeter fixed
@prologic I agree with @abucci, @darch and @marado. Also, in order to set a good example, we would have to rename our feed filenames which would break threading.
I am against the original idea of forking twtxt.txt into yarn.txt unless I see any technical reason or feature that would justify breaking compatibility - so far I don't see one. But I agree in principle with @darch that maybe we can add something on the metadata of the feeds enumerating the extensions we use or... I don't know, something that will allow any twtxt user to know how to deal with any 'yarnisms' in the content of our twts (even if the only one that comes to my mind as needing explanation is the thread hashes - how to interpret them).
@prologic yeah. I'd add "Big Data" to that hype list, and I'm sure there are a bunch more that I'm forgetting.
On the topic of a GPU cluster, the optimal design is going to depend a lot on what workloads you intend to run on it. The weakest link in these things is the data transfer rate, but that won't matter too much for compute-heavy workloads. If your workloads are going to involve a lot of data, though, you'd be better off with a smaller number of high-VRAM cards than with a larger number of interconnected cards. I guess that's hardware engineering 101 stuff, but still...
@abucci Hmmm 🤔 I'll sleep on it, but good counterpoint 👌
@abucci Hmmm 🤔 I'll sleep on it, but good counterpoint 👌
@abucci Hmmm 🤔 I'll sleep on it, but good counterpoint 👌
@prologic I would politely suggest again that we not react to people with bad attitudes who talk shit about yarn. If twt is forked, it should be forked to add features that are otherwise not possible. Not to appease people who will probably never be appeased.
👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).
👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).
👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).
I generally don't buy into hype myself anyway, didn't buy into the "Cloud" hype, nor the "Cryptocurrency" hype, and I'm sure as hell not buying into the so-called "AI" hype. Wake me up when I can run this shit™ on my own GPU-powered machines 🤣 -- As a vision impaired person, the only use-case I've found that's remotely useful for me is to summarize text. Problem though? I'm not going to use OpenAI's service to do this. Why? Privacy! Fuck me, do you really think I'm just going to dump shit™ into your API endpoints?! (or Web App).
One of these days I'd like to build a small GPU cluster, but I haven't decided how yet. Cluster or RPI(s) or a more expensive cluster of 1RU pizza boxes with NVIDIA Tesla cards, or a 1RU 4-node NVIDIA AGX Jetson cluster?
I generally don't buy into hype myself anyway, didn't buy into the "Cloud" hype, nor the "Cryptocurrency" hype, and I'm sure as hell not buying into the so-called "AI" hype. Wake me up when I can run this shit™ on my own GPU-powered machines 🤣 -- As a vision impaired person, the only use-case I've found that's remotely useful for me is to summarize text. Problem though? I'm not going to use OpenAI's service to do this. Why? Privacy! Fuck me, do you really think I'm just going to dump shit™ into your API endpoints?! (or Web App).
One of these days I'd like to build a small GPU cluster, but I haven't decided how yet. Cluster or RPI(s) or a more expensive cluster of 1RU pizza boxes with NVIDIA Tesla cards, or a 1RU 4-node NVIDIA AGX Jetson cluster?
I generally don't buy into hype myself anyway, didn't buy into the "Cloud" hype, nor the "Cryptocurrency" hype, and I'm sure as hell not buying into the so-called "AI" hype. Wake me up when I can run this shit™ on my own GPU-powered machines 🤣 -- As a vision impaired person, the only use-case I've found that's remotely useful for me is to summarize text. Problem though? I'm not going to use OpenAI's service to do this. Why? Privacy! Fuck me, do you really think I'm just going to dump shit™ into your API endpoints?! (or Web App).
One of these days I'd like to build a small GPU cluster, but I haven't decided how yet. Cluster or RPI(s) or a more expensive cluster of 1RU pizza boxes with NVIDIA Tesla cards, or a 1RU 4-node NVIDIA AGX Jetson cluster?
@xuu That's hilarious that you mention content-negotiation as yarnd does this, and has done for quite some time, though I suspect it achieves nothing 🤣 (it does for AP, Twtxt, etc, though...) -- The original spec didn't even mention content-types or any of the sort, so I very much doubt any older clients (just twtxt the ref client?) even attempts to do this? 🤔
@xuu That's hilarious that you mention content-negotiation as yarnd does this, and has done for quite some time, though I suspect it achieves nothing 🤣 (it does for AP, Twtxt, etc, though...) -- The original spec didn't even mention content-types or any of the sort, so I very much doubt any older clients (just twtxt the ref client?) even attempts to do this? 🤔
@xuu That's hilarious that you mention content-negotiation as yarnd does this, and has done for quite some time, though I suspect it achieves nothing 🤣 (it does for AP, Twtxt, etc, though...) -- The original spec didn't even mention content-types or any of the sort, so I very much doubt any older clients (just twtxt the ref client?) even attempts to do this? 🤔
On LinkedIn I see a lot of posts aimed at software developers along the lines of "If you're not using these AI tools (X,Y,Z) you're going to be left behind."
Two things about that:
1. No you're not. If you have good soft skills (good communication, show up on time, general time management) then you're already in excellent shape. No AI can do that stuff, and for that alone no AI can replace people
2. This rhetoric is coming directly from the billionaires who are laying off tech people by the 100s of thousands as part of the class war they've been conducting against all working people since the 1940s. They want you to believe that you have to scramble and claw over one another to learn the "AI" that they're forcing onto the world, so that you stop honing the skills that matter (see #1) and are easier to obsolete later. Don't fall for it. It's far from clear how this will shake out once governments get off their asses and start regulating this stuff, by the way--most of these "AI" tools are blatantly breaking copyright and other IP laws, and some day that'll catch up with them.
That said, it is helpful to know thy enemy.
On LinkedIn I see a lot of posts aimed at software developers along the lines of "If you're not using these AI tools (X,Y,Z) you're going to be left behind."
Two things about that:
1. No you're not. If you have good soft skills (good communication, show up on time, general time management) then you're already in excellent shape
2. This rhetoric is coming directly from the billionaires who are laying off tech people by the 100s of thousands as part of the class war they've been conducting against all working people since the 1940s. They want you to believe that you have to scramble and claw over one another to learn the "AI" that they're forcing onto the world, so that you stop honing the skills that matter (see #1) and are easier to obsolete later. Don't fall for it.
That said, it is helpful to know thy enemy.
On LinkedIn I see a lot of posts aimed at software developers along the lines of "If you're not using these AI tools (X,Y,Z) you're going to be left behind."
Two things about that:
1. No you're not. If you have good soft skills (good communication, show up on time, general time management) then you're already in excellent shape. No AI can do that stuff, and for that alone no AI can replace people
2. This rhetoric is coming directly from the billionaires who are laying off tech people by the 100s of thousands as part of the class war they've been conducting against all working people since the 1940s. They want you to believe that you have to scramble and claw over one another to learn the "AI" that they're forcing onto the world, so that you stop honing the skills that matter (see #1) and are easier to obsolete later. Don't fall for it.
That said, it is helpful to know thy enemy.
We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way... We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.
We could ask them? But on the counter would bukket or jan6 follow the pure twtxt feeds? Probably not either way... We could use content negotiation as well. text/plain for basic and text/yarn for enhanced.
[47°09′29″S, 126°43′26″W] Resetting dosimeter
@prologic I will try and get that tonight. (Currently at work).
[47°09′02″S, 126°43′05″W] Dosimeter overflow
Getting a very frequent crash in yarn. Have to restart it several times a day now. Ill pull down and compile latest later today and see if that helps.
[47°09′16″S, 126°43′00″W] Dosimeter malfunction
@funbreaker The original spec was very lax on specifics and details. I guess it was never intended to be used as a decentralized social media ecosystem 😆 Which has been made quite clear by the few that are strongly outspoken and don't want this. 🤦♂️ and/or unsupportive of any other uses (despite the open spec and "fork me" badge 🤣)
@funbreaker The original spec was very lax on specifics and details. I guess it was never intended to be used as a decentralized social media ecosystem 😆 Which has been made quite clear by the few that are strongly outspoken and don't want this. 🤦♂️ and/or unsupportive of any other uses (despite the open spec and "fork me" badge 🤣)
@funbreaker The original spec was very lax on specifics and details. I guess it was never intended to be used as a decentralized social media ecosystem 😆 Which has been made quite clear by the few that are strongly outspoken and don't want this. 🤦♂️ and/or unsupportive of any other uses (despite the open spec and "fork me" badge 🤣)
@shreyan I am actually seriously considering forking the spec and putting this to the community.
One of the motivating reasons to do this (besides to avoid the continued hostility) is we don't share the same goals or visions.
Decentralized microBlogging is for all (not just retro enthusiasts and hackers)
@shreyan I am actually seriously considering forking the spec and putting this to the community.
One of the motivating reasons to do this (besides to avoid the continued hostility) is we don't share the same goals or visions.
Decentralized microBlogging is for all (not just retro enthusiasts and hackers)
@shreyan I am actually seriously considering forking the spec and putting this to the community.
One of the motivating reasons to do this (besides to avoid the continued hostility) is we don't share the same goals or visions.
Decentralized microBlogging is for all (not just retro enthusiasts and hackers)
@shreyan It honestly means nothing. It's like 12-factor apps 😆
@shreyan It honestly means nothing. It's like 12-factor apps 😆
@shreyan It honestly means nothing. It's like 12-factor apps 😆
🧮 USERS:1 FEEDS:2 TWTS:573 ARCHIVED:63631 CACHE:2212 FOLLOWERS:13 FOLLOWING:14