I would also like to add that their entire Web portal works without JavaScript and it has all the features you would expect and more.
I would also like to add that their entire Web portal works without JavaScript and it has all the features you would expect and more.
I also pay $1 per gigabyte-month for storage and I am using 9.29 MiB which means I pay a little less than one cent per month. It used to be even less than that, but since I started using Git the complete Git history is stored on the server as well as the live copy of the site.
There is an additional charge of 1 cent per 44.64 "RAUs", their measurement combining CPU and memory usage over time. On the Non-Production plan, only resources used by processes other than the Web server are counted. I don't believe I have ever been charged for this.
Here is my billing report for 2023 so far.
tag URIs, nice. :)That looks like a good system. Simple and effective. I ask because my current backup system is lacking and I'd like to do something about that. I don't want to use cloud storage, so I'll be moving hard drives around. I'm just not sure on what to do on the software side.
Solutions like Restic and Borg have many advantages, but the disadvantage is that your data is confined to that particular tool. I think I'm willing to make that trade to have snapshots, compression, deduplication, etc. I'm just on the fence about which one I should use.
@prologic, why did you choose Restic? How do you like it so far? If you've had to restore from the backup, what was that like?
tag URIs, nice. :)That looks like a good system. Simple and effective. I ask because my current backup system is lacking and I'd like to do something about that. I don't want to use cloud storage, so I'll be moving hard drives around. I'm just not sure on what to do on the software side.
Solutions like Restic and Borg have many advantages, but the disadvantage is that your data is confined to that particular tool. I think I'm willing to make that trade to have snapshots, compression, deduplication, etc. I'm just on the fence about which one I should use.
@prologic, why did you choose Restic? How do you like it so far? If you've had to restore from the backup, what was that like?
mckinley.cc is now available as a Tor hidden service: http://mckinley2nxomherwpsff5w37zrl6fqetvlfayk2qjnenifxmw5i4wyd.onion/
I don't want ~27 hours generating keys to go to waste :)~
> However, the key on the unencrypted partition is only valid for the time it takes to reboot, assuming we reboot as soon as the script completes.
fc either. It will definitely come in handy.
sudo !! (or doas !!) if you're using Bash.
Monero in particular uses an algorithm that's supposed to be ASIC resistant and, while it can be mined on a GPU, it's more efficient to mine on a CPU. I'm curious if that makes it easier or harder for a hostile entity to perform a 51% attack.
Is this true, @prologic?
I compiled it and followed you, but whenever I run
./twtwt timeline it requests my followed feeds in an infinite loop. I didn't realize until I sent, probably, 150 requests, so I'm very sorry for clogging up your logs. ./twtwt view win0error works fine.
Well, really, it's the only frontend to a board game server that can be used as an online clone of Monopoly.
There are a couple public instances that we can use.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled]\n[Scheduled]\n[Scheduled]\n[Scheduled]\n" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "\n\n\n\n\n\n\n\n" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled]" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled]" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled][Scheduled][Scheduled][Scheduled][Scheduled][Scheduled][Scheduled][Scheduled]" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "\n\n\n\n" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "\n\n" in the title for premieres and remove it when the video is available.
If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled][Scheduled=]" in the title for premieres and remove it when the video is available.=
If there was a rule that you've broken, then it's content moderation. A separate discussion can be had over whether or not that rule is just.
Fortunately, twtxt is very difficult to suppress completely. As long as I can still put a text file somewhere for people to download, I can still post.
Apple doesn't care about you: https://mckinley.cc/notes/20221229-apple-doesnt-care.html
> Should we go for multi-user and org/user? Or keep it simple?
I really don't know which would be better.
You would need user accounts for issues and to facilitate collaboration, unless you used e-mail, which isn't really a bad thing. The SourceHut model works very well.
No matter what, I would love to be able to archive issues using Git alone. You were talking about integrating git-bug or something similar, and I think that's an excellent idea.
@prologic, @prologic@twtxt.net, @prologic. @prologic@twtxt.net. @<prologic https://twtxt.net/user/prologic/twtxt.txt>, @<prologic https://twtxt.net/user/prologic/twtxt.txt>.
@prologic, @prologic, @prologic. @prologic. @prologic, @prologic.
@prologic,@prologic,
Also, the shorthand mention syntax has struck again. Apologies, @justamoment.
ssh ed@bitreich.org.
Don't let it get to you, man. Interoperability with vanilla twtxt is the best feature of Yarn, and it's not worth breaking that because of one person. Besides, you won't win him over even if you do.
Don't let it get to you, man. Interoperability with vanilla twtxt is the best feature of Yarn, and it's not worth breaking that because of one person. Besides, you won't win him over even if you do.
Are you running IRIX on the SGIs?
Are you running IRIX on the SGIs?
As far as I know, you have to load the page in a browser before you can see the entire URL, giving it the opportunity to redirect somewhere else or exploit some vulnerability on your device.
I think we agree here. When the user has no control and is taught to blindly trust these things, bad things happen.
You can put a sticker with a QR code (and no other information) on a wall in a city and people will scan it out of curiosity. They scan it, their iPhone only tells them it goes to snapchat.com (I just checked on the latest version of iOS), and they end up on my website instead because it's an open redirect.
Granted, my website is a much better place to be than snapchat.com, but you get the idea.