RFC 3339 timestamps, if I understand you correctly, I _think_ it's extremely unlikely for someone to repost a Twt (an edit) within the same second (at least not humanly possible). In any case, I've only validated the ideas so far in isolation, the algorithm(s) need to be built, feature gated, measured, understood and finally put in place with some UX (I like @ullarah's gugestion)
> you are free to have your own opinion as long as that opinion matches mine
π€¦ββοΈπ€¦ββοΈπ€¦ββοΈ
> you are free to have your own opinion as long as that opinion matches mine
π€¦ββοΈπ€¦ββοΈπ€¦ββοΈ
- Can I control who my children can and cannot contact/message/etc?
- Can I control who my children can and cannot contact/message/etc?
Ideally I would either like to be in control of the server-side -- self-hosted with accounts I can control and who/what they are able to connect to, etc.
Or, completely local to a local network (i.e: p2p, wifi only).
Ideally I would either like to be in control of the server-side -- self-hosted with accounts I can control and who/what they are able to connect to, etc.
Or, completely local to a local network (i.e: p2p, wifi only).
websub feature? π€ 
-- For those of you who are running main or prologic/yarnd:latest and have websub enabled, please update to commit c6d87580 or later πββοΈ
websub feature? π€ -- For those of you who are running main or prologic/yarnd:latest and have websub enabled, please update to commit c6d87580 or later πββοΈ
Dealing with this is hardβ’ But I have some ideas π
Dealing with this is hardβ’ But I have some ideas π
file.txt, but is there more to this? the contents makes no sense π
file.txt, but is there more to this? the contents makes no sense π
Unzip - Array buffer allocation failed
Unzip - Array buffer allocation failed
@tkanos and I are here ! π€
@tkanos and I are here ! π€
> Is this in relation to the so-called (dead and unmaintained) βreference clientβ ?
>
>> What ???????
Sorry dude, I withdraw my comment as I had no idea what each of your bullet points were referring to π I blame myself and being tired and having been up too many hours this week dealing with work π’
> Is this in relation to the so-called (dead and unmaintained) βreference clientβ ?
>
>> What ???????
Sorry dude, I withdraw my comment as I had no idea what each of your bullet points were referring to π I blame myself and being tired and having been up too many hours this week dealing with work π’
twtr to be the new reference client once complete π
twtr to be the new reference client once complete π
local Docker Volumes in my Swarm Cluster is:
$ for node in $(seq -s ' ' -f 'dm%g' 1 6); do backup-all-volumes "${node}"; done
π
local Docker Volumes in my Swarm Cluster is:
$ for node in $(seq -s ' ' -f 'dm%g' 1 6); do backup-all-volumes "${node}"; done
π
> I didnβt know about the plan to replace Goryon, how do you manage to compile it for Play store and the others?
I _believe_ we can package it up with with Cordova. But first let's just get it working and installed/deployed to
https://yarn.social/app π As it's a PWA it's immediately installable on pretty much every device/os anyway that supports PWA (quite a few now)
> I didnβt know about the plan to replace Goryon, how do you manage to compile it for Play store and the others?
I _believe_ we can package it up with with Cordova. But first let's just get it working and installed/deployed to
https://yarn.social/app π As it's a PWA it's immediately installable on pretty much every device/os anyway that supports PWA (quite a few now)
file.txt in it, but I can't be certain. I'm actually not really that familiar with CyberChef, it looks pretty cool though, probably just need to get used to it!
file.txt in it, but I can't be certain. I'm actually not really that familiar with CyberChef, it looks pretty cool though, probably just need to get used to it!
$ curl -v -o /dev/null https://twtxt.net/user/mckinley/twtxt.txt 2>&1 | grep -i 'Content-Length'
< content-length: 107361
$ curl -v -o /dev/null https://twtxt.net/user/mckinley/twtxt.txt 2>&1 | grep -i 'Content-Length'
< content-length: 107361
Yarn.social Video Conf
- Date/Time:
- Saturday, March 12 Β· 22:00 β 23:00 (AEST)
- Saturday, March 12 Β· 12:00 β 13:00 (UTC)
- Google Meet joining info
- Video call link: https://meet.google.com/xmr-syif-qkq
- Or dial: βͺ(US) +1 314-474-3042β¬ PIN: βͺ331 203 613β¬#)
> Apologies, but we'll use Google Meet this time, as sometimes folks can't join with my PeerCalls instance very well π’
#Yarn.social #Conf
Yarn.social Video Conf
- Date/Time:
- Saturday, March 12 Β· 22:00 β 23:00 (AEST)
- Saturday, March 12 Β· 12:00 β 13:00 (UTC)
- Google Meet joining info
- Video call link: https://meet.google.com/xmr-syif-qkq
- Or dial: βͺ(US) +1 314-474-3042β¬ PIN: βͺ331 203 613β¬#)
> Apologies, but we'll use Google Meet this time, as sometimes folks can't join with my PeerCalls instance very well π’
#Yarn.social #Conf
-I, --max-cache-items and -C, --max-cache-ttl options which default to 150 and 240h by default. As you are a user on my pod at twtxt.net, these settings directly impact you. If you were to run your own pod (for example) you could choose to tweak these to your 'taste". @david for example runs his pod netbros.com with quite high Cache settings.
-I, --max-cache-items and -C, --max-cache-ttl options which default to 150 and 240h by default. As you are a user on my pod at twtxt.net, these settings directly impact you. If you were to run your own pod (for example) you could choose to tweak these to your 'taste". @david for example runs his pod netbros.com with quite high Cache settings.
# Description =
# Avatar =
# Nick =
As documented in Yarn.social :: Manually π
# Description =
# Avatar =
# Nick =
As documented in Yarn.social :: Manually π
As my old man said to me many moons ago when I was first designing this (he helped and contributed ideas here!):
> If I said something X ago, I don't want someone to say "Hey but X ago you said this". What if I've changed my mind since then and now have a different opinion?
I'm paraphrasing here of course, we talk regularly on the phone, but a lot of ideas ans inspiration has come from my Dad π -- The idea here is that Humans forget, so should Yarn.social
As my old man said to me many moons ago when I was first designing this (he helped and contributed ideas here!):
> If I said something X ago, I don't want someone to say "Hey but X ago you said this". What if I've changed my mind since then and now have a different opinion?
I'm paraphrasing here of course, we talk regularly on the phone, but a lot of ideas ans inspiration has come from my Dad π -- The idea here is that Humans forget, so should Yarn.social
Cache expired posts vanish from threads with no warning - yarn - Mills
As Twts fall off the active Cache and are archived in an on-disk Archive, Yarns and Twts eventually "disappear" (they don't really, they are still searchable and accessible as everything is content addressable).
Cache expired posts vanish from threads with no warning - yarn - Mills
As Twts fall off the active Cache and are archived in an on-disk Archive, Yarns and Twts eventually "disappear" (they don't really, they are still searchable and accessible as everything is content addressable).
> youβre reading from cache, so itβs quicker. memory will always have significantly faster iops vs disk-bound read operations. also recommend giving the codebase a look. thereβs always room for contributors. iβm planning to take a crack at a few issues.
It's even more than just "memory is faster than disk". The Cache is designed to have O(1) lookups on all Profile (think Feed) and User Timeline as well as Pod Discover views. This is very important for the UX.
> youβre reading from cache, so itβs quicker. memory will always have significantly faster iops vs disk-bound read operations. also recommend giving the codebase a look. thereβs always room for contributors. iβm planning to take a crack at a few issues.
It's even more than just "memory is faster than disk". The Cache is designed to have O(1) lookups on all Profile (think Feed) and User Timeline as well as Pod Discover views. This is very important for the UX.
> As for pagination, sure, it can be hard, but why would it be harder in this case than in the cases where Yarn already does it?
It's done in the background as a background job. See this Dashbaord for a visuaul:
> (As for infinite scroll, if you have pagination on the server side already, itβs trivial on the client side. Yes you need JS of course, but not a lot)
Remember the builtin Web Interface (an SSR) is designed to be able to used without Javascript (graceful degradation).
> As for pagination, sure, it can be hard, but why would it be harder in this case than in the cases where Yarn already does it?
It's done in the background as a background job. See this Dashbaord for a visuaul:
> (As for infinite scroll, if you have pagination on the server side already, itβs trivial on the client side. Yes you need JS of course, but not a lot)
Remember the builtin Web Interface (an SSR) is designed to be able to used without Javascript (graceful degradation).
> Particularly with the apparent convention of the newest posts being at the bottom of the file.
This is generally the convenatio, yes. And folks like @lyse @xuu @movq and I have considered and talked about formalizing the "direction" of a feed including supporting "Range" requests. These are both things that I will likely do myself at some point, because it further helps with optimizing the traffic/bandwidth used and helps keeps things running smoothly as the network scales over time.
> Particularly with the apparent convention of the newest posts being at the bottom of the file.
This is generally the convenatio, yes. And folks like @lyse @xuu @movq and I have considered and talked about formalizing the "direction" of a feed including supporting "Range" requests. These are both things that I will likely do myself at some point, because it further helps with optimizing the traffic/bandwidth used and helps keeps things running smoothly as the network scales over time.
> but Iβm a little puzzled why the same issues with a feed being huge donβt present an issue every time you want to poll for updates?
They do! As I said in af4el2q Pods will refuse to fetch feeds over the
--max-fetch-limit in size. Feeds are also rotated on Pods. There is also a soec for this.
> but Iβm a little puzzled why the same issues with a feed being huge donβt present an issue every time you want to poll for updates?
They do! As I said in af4el2q Pods will refuse to fetch feeds over the
--max-fetch-limit in size. Feeds are also rotated on Pods. There is also a soec for this.
yarnd for example has a builtin weekly job that ensures feeds on a pod are kept under 1MB in size (configurable) and are rotated when they exceed this. Pods will also refuse to fetch feeds over this size too.
yarnd for example has a builtin weekly job that ensures feeds on a pod are kept under 1MB in size (configurable) and are rotated when they exceed this. Pods will also refuse to fetch feeds over this size too.
> (this is on falkon, based on qtwebengine/chromium)
> (this is on falkon, based on qtwebengine/chromium)