# 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 194394
# self = https://watcher.sour.is?offset=194394
# prev = https://watcher.sour.is?offset=194294
we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases....my friend's feed with like four posts parsed correctly so i tried this account's feed and well now im not going to bed on time
we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases....my friend's feed with like four posts parsed correctly so i tried this account's feed and well now im not going to bed on time
@bender ty for attempting to test, though, it means a lot! lmk if u find any more silly things i need to clarify or fix :> be prepared for everything breaking during beta :p
@bender i also recently discovered there was a bug causing new users to initialize wrong leading to their posts not being saved :p ..and made breaking changes to how the config and database files are stored so um, make sure to clear your local tree before updating!
@bender as the host (eg twtxt.net) determines the canonical url of the instance in generated feed url metadata as well as every hash of every post made on the instance internally, i added this error message to make sure people don't accidentally set up their instance on localhost :p for testing i set it to localhost:31212 and protocols to ["http"], it's a recent addition that could definitely do with documenting in the getting started section
@lyse retwts are a discovery feature! on federated platforms with no algorithm where you only ever see posts from accounts you explicitly follow, the element of "hey look at this!" helps users to find other accounts they might like organically
i agree quoting and replying forum-style is generally a much better way of doing things even though im a heathen and i revel in the dark patterns inspired by quote posts but when you have nothing to add and you just want to share a twt with your followers it'd be good to have a standardized way of linking to twt
@bender@kat after implementing cws in bbycll (parsing them the way i described in op) i understand why <details> aren't rendered. firstly they're not actually markdown, and secondly they style weird — details are forced onto a new line as a block element but you can't make the <summary> inline because it is inside <details>, and making <details> inline will also indent everything inside it
@kat I reckon the original <details> need to have the open attribute set in order to expand it, so I cannot just define some custom CSS rules to do that in my browser.
But in regards to twtxt, my client won't hide anything in that realm anyway. :-) It's just more noise.
On m'a fait remarquer que mon serveur n'était pas accessible en ipv6... Merci! Je ne m'en apercevais pas depuis chez moi. Encore une histoire du firewall obscur de mon routeur :/. Là, normalement, c'est bon. ???
On m'a fait remarquer que mon serveur n'était pas accessible en ipv6... Merci! Je ne m'en apercevais pas depuis chez moi. Encore une histoire du firewall obscur de mon routeur :/. Là, normalement, c'est bon. ???
@dce Nope. 😃 What’s that genre called? Sounds like old horror movies from the 70'ies (or it could be a soundtrack to Salad Fingers, if anyone remembers that).
@kat Ta. The only good use for <details> is to collapse long logs in bug analysis reports. Other than that, I find it rather annoying to expand sections manually.
As for spoilers, personally, I don't care at all. Not the slightest bit. If there is something that I don't wanna read, I just stop reading. ¯\_(ツ)_/¯
But I've got the feeling that I've got an unpopular opinion on that matter. ;-)_
@bender I see, thanks. Well, I never found these warnings useful. To hide answers to conundrums or the like, ROT13ing or base64-encoding them is plenty sufficient.
Hahaha, I never heard of Poopgate before. :-D Poor passengers.
@lyse a content warning is kind of like a forum spoiler cut, or like the
<details>
tag in HTML; it lets you write a sentence or so that someone can then click to expand to see the actual post. it's called a CW because most people use it to warn for potentially triggering/harmful subjects, but you can really use it for anything, like spoilers in a TV show or even for joke punchlines
@zvava I never used any of the social media platforms, that's why I'm probably ignorant.
I don't understand the concept of a retwt. Just quote the (relevant) parts from whereever and comment on that. Or post a link instead of a quote. Sounds simple enough. :-) That's also has the benefit that it works with every source, no matter what. Since it's called retwt, I'd imagine this to only work (well) with whatever messages the system itself offers. But I could be wrong. What would be the benefit of having a dedicated message type or structure for "hey, look at that" messages in your opinion?
@kat Ten stories or more are already very tall in my books. Not sure at which height I would start calling high rise buildings sky scrapers, but Wikipedia suggests around 150 meters, depending on region.
in the same vein, i think content warnings can be faithfully implemented by parsing CW: ..., tw // ..., etc. from the first line of a post followed by two newlines, like how they're used on platforms that don't have content warnings
at first i dismissed the idea of likes on twtxt as not sensible...like at all — then i considered they could just be published in a metadata field (though that field could get really unruly after a while)
retwts are plausible, as "RE: https://example.com/twtxt.txt#abcdefg", the hash could even be the original timestamp from the feed to make it human readable/writable, though im extremely wary of clogging up timelines
i _thought_ quote twts could be done extremely sensibly, by interpreting a mention+hash at the end of the twt differently to when placed at the beginning — but the twt subject extension requires it be at the beginning, so the clean fallback to a normal reply i originally imagined is out of the question — it could still be possible (reusing the retwt format, just like twitter!) but i'm not convinced it's worth it at that point
is any of this in the spirit of twtxt? no, not in the slightest, lmao
@lyse hahaha very rarely!!! it wasn't quite a sky scraper, just a few floors up, but my perspective may be skewed because i'm used to high buildings :P
@lyse hahaha very rarely!!! it wasn't quite a sky scraper, just a few floors up, but my perspective may be skewed because i'm used to high buildings :P
I have a feeling that learning to play electric double bass *through an amplifier* was a big mistake.
At the core, this is an acoustic instrument. If you play it through an amp, you will instinctively only do the bare minimum to get *some* sound going, because the amp does the heavy lifting. But it’s just not right.
This is a very physical instrument. It needs a lot of force and strength – in comparison, an electric bass guitar is almost flimsy and delicate. I need to “feel” what’s going on and that’s just not the case when using headphones.
I feel like I wasted ~3 years. 🫤 But maybe it’ll get better from now on …~
This is just one instrument: Electric bass guitar + EBow. And echo/delay on top. But it’s a single track, single take. It amazes me quite a bit how much you can do with that little thing. 🤯
Observador a fazer debates autárquicos, a convidar CH mas não BE ou Livre (vem, convidaram-nos em Almada, mas só aí... devia ser porque estavam a contar com eles para fazer oposição ao PS)... acho que sim, faz todo o sentido, não vale a pena esconder ao que vão.
search page, bookmarks page, improved thread view (that i will probably improve further), as well as a logo and a whole ui redesign. it is truly all coming together...were i to mark any items off the roadmap :p
Bush fire
A mushroom, spontaneously grown. I bet that if I tried to grow them I wouldn't manage to get even one...
captura de tela do vídeo com o exemplo de partial com um placeholder