> 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. š¤
> 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. š¤
> 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. š¤
> 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. š¤
> 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? š)
> 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? š)
> 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? š)
> 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? š)
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. š
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. š
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. š
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. š
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I donāt really have that in my inbox. š¤
These are the Top 10, btw:
$ awk '/^From: / { user\n++ } END { for (u in user) { print user\n, u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I donāt really have that in my inbox. š¤
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I donāt really have that in my inbox. š¤
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I donāt really have that in my inbox. š¤
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I donāt really have that in my inbox. š¤
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
And I just realized: Muttās layout helps a lot. Skimming over new twts is really easy and itās not a big loss if there are a couple of shitpostsā¢ in my ātimelineā. This is very different from Mastodon (both the default web UI and all clients Iāve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. š
(I mostly only follow Hashtags on Mastodon anyway. Itās more interesting that way.)
And I just realized: Muttās layout helps a lot. Skimming over new twts is really easy and itās not a big loss if there are a couple of shitpostsā¢ in my ātimelineā. This is very different from Mastodon (both the default web UI and all clients Iāve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. š
(I mostly only follow Hashtags on Mastodon anyway. Itās more interesting that way.)
And I just realized: Muttās layout helps a lot. Skimming over new twts is really easy and itās not a big loss if there are a couple of shitpostsā¢ in my ātimelineā. This is very different from Mastodon (both the default web UI and all clients Iāve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. š
(I mostly only follow Hashtags on Mastodon anyway. Itās more interesting that way.)
And I just realized: Muttās layout helps a lot. Skimming over new twts is really easy and itās not a big loss if there are a couple of shitpostsā¢ in my ātimelineā. This is very different from Mastodon (both the default web UI and all clients Iāve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. š
(I mostly only follow Hashtags on Mastodon anyway. Itās more interesting that way.)
st3wsda and it started like this:(#yqke7sq) I've been sketching out some ā¦
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some ā¦
This canāt be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. š
st3wsda and it started like this:(#yqke7sq) I've been sketching out some ā¦
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some ā¦
This canāt be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. š
st3wsda and it started like this:(#yqke7sq) I've been sketching out some ā¦
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some ā¦
This canāt be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. š
st3wsda and it started like this:(#yqke7sq) I've been sketching out some ā¦
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some ā¦
This canāt be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. š
# follow_notify = gemini://foo/bar to your feedās metadata, so that clients who follow you can ping that URL every now and then? How would you even notice that, do you regularly read your gemini logs? š¤
# follow_notify = gemini://foo/bar to your feedās metadata, so that clients who follow you can ping that URL every now and then? How would you even notice that, do you regularly read your gemini logs? š¤
# follow_notify = gemini://foo/bar to your feedās metadata, so that clients who follow you can ping that URL every now and then? How would you even notice that, do you regularly read your gemini logs? š¤
# follow_notify = gemini://foo/bar to your feedās metadata, so that clients who follow you can ping that URL every now and then? How would you even notice that, do you regularly read your gemini logs? š¤
https://devblogs.microsoft.com/oldnewthing/20211129-00/?p=105979
Confession: I completely forgot that Alt+Tab existed in text mode. š¤¦ Itās not even a hidden feature, itās advertised right when you start a fullscreen dos box. Well, Alt+Tab wasnāt a thing I did regularly anyway ā it was usually Ctrl+Esc to open the window list (which also worked in OS/2). š¤ I *think* I only started using Alt+Tab when Windows 95 removed Ctrl+Esc (because it had no use anymore, it essentially got replaced by the tasklist).
https://devblogs.microsoft.com/oldnewthing/20211129-00/?p=105979
Confession: I completely forgot that Alt+Tab existed in text mode. š¤¦ Itās not even a hidden feature, itās advertised right when you start a fullscreen dos box. Well, Alt+Tab wasnāt a thing I did regularly anyway ā it was usually Ctrl+Esc to open the window list (which also worked in OS/2). š¤ I *think* I only started using Alt+Tab when Windows 95 removed Ctrl+Esc (because it had no use anymore, it essentially got replaced by the tasklist).
https://devblogs.microsoft.com/oldnewthing/20211129-00/?p=105979
Confession: I completely forgot that Alt+Tab existed in text mode. š¤¦ Itās not even a hidden feature, itās advertised right when you start a fullscreen dos box. Well, Alt+Tab wasnāt a thing I did regularly anyway ā it was usually Ctrl+Esc to open the window list (which also worked in OS/2). š¤ I *think* I only started using Alt+Tab when Windows 95 removed Ctrl+Esc (because it had no use anymore, it essentially got replaced by the tasklist).
https://devblogs.microsoft.com/oldnewthing/20211129-00/?p=105979
Confession: I completely forgot that Alt+Tab existed in text mode. š¤¦ Itās not even a hidden feature, itās advertised right when you start a fullscreen dos box. Well, Alt+Tab wasnāt a thing I did regularly anyway ā it was usually Ctrl+Esc to open the window list (which also worked in OS/2). š¤ I *think* I only started using Alt+Tab when Windows 95 removed Ctrl+Esc (because it had no use anymore, it essentially got replaced by the tasklist).
https://devblogs.microsoft.com/oldnewthing/20240903-00/?p=110205
All this Virtual Machine Manager stuff went completely over my head back then ā¦ š¤Æ
https://devblogs.microsoft.com/oldnewthing/20240903-00/?p=110205
All this Virtual Machine Manager stuff went completely over my head back then ā¦ š¤Æ
https://devblogs.microsoft.com/oldnewthing/20240903-00/?p=110205
All this Virtual Machine Manager stuff went completely over my head back then ā¦ š¤Æ
https://devblogs.microsoft.com/oldnewthing/20240903-00/?p=110205
All this Virtual Machine Manager stuff went completely over my head back then ā¦ š¤Æ
> But maybe with the climate getting hotter and hotter, they migrate north to me, too.
And a lot of other nasty stuff with it, bugs, spiders, you name it. Didnāt we migrate all this way up north to be free from such Ungeziefer? š
> But maybe with the climate getting hotter and hotter, they migrate north to me, too.
And a lot of other nasty stuff with it, bugs, spiders, you name it. Didnāt we migrate all this way up north to be free from such Ungeziefer? š
> But maybe with the climate getting hotter and hotter, they migrate north to me, too.
And a lot of other nasty stuff with it, bugs, spiders, you name it. Didnāt we migrate all this way up north to be free from such Ungeziefer? š
> But maybe with the climate getting hotter and hotter, they migrate north to me, too.
And a lot of other nasty stuff with it, bugs, spiders, you name it. Didnāt we migrate all this way up north to be free from such Ungeziefer? š
https://movq.de/v/f79b94485a/s.png
This was really useful. š¤ Chromium also did it for a while and then they removed it due to privacy concerns. Now none of the popular browsers do it anymore. š«¤
- https://bugzilla.mozilla.org/show_bug.cgi?id=665531
- https://chromium.googlesource.com/chromium/src/+/a9b4fb70b4318b220deee0da7b1693d16b8ed071
- https://bugs.webkit.org/show_bug.cgi?id=260778
https://movq.de/v/f79b94485a/s.png
This was really useful. š¤ Chromium also did it for a while and then they removed it due to privacy concerns. Now none of the popular browsers do it anymore. š«¤
- https://bugzilla.mozilla.org/show_bug.cgi?id=665531
- https://chromium.googlesource.com/chromium/src/+/a9b4fb70b4318b220deee0da7b1693d16b8ed071
- https://bugs.webkit.org/show_bug.cgi?id=260778
https://movq.de/v/f79b94485a/s.png
This was really useful. š¤ Chromium also did it for a while and then they removed it due to privacy concerns. Now none of the popular browsers do it anymore. š«¤
- https://bugzilla.mozilla.org/show_bug.cgi?id=665531
- https://chromium.googlesource.com/chromium/src/+/a9b4fb70b4318b220deee0da7b1693d16b8ed071
- https://bugs.webkit.org/show_bug.cgi?id=260778
https://movq.de/v/f79b94485a/s.png
This was really useful. š¤ Chromium also did it for a while and then they removed it due to privacy concerns. Now none of the popular browsers do it anymore. š«¤
- https://bugzilla.mozilla.org/show_bug.cgi?id=665531
- https://chromium.googlesource.com/chromium/src/+/a9b4fb70b4318b220deee0da7b1693d16b8ed071
- https://bugs.webkit.org/show_bug.cgi?id=260778
# follow_notify = gopher://foo/bar
And we ping that every now and then? š¤=
# follow_notify = gopher://foo/bar
And we ping that every now and then? š¤=
# follow_notify = gopher://foo/bar
And we ping that every now and then? š¤=
# follow_notify = gopher://foo/bar
And we ping that every now and then? š¤=
I also saw a string of starlink satellites passing by. What a strange sight that was.
I also saw a string of starlink satellites passing by. What a strange sight that was.
I also saw a string of starlink satellites passing by. What a strange sight that was.
I also saw a string of starlink satellites passing by. What a strange sight that was.
gemini://sunshinegardens.org/users/xj9/twtxt/tw.txt
But there *are*
nick, url, and description metadata headers in the feed, even an avatar. š¤
gemini://sunshinegardens.org/users/xj9/twtxt/tw.txt
But there *are*
nick, url, and description metadata headers in the feed, even an avatar. š¤
gemini://sunshinegardens.org/users/xj9/twtxt/tw.txt
But there *are*
nick, url, and description metadata headers in the feed, even an avatar. š¤
gemini://sunshinegardens.org/users/xj9/twtxt/tw.txt
But there *are*
nick, url, and description metadata headers in the feed, even an avatar. š¤
Whatās going on with the frogs? I guess they canāt properly see in the dark? š¤
That large āindividualā towards the would have freaked me out. Was it at least furry? Or was it a huge spider? š¤Ŗ
Whatās going on with the frogs? I guess they canāt properly see in the dark? š¤
That large āindividualā towards the would have freaked me out. Was it at least furry? Or was it a huge spider? š¤Ŗ
Whatās going on with the frogs? I guess they canāt properly see in the dark? š¤
That large āindividualā towards the would have freaked me out. Was it at least furry? Or was it a huge spider? š¤Ŗ
Whatās going on with the frogs? I guess they canāt properly see in the dark? š¤
That large āindividualā towards the would have freaked me out. Was it at least furry? Or was it a huge spider? š¤Ŗ
http://www.avernus.com/desktop-textures/copyright.html
But the following addendum does not exist yet in the
COPYRIGHT file on my disk. š
> This restriction does not apply to use in World-Wide Web pages served from or viewed on Windows machines.
http://www.avernus.com/desktop-textures/copyright.html
But the following addendum does not exist yet in the
COPYRIGHT file on my disk. š
> This restriction does not apply to use in World-Wide Web pages served from or viewed on Windows machines.
http://www.avernus.com/desktop-textures/copyright.html
But the following addendum does not exist yet in the
COPYRIGHT file on my disk. š
> This restriction does not apply to use in World-Wide Web pages served from or viewed on Windows machines.
http://www.avernus.com/desktop-textures/copyright.html
But the following addendum does not exist yet in the
COPYRIGHT file on my disk. š
> This restriction does not apply to use in World-Wide Web pages served from or viewed on Windows machines.