Searching We.Love.Privacy.Club

Twts matching #twtxt
Sort by: Newest, Oldest, Most Relevant
In-reply-to » @falsifian Congrats, mate, no sleep at night anymore! ;-D That's a cool age measuring blanket. Haven't seen something like that before.

@lyse@lyse.isobeef.org Thanks for letting me know. HTML checkers seem happy now. I’m not sure what to do about the images not loading. The photos have three sizes (thumbnail, photo page, and original if you click the img tag on the photo page); can you at least see the smaller two sizes? Maybe I will do some experimental fetches and/or start measuring things on my web server.

⤋ Read More
In-reply-to » Yeah. It's a peculiar situation.

@rdlmda@rdlmda.me What a truly wonderful description. ;‘-D But sorry to hear that. Luckily, no issues over here. It’s extremely rare that this happens. Last time (around five years ago or so) they were cutting down trees in the forest and threw a tree in the overhead power line (which had been converted to underground last year). Power had to be killed in order for the fire brigade to actually extinguish the fire.

⤋ Read More

My twtxt instance is under a de-facto attack. Or, at this point, I can’t even differentiate an attack from the other in the constant barrage or malicious requests.

There were so many bots hammering it, in only 3 days, they consumed the ironically significant amount of 666 MB — I kid you not! In the last 24 hours, there were 59,673 hits on this endpoint alone.

I had to put my twtxt web interface behind a password-protected BasicAuth directive. As I’m the only one using it, it’s fine.

Bots, scrappers and Large Laggy Manglers are poisoning the open web.

⤋ Read More
In-reply-to » For the record, the third thing is to activate agent forwarding. In ~/.ssh/config:

@lyse@lyse.isobeef.org Hm, I’m not sure I would want to do that:

ForwardAgent
    ...

    Agent forwarding should be enabled  with  caution.   Users
    with  the ability to bypass file permissions on the remote
    host (for the agent's Unix-domain socket) can  access  the
    local agent through the forwarded connection.  An attacker
    cannot  obtain  key  material from the agent, however they
    can perform operations on the keys that enable them to au‐
    thenticate using the identities loaded into the agent.

⤋ Read More
In-reply-to » Third power failure in two weeks. Every time a different apartment loses power at the same time as mine. I hope the power company is able to find the cause.

@rdlmda@rdlmda.me that’s odd. In here is similar, but not random. All it takes is some rain, and then flip a coin: we may, or may not lose power.

⤋ Read More
In-reply-to » @lyse Changing the user name helped, it now says Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).

@movq@www.uninformativ.de I don’t think it is anything you are doing wrong. I think it is on @prologic@twtxt.net side. I am getting the exact same result, but I never cloned that repository. Maybe it worked fine at certain point, when @lyse@lyse.isobeef.org cloned it, but I doubt brand new users can get through.

⤋ Read More
In-reply-to » Anyone else having trouble pulling from git.mills.io? 🤔

@lyse@lyse.isobeef.org Changing the user name helped, it now says Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).

Here’s a debug log, @prologic@twtxt.net, perhaps you could take a look at this 🙏: https://movq.de/v/116c5f514b/clone2.txt

(Might be a silly mistake on my part. Wrong remote path or something?)

⤋ Read More
In-reply-to » (#vzivuda) @kiwu Sorry, I have two functional brain cells left in my brain, and I'm not sure if you're asking What am I putting in it, as in a) when making some? Or as in b) when consuming/serving it?

@rdlmda@rdlmda.me it is called, in Spanish, “the mother”. It is created through a bit (not by much) effort, and kept as a starting point. Just like Asian cuisine has dishes that never cool, always cooking leaving always a base on it.

How do you think a lathe (and just about any tool, etc.) is done? Yup, in part by using a lathe. 😅

⤋ Read More
In-reply-to » Registries suck. Or, should I say, "bend". I say look at the people @prologic is following, and you have found the whole twtxt world. 😅

Yes… Look at everyone @prologic@twtxt.net is following! Next, look at everyone each one of them is following… Next… Hmm… Build a graph of follows and mentions, it’ll be so FUN and not at all time-consuming

– My evil ADHD brain

Image

⤋ Read More
In-reply-to » Hello twtxt! I still exist. I have a baby now and put some pictures at https://photos.falsifian.org/ . Album HTML loosely inspried by @lyse

@falsifian@www.falsifian.org Congrats, mate, no sleep at night anymore! ;-D That’s a cool age measuring blanket. Haven’t seen something like that before.

Btw. the index.html includes an out of place </ul>. And I just wanna let you know that the full-size photos don’t load for me over here across the pond. They always run into a timeout after a few slooow percent. But no worries. :-)

