# 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 196298
# self = https://watcher.sour.is?offset=169958
# next = https://watcher.sour.is?offset=170058
# prev = https://watcher.sour.is?offset=169858
prologic
twtxt.net
View Thread
@falsifian Yes;

> I don’t think twtxt hashes are long enough to prevent spoofing.

The current spec needs to be updated to expand the hash length to 11 characters to avoid hash collisions (_which will happen at some point with 7, if not already_).

The issue isn't dealing with "spoofing", it's about solving how clients in a decentralised model agree on the threading model and identity of a thread. Message ID(s) suffer from the fact that as @movq points out, clients have to "obey" this unwritten rule, but they're otherwise just arbitrary. Whereas Twt Hashes (_I didn't come up with the idea originally, some smart fellow in cryptography did_) are content addressable, meaning that clients don't have to agree on anything, they can trust that the hash is a cryptographic representing of the thread they're replying to, no matter what.
prologic
twtxt.net
View Thread
@falsifian I like this idea actually for edits.
prologic
twtxt.net
View Thread
@falsifian I like this idea actually for edits.
falsifian
www.falsifian.org
View Thread
@movq @prologic Another option would be: when you edit a twt, prefix the new one with (#\n) and some indication that it's an edited version of the original tweet with that hash. E.g. if the hash used to be abcd123, the new version should start "(#abcd123) (redit)".

What I like about this is that clients that don't know this convention will still stick it in the same thread. And I feel it's in the spirit of the old pre-hash (subject) convention, though that's before my time.

I guess it may not work when the edited twt itself is a reply, and there are replies to it. Maybe that could be solved by letting twts have more than one (subject) prefix.

> But the great thing about the current system is that nobody can spoof message IDs.

I don't think twtxt hashes are long enough to prevent spoofing.
falsifian
www.falsifian.org
View Thread
@movq @prologic Another option would be: when you edit a twt, prefix the new one with (#[old hash]) and some indication that it's an edited version of the original tweet with that hash. E.g. if the hash used to be abcd123, the new version should start "(#abcd123) (redit)".

What I like about this is that clients that don't know this convention will still stick it in the same thread. And I feel it's in the spirit of the old pre-hash (subject) convention, though that's before my time.

I guess it may not work when the edited twt itself is a reply, and there are replies to it. Maybe that could be solved by letting twts have more than one (subject) prefix.

> But the great thing about the current system is that nobody can spoof message IDs.

I don't think twtxt hashes are long enough to prevent spoofing.
prologic
twtxt.net
View Thread
@movq Care to share your thoughts here?

> I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.
prologic
twtxt.net
View Thread
@movq Care to share your thoughts here?

> I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.
@jo
comam.es
View Thread
[47°09′16″S, 126°43′09″W] --white noise--
@jo
comam.es
View Thread
[47°09′20″S, 126°43′46″W] Dosimeter fixed
baldo
baldo.cat
View Thread
- Si estiro de ahí… ¿caerá comida?-
#catsoftwtxt
baldo
baldo.cat
View Thread
- Si estiro de ahí… ¿caerá comida?-
/https://baldo.cat/media/photos/IMG_1894.jpeg) #catsoftwtxt
baldo
baldo.cat
View Thread
- Si estiro de ahí… ¿caerá comida?-
#catsoftwtxt
movq
www.uninformativ.de
View Thread
@prologic @lyse Yeah, same. They say:

> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.

You already can ask your most passionate followers to support you: You can ask for donations.

I regularly donate to people if their content is great and if they actually ask for donations (many just don’t). The platforms for that already exist, I think. 🤔

I’m not interested in the slightest in stuff that has a paywall. “Subscribe for more content!” No, why, go away. Pages that do this immediately feel shady and not trust-worthy. 🤔
movq
www.uninformativ.de
View Thread
@prologic @lyse Yeah, same. They say:

> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.

You already can ask your most passionate followers to support you: You can ask for donations.

I regularly donate to people if their content is great and if they actually ask for donations (many just don’t). The platforms for that already exist, I think. 🤔

I’m not interested in the slightest in stuff that has a paywall. “Subscribe for more content!” No, why, go away. Pages that do this immediately feel shady and not trust-worthy. 🤔
movq
www.uninformativ.de
View Thread
@prologic @lyse Yeah, same. They say:

> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.

You already can ask your most passionate followers to support you: You can ask for donations.

I regularly donate to people if their content is great and if they actually ask for donations (many just don’t). The platforms for that already exist, I think. 🤔

I’m not interested in the slightest in stuff that has a paywall. “Subscribe for more content!” No, why, go away. Pages that do this immediately feel shady and not trust-worthy. 🤔
movq
www.uninformativ.de
View Thread
@prologic @lyse Yeah, same. They say:

> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.

You already can ask your most passionate followers to support you: You can ask for donations.

I regularly donate to people if their content is great and if they actually ask for donations (many just don’t). The platforms for that already exist, I think. 🤔

I’m not interested in the slightest in stuff that has a paywall. “Subscribe for more content!” No, why, go away. Pages that do this immediately feel shady and not trust-worthy. 🤔
prologic
twtxt.net
View Thread
Agreed
prologic
twtxt.net
View Thread
Agreed
lyse
lyse.isobeef.org
View Thread
But I forgot to update the mentions. Oh well. I don't bother breaking hashes once more, so I just leave it at that. :-)
lyse
lyse.isobeef.org
View Thread
@prologic I simply have absolutely no interest in selling my thoughts to others. I don't like things behind paywalls. Each to their own, but I'm not gonna contribute to that.
movq
www.uninformativ.de
View Thread
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
movq
www.uninformativ.de
View Thread
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
movq
www.uninformativ.de
View Thread
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
movq
www.uninformativ.de
View Thread
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
movq
www.uninformativ.de
View Thread
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴

> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*

Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.

What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.

So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.

(Oh god. Are we re-inventing Usenet then? Again? 😂)
movq
www.uninformativ.de
View Thread
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴

> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*

Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.

What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.

So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.

(Oh god. Are we re-inventing Usenet then? Again? 😂)
movq
www.uninformativ.de
View Thread
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴

> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*

Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.

What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.

So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.

(Oh god. Are we re-inventing Usenet then? Again? 😂)
movq
www.uninformativ.de
View Thread
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴

> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*

Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.

What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.

So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.

(Oh god. Are we re-inventing Usenet then? Again? 😂)
baldo
baldo.cat
View Thread
-¿Vienes mucho por este cojín?-
/https://baldo.cat/media/photos/IMG_1886.jpeg) #catsoftwtxt
baldo
baldo.cat
View Thread
-¿Vienes mucho por este cojín?-
#catsoftwtxt
baldo
baldo.cat
View Thread
-¿Vienes mucho por este cojín?-
#catsoftwtxt
baldo
baldo.cat
View Thread
-¡Fuera intruso! O te las verás con mis puños 👊 -
#catsoftwtxt
baldo
baldo.cat
View Thread
-¡Fuera intruso! O te las verás con mis puños 👊 -
#catsoftwtxt
baldo
baldo.cat
View Thread
-¡Fuera intruso! O te las verás con mis puños 👊 -
/https://baldo.cat/media/photos/IMG_1890.jpeg) #catsoftwtxt
lyse
lyse.isobeef.org
View Thread
@prologic https://lyse.isobeef.org/tmp/hashes.png Yep, broken hashes. I just fixed them after refollowing on the new URL (my client doesn't know metadata fields).
lyse
lyse.isobeef.org
View Thread
@prologic Yes, that's when I noticed. Luckily, I had another knive in my bagpack. But I cannot find the folding one at home either. Damn. I already lost my other knive at the flea market in May this year, now the next one. This sucks.
prologic
twtxt.net
View Thread
@bender A Fred changed its url metadata field 🤣
prologic
twtxt.net
View Thread
@bender A Fred changed its url metadata field 🤣
bender
twtxt.net
View Thread
@prologic “I’m now 100% certain this is what happened”, what exactly happened?
jcolag
john.colagioia.net
View Thread
On my blog: Free Culture Book Club — Aumyr, part 1 https://john.colagioia.net/blog/2024/09/07/aumyr-1.html #freeculture #bookclub
prologic
twtxt.net
View Thread
After unfollowing and refollowing on the new feed URL, I'm now 100% certain this is what happened for @cuaxolotl 🤣 The _real_ problem is really this:

> How do we identify a feed?

It cannot be the URL, because the author _could_ change where they serve it from. This was as "good" as we could get it, but time and time again this has proven to be problematic for, well, a few folks that change their mind, which frankly should be allowed 😅
prologic
twtxt.net
View Thread
After unfollowing and refollowing on the new feed URL, I'm now 100% certain this is what happened for @cuaxolotl 🤣 The _real_ problem is really this:

> How do we identify a feed?

It cannot be the URL, because the author _could_ change where they serve it from. This was as "good" as we could get it, but time and time again this has proven to be problematic for, well, a few folks that change their mind, which frankly should be allowed 😅
prologic
twtxt.net
View Thread
For supporting edits, I was thinking more along the lines of: If a client edits a Twt already published, it _should_ put the hash of the previous Twt. Something like:


2024-09-05T13:37:40Z   (edit:mp6ox4a) Hello world!
prologic
twtxt.net
View Thread
For supporting edits, I was thinking more along the lines of: If a client edits a Twt already published, it _should_ put the hash of the previous Twt. Something like:


2024-09-05T13:37:40Z   (edit:mp6ox4a) Hello world!
prologic
twtxt.net
View Thread
For supporting edits, I was thinking more along the lines of: If a client edits a Twt already published, it _should_ put the hash of the previous Twt. Something like:


2024-09-05T13:37:40+00:00   (edit:mp6ox4a) Hello world!
prologic
twtxt.net
View Thread
For supporting edits, I was thinking more along the lines of: If a client edits a Twt already published, it _should_ put the hash of the previous Twt. Something like:


2024-09-05T13:37:40+00:00   (edit:mp6ox4a) Hello world!
prologic
twtxt.net
View Thread
To be honest, I don't really see "editing" as a problem. I see that as a natural behavior of "forking" in the first place, that just forms a. new sub-tree. What's _really_ problematic here is when a feed author changes the "identity" of their feed and changes the # url = metadata field, which is what I _believe_ @cuaxolotl has just done, though I'm not 100% certain, I'm like 98% sure haha 😝
prologic
twtxt.net
View Thread
To be honest, I don't really see "editing" as a problem. I see that as a natural behavior of "forking" in the first place, that just forms a. new sub-tree. What's _really_ problematic here is when a feed author changes the "identity" of their feed and changes the # url = metadata field, which is what I _believe_ @cuaxolotl has just done, though I'm not 100% certain, I'm like 98% sure haha 😝
prologic
twtxt.net
View Thread
@lyse Did you check your pocket? 🤣
prologic
twtxt.net
View Thread
@lyse Did you check your pocket? 🤣
@jo
comam.es
View Thread
[47°09′36″S, 126°43′10″W] Resetting dosimeter
lyse
lyse.isobeef.org
View Thread
@movq It sounds complicated. After reading it only twice, I haven't gotten it. :-D

Yes, I'm all for dedicated message IDs. That would be a whole new format then. But I would be fine with it. The only thing is that all our clients have to be touched. At the moment, I do not worry about spoofing (however, I definitely should).
lyse
lyse.isobeef.org
View Thread
Fuck, I lost my pocket knive somewhere.
prologic
twtxt.net
View Thread
@movq Sorry but what's a partial hash exactly? 🤔
prologic
twtxt.net
View Thread
@movq Sorry but what's a partial hash exactly? 🤔
movq
www.uninformativ.de
View Thread
All this hash breakage made me wonder if we should try to introduce “message IDs” after all. 😅

But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same Message-ID header in *each and every mail*, that would break e-mail threading all the time.

In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.

If we wanted to allow editing twts, we could do something like this:

2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!

Here, mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:

2024-09-05T14:57:14+00:00 (~bpt74ka) (#hlnw5ha) Yes, hello!

That second twt has a partial hash of bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.

Would this be worth it? It’s certainly not backwards-compatible. 😂
movq
www.uninformativ.de
View Thread
All this hash breakage made me wonder if we should try to introduce “message IDs” after all. 😅

But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same Message-ID header in *each and every mail*, that would break e-mail threading all the time.

In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.

If we wanted to allow editing twts, we could do something like this:

2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!

Here, mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:

2024-09-05T14:57:14+00:00 (~bpt74ka) (#hlnw5ha) Yes, hello!

That second twt has a partial hash of bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.

Would this be worth it? It’s certainly not backwards-compatible. 😂
movq
www.uninformativ.de
View Thread
All this hash breakage made me wonder if we should try to introduce “message IDs” after all. 😅

But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same Message-ID header in *each and every mail*, that would break e-mail threading all the time.

In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.

If we wanted to allow editing twts, we could do something like this:

2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!

Here, mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:

2024-09-05T14:57:14+00:00 (~bpt74ka) (#hlnw5ha) Yes, hello!

That second twt has a partial hash of bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.

Would this be worth it? It’s certainly not backwards-compatible. 😂
movq
www.uninformativ.de
View Thread
All this hash breakage made me wonder if we should try to introduce “message IDs” after all. 😅

But the great thing about the current system is that nobody can spoof message IDs. 🤔 When you think about it, message IDs in e-mails only work because (almost) everybody plays fair. Nothing stops me from using the same Message-ID header in *each and every mail*, that would break e-mail threading all the time.

In Yarn, twt hashes are *derived* from twt content and feed metadata. That is pretty elegant and I’d hate see us lose that property.

If we wanted to allow editing twts, we could do something like this:

2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello world!

Here, mp6ox4a would be a “partial hash”: To get the actual hash of this twt, you’d concatenate the feed’s URL and mp6ox4a and get, say, hlnw5ha. (Pretty similar to the current system.) When people reply to this twt, they would have to do this:

2024-09-05T14:57:14+00:00\t(~bpt74ka) (#hlnw5ha) Yes, hello!

That second twt has a partial hash of bpt74ka and is a reply to the full hash hlnw5ha. The author of the “Hello world!” twt could then edit their twt and change it to 2024-09-05T13:37:40+00:00 (~mp6ox4a) Hello friends! or whatever. Threading wouldn’t break.

Would this be worth it? It’s certainly not backwards-compatible. 😂
prologic
twtxt.net
View Thread
@cuaxolotl Did you recently change the url metdata key of your feed?


# url = https://sunshinegardens.org/~xj9/twtxt/tw.txt


Was this at one point # url = https://sunshinegardens.org/users/xj9/twtxt/tw.txt?
prologic
twtxt.net
View Thread
@cuaxolotl Did you recently change the url metdata key of your feed?


# url = https://sunshinegardens.org/~xj9/twtxt/tw.txt


Was this at one point # url = https://sunshinegardens.org/users/xj9/twtxt/tw.txt?
prologic
twtxt.net
View Thread
@lyse Please for the love of god, elaborate 😅
prologic
twtxt.net
View Thread
@lyse Please for the love of god, elaborate 😅
prologic
twtxt.net
View Thread
@lyse da fuq?! same here, what did you just reply to?! 🤔
prologic
twtxt.net
View Thread
@lyse da fuq?! same here, what did you just reply to?! 🤔
prologic
twtxt.net
View Thread
@lyse da hell are you replying to?! 🤣
prologic
twtxt.net
View Thread
@lyse da hell are you replying to?! 🤣
prologic
twtxt.net
View Thread
Offline backups currently cost me around ~$2.00 AUD per month.~
prologic
twtxt.net
View Thread
Offline backups currently cost me around ~$2.00 AUD per month.~
prologic
twtxt.net
View Thread
Spent the day performing backups (_hadn't done it in a while 😱_) and wrote a full backup definition internal document that defines my backup process, scope, security, frequency, backup locations, capacity and backup and restoration procedures. Very happy with the doc and the updated (_now fully documented_) plan and scheduled backup frequency (_once per month, which I'll put into my calendar as it's done by hand for now, with tools_). So far backing up ~410GB out of a possible ~12.8TB worth of data in two locations -- I deliberately don't backup everything as much of the data can be re-created (_music, videos, tv shows, etc_). #Backups #Data_
prologic
twtxt.net
View Thread
Spent the day performing backups (_hadn't done it in a while 😱_) and wrote a full backup definition internal document that defines my backup process, scope, security, frequency, backup locations, capacity and backup and restoration procedures. Very happy with the doc and the updated (_now fully documented_) plan and scheduled backup frequency (_once per month, which I'll put into my calendar as it's done by hand for now, with tools_). So far backing up ~410GB out of a possible ~12.8TB worth of data in two locations -- I deliberately don't backup everything as much of the data can be re-created (_music, videos, tv shows, etc_). #Backups #Data_
@jo
comam.es
View Thread
[47°09′09″S, 126°43′57″W] Dosimeter malfunction
lyse
lyse.isobeef.org
View Thread
@cuaxolotl Yes, that's how it works. It never occurred to me that I just start changing things without a plan first.
lyse
lyse.isobeef.org
View Thread
@cuaxolotl Yes, that's how it works. It never occurred to me that I just start changing things without a plan first.
lyse
lyse.isobeef.org
View Thread
@cuaxolotl Hahahaha! :-D
lyse
lyse.isobeef.org
View Thread
@cuaxolotl Hahahaha! :-D
lyse
lyse.isobeef.org
View Thread
@prologic Not my cup of tea.
@jo
comam.es
View Thread
[47°09′21″S, 126°43′10″W] Reading: 1.59 Sv
prologic
twtxt.net
View Thread
I'll share my opinion on this later 🤣
prologic
twtxt.net
View Thread
I'll share my opinion on this later 🤣
prologic
twtxt.net
View Thread
What do we think about this? 😅
prologic
twtxt.net
View Thread
What do we think about this? 😅
prologic
twtxt.net
View Thread
Swa this pop up in my Github news feed today 🤔 Which links to https://github.com/musingstudio/go-subclub

> A Go (golang) library for interacting with the sub.club API.

So I got curious and had a peek 👀

> Let's fund the Fediverse
>> Posting or hosting on the open social networks no longer means you have to do it for free. Developer Preview now available.

And further down:

> Monetize your feeds
>> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.
>>
>> That's a promise not available on the Fediverse ...until now.

Hmmm 🤔
prologic
twtxt.net
View Thread
Swa this pop up in my Github news feed today 🤔 Which links to https://github.com/musingstudio/go-subclub

> A Go (golang) library for interacting with the sub.club API.

So I got curious and had a peek 👀

> Let's fund the Fediverse
>> Posting or hosting on the open social networks no longer means you have to do it for free. Developer Preview now available.

And further down:

> Monetize your feeds
>> If you post quality content and you've developed a loyal audience, you should be able to ask your most passionate followers to support you with a premium subscription.
>>
>> That's a promise not available on the Fediverse ...until now.

Hmmm 🤔
stats
yarn.meff.me
View Thread
🧮 USERS:1 FEEDS:2 TWTS:1085 ARCHIVED:78244 CACHE:2417 FOLLOWERS:17 FOLLOWING:14
fredg
galusik.fr
View Thread
https://galusik.fr/fridayrockmetal/2024-09-06-frm.m3u Tonight #fridayrockmetal playlist
prologic
twtxt.net
View Thread
@slashdot I can only see a mass exodus of uses fleeing telegram as the service becomes less secure or less privacy focused and basically more shit.
prologic
twtxt.net
View Thread
@slashdot I can only see a mass exodus of uses fleeing telegram as the service becomes less secure or less privacy focused and basically more shit.
cuaxolotl
sunshinegardens.org
View Thread
RT https://hispagatos.space/@argumento/113092655322062316
prologic
twtxt.net
View Thread
@quark cheers 🍻
prologic
twtxt.net
View Thread
@quark cheers 🍻
prologic
twtxt.net
View Thread
it might have made sense in the days of hose and buggy and smoke signals to centralise everything, but these days we have a globalized interconnected society with fast transport and communications. There is no reason for this model anymore 🤣
prologic
twtxt.net
View Thread
it might have made sense in the days of hose and buggy and smoke signals to centralise everything, but these days we have a globalized interconnected society with fast transport and communications. There is no reason for this model anymore 🤣
prologic
twtxt.net
View Thread
@slashdot Can we please stop this whole "Back to the Office" garbage nonsense?! 😱 If a job does not require the physical presence of a person(s) to perform their role, or they are not "customer facing" or in a job that's required to "serve the public", let's just stop this utter nonsense. As much as I want my shares in Cromwell to go up, I really don't care. Let the corporate office buildings burn to the ground for all I care, turn them into cheap housing estates or apartments. Why we ever thought centralizing in once place to live and work is beyond me 🤦‍♂️
prologic
twtxt.net
View Thread
@slashdot Can we please stop this whole "Back to the Office" garbage nonsense?! 😱 If a job does not require the physical presence of a person(s) to perform their role, or they are not "customer facing" or in a job that's required to "serve the public", let's just stop this utter nonsense. As much as I want my shares in Cromwell to go up, I really don't care. Let the corporate office buildings burn to the ground for all I care, turn them into cheap housing estates or apartments. Why we ever thought centralizing in once place to live and work is beyond me 🤦‍♂️
prologic
twtxt.net
View Thread
@cuaxolotl No you're not the only one. I do this too, I often think about a problem in my head, even imagine the code, sometimes for weeks, hell even months, before I even write a line of code 🧑‍💻
prologic
twtxt.net
View Thread
@cuaxolotl No you're not the only one. I do this too, I often think about a problem in my head, even imagine the code, sometimes for weeks, hell even months, before I even write a line of code 🧑‍💻
prologic
twtxt.net
View Thread
@lyse Thankfully it's quite cool here so far 👌
prologic
twtxt.net
View Thread
@lyse Thankfully it's quite cool here so far 👌
jcolag
john.colagioia.net
View Thread
On my blog: Toots 🦣 from 09/02 to 09/06 https://john.colagioia.net/blog/2024/09/06/week.html #linkdump #socialmedia #quotes #week