Searching yarn

Twts matching #http
Sort by: Newest, Oldest, Most Relevant
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@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 » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

** WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to “store now, decrypt later” attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html

😱😱😱

⤋ Read More
↳ In-reply-to » @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 » 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
↳ 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

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/

⤋ Read More
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@rdlmda@rdlmda.me I never saw the point of a registry to be honest, as it defeated the point of what I believed to be a truly decentralised non-social social ecosystem. What can and does work however is a search engine and crawler. I used to run one, but I took it down, mostly because it got expensive to operate, at least the implementation I built… Maybe one day i’ll try again with a SQLite backend.

⤋ Read More