> one probably needs their own pod to play with themes
That’s super easy, just run a local one, like @prologic and @darch do. You don’t need to run it on the open Net, only on your own machine.
> one probably needs their own pod to play with themes
That’s super easy, just run a local one, like @prologic and @darch do. You don’t need to run it on the open Net, only on your own machine.
I also try to link things just as I would do on a web page, not just drop long URLs. Don’t get me wrong, sometimes I hate being this bloody picky. 😅
> there seem to be too much space over the txt-context now - at least on mobil
I have fixed that. PR pending commit.
dreadnought:fastidious$ gpg --locate-keys me@sour.is
gpg: key 8B3B0604F164E04F: public key "Xuu at Sour.is <me@sour.is>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: no ultimately trusted keys found
pub rsa4096 2016-08-15 [SC] [expires: 2024-09-12]
20AE2F310A74EA7CEC3AE69F8B3B0604F164E04F
uid [ unknown] Xuu at Sour.is <me@sour.is>
sub rsa4096 2016-08-15 [E] [expires: 2024-09-11]
> can you try the wkd now?
Getting:
dreadnought:fastidious$ gpg --locate-keys me@sour.is
gpg: error retrieving 'me@sour.is' via WKD: Network is unreachable
gpg: error reading key: Network is unreachable
> I’m indifferent on this one
Oh, no, then we'll just leave it as is. Liking it this way must be the reason he changed it, so why bother? 😂 I can always change it, or develop a liking for the new one. So, meh too.
> so you would want me to spend even more time building native iOS and Android apps
I know it isn’t doable. That’s why I think is best to focus on offering a first class experience on the web. I am on mobile web right now, no problems. 😊
systemd information on Yarn's wiki!
> The subject is the message-id, so, why not?
The subject (hash, in case my naming is wrong) is in the
in-reply-to header.
> I don’t just want to see “@lyse”, I want to see the URL as well
I agree on that. I was only referring to the hash. Having it on body is superfluous, and just adds unneeded noise.
I truly love where *jenny* is headed!
> Funny, I’m so used to seeing these tags, it’s almost a bit confusing now that they’re “missing”.
They are all gone from *yarnd* as well (even from the twt body!). So much cleaner!
networkQuality does a pretty decent job to measure network speeds.h
dreadnought:fastidious$ networkQuality -s
==== SUMMARY ====
Upload capacity: 530.336 Mbps
Download capacity: 871.282 Mbps
Upload flows: 16
Download flows: 12
Upload Responsiveness: High (2981 RPM)
Download Responsiveness: High (2055 RPM)
> Sorry don’t really get your reasoning here…
It would be amazing if when I hit reply to a twt in a conversation (like I did on this one for
#rp47m4q, your twt), the *twt-context* link would go straight to the twt I replied (like this) to within a conversation, not to the conversation top, as it does now.
> How do I activate the new twt-context on my own pod?
Use
show_twt_context under "Enabled Optional Features" on "Manage Pod".
fastidious@tilde:~$ gpg --search me@sour.is
gpg: data source: https://keys.openpgp.org:443
(1) Xuu at Sour.is <me@sour.is>
xuu at dn42 <xuu@dn42.us>
4096 bit RSA key 8B3B0604F164E04F, created: 2016-08-15
Keys 1-1 of 1 for "me@sour.is". Enter number(s), N)ext, or Q)uit >
<a href="{{ urlForRootConv $.Twt }}"><small class="twt-context">{{ formatTwtContext $.Twt $.User }}</small></a>
What token would I use to set a
:target to the starter twt on the conversation? I tried using $.Twt, but it is encoded for URL. What I am looking to do is something like this:
<a href="{{ urlForRootConv $.Twt }}#HASH_OF_FIRST_TWT"><small class="twt-context">{{ formatTwtContext $.Twt $.User }}</small></a>
Will that be possible?
<a href="{{ urlForRootConv $.Twt }}"><small class="twt-context">{{ formatTwtContext $.Twt $.User }}</small></a>
What token would I use to set a
:target to the starter twt on the conversation? I tried using $.Twt, but it is encoded for URL. What I am looking to do is something like this:
<a href="{{ urlForRootConv $.Twt }}/#HASH_OF_FIRST_TWT"><small class="twt-context">{{ formatTwtContext $.Twt $.User }}</small></a>
Will that be possible?
99-yarn.css, and forgot to *minify*. All good now.
> Also there is no need to render the twt-context in conversation view ;)
Actually, I would say *we need to only show the content in conversation view*.
Your cat must be family on my mum’s dog. He does the same quite often, so he loves me because I give him delightful treats. Mum says I spoil him; I tell her he only lives once.
> They used it to send like 3 or 4 inconsequential emails and then just gave up on it
Pretty much like the rest of us 😂. I use GnuPG to encrypt anything sensitive that I upload to clouds, and occasionally sign an email (ASCII armoured, not PGP MIME), but that’s pretty much it.
> Naturally we wanted to share those moments with our extended family… What are your choices?
Our family normally share photos via iCloud Photos, Google Photos, or directly via Messages (or SMS/MMS) if they're just a handful of photos to share.
> I’ve never been to a key signing party? Sounds too hip for me [...]
It is dated now, not hip. I went to two or three in the late 1990's. My first and very old---now defunct and gone---PGP RSA key was signed by Zimmermann himself.
> Right now, I’m very skeptical, but that might just be my German pessimism.
I am also skeptical, but that might just be my Spanish cynicism. 🤣
> Signed this feed [...]
I can't find your key at hkps://keys.openpgp.org, so can't fully verify.
publish_command and verify outside *jenny*, so, if it add bloat and extra complexity I would say pass.
publish_command and verify outside *jenny*, so, if it adds bloat and extra complexity I would say pass.
> This belongs into a museum.
That reminded me Indiana Jones. 😂
If there are issues, they are not show stoppers. Considering the many changes since last release, as you wrote, is makes sense to cut a release.
If there are issues, they are not show stoppers. Considering the many changes since last release, as you wrote, it makes sense to cut a release.
yarn.min.css, but separately. Is that not possible?
To further the problem, Delta COVID is also much more infectious, and that's the one going rampant. So, yeah.
To further the problem, Delta COVID is also much more infectious, and that's the one going rampant. So, yeah.
> I believe this commit fixes that bug
Nope. 😢
> II’m using it right now
Log out, go to Timeline, refresh. Click on any “Yarn” link. Go to bottom, click login, then login. You are back on Timeline. Click on a “Yarn” link (any random one), pick a twt within it, and look a “Reply”. You will be lucky if you see it. If you don’t, refresh page, then you will see it.
> probably teach them to floss from day 1
One thing is teaching them, the other is having them do it, or do it right. 😂
> This is not something I’ve ever observed
You have said that you exclusively use the phone app. You might never see it.
> we need to improve/fix the login flows and back to the original view
It needs to be fixed/implemented. Right now it is not working/non-existent. Just now, for example, I logged in, was on Timeline. I clicked this yarn, and went to reply to this twt of yours, saw a login at the bottom of the page. Had to refresh the page, so it knew I was logged in. That kind of things.