⤋ Read More

Anyone else having trouble pulling from git.mills.io? 🤔

$ g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
Cloning into 'twtxt.dev'...
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.

The key verification function on https://git.mills.io/user/settings/keys says I’m using the correct key.

This also looks good:

$ GIT_SSH_COMMAND="ssh -v" g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
...
debug1: Authentications that can continue: publickey
debug1: Offering public key: /home/user/.ssh/keys/key-millsio ED25519 SHA256:nVNT... explicit
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.

Does it work for you, @lyse@lyse.isobeef.org @prologic@twtxt.net?

⤋ Read More
In-reply-to » Last year, I made a huge mistake. I repeated on here, what multiple sourcea at Google told me, and what is to this day, written on their blog about Android. I failed to take into consideration, that people who work at Google, often just lie, or present things intentionally vaguely, so they do not have to follow through with their promises. I would like to apologize to everyone, who took my previous posts here, as assurance software not explicitly approved by Google, will continue working on Android, past this year (or even just a couple months from now) and that everything has been resolved, as things are now in fact even worse, than they were before. To follow the current state of "Open Android", please check: https://keepandroidopen.org/

@bender@twtxt.net It is not yet lost, other than the ongoing communication with local politicians, the European Commission, (thanks to other developers) the U.S. Department of Justice, over 50 other organizations (see some of them, signed on the open letter, top of the before mentioned website), we’re also actively looking into possible workarounds and exploring other available legal options, while companies like Motorola, are already planning to offer GrapheneOS, on some phones.

⤋ Read More
In-reply-to » Last year, I made a huge mistake. I repeated on here, what multiple sourcea at Google told me, and what is to this day, written on their blog about Android. I failed to take into consideration, that people who work at Google, often just lie, or present things intentionally vaguely, so they do not have to follow through with their promises. I would like to apologize to everyone, who took my previous posts here, as assurance software not explicitly approved by Google, will continue working on Android, past this year (or even just a couple months from now) and that everything has been resolved, as things are now in fact even worse, than they were before. To follow the current state of "Open Android", please check: https://keepandroidopen.org/

@thecanine@twtxt.net sorry to hear that, mate. Don’t worry, something better will come up. After all, it has got to be easy to beat Android, right? :-)

⤋ Read More
In-reply-to » Last year, I made a huge mistake. I repeated on here, what multiple sourcea at Google told me, and what is to this day, written on their blog about Android. I failed to take into consideration, that people who work at Google, often just lie, or present things intentionally vaguely, so they do not have to follow through with their promises. I would like to apologize to everyone, who took my previous posts here, as assurance software not explicitly approved by Google, will continue working on Android, past this year (or even just a couple months from now) and that everything has been resolved, as things are now in fact even worse, than they were before. To follow the current state of "Open Android", please check: https://keepandroidopen.org/

@bender@twtxt.net Yes, really should have chosen my words more wisely. As @movq@www.uninformativ.de mentions, we got a vague promise of an “advanced flow” being implemented, and in my case also a vague promise of a video call, with someone at Google, regarding it. Now when the backlash died down, it does not look like Google plans to follow through, with any of this and they’re completely unwilling to elaborate and get back to us, about if and how any of this will be implemented.

⤋ Read More
In-reply-to » Last year, I made a huge mistake. I repeated on here, what multiple sourcea at Google told me, and what is to this day, written on their blog about Android. I failed to take into consideration, that people who work at Google, often just lie, or present things intentionally vaguely, so they do not have to follow through with their promises. I would like to apologize to everyone, who took my previous posts here, as assurance software not explicitly approved by Google, will continue working on Android, past this year (or even just a couple months from now) and that everything has been resolved, as things are now in fact even worse, than they were before. To follow the current state of "Open Android", please check: https://keepandroidopen.org/

@thecanine@twtxt.net are you referring to the “WE FUCKING WON!” twtxt?

⤋ Read More