- KickAss 12V/24V 25A DCDC Charger With Solar MPPT + Pre-Wired Anderson
- iTECHDCDC25 12V/24V 25A DCDC & MPPT Battery Charger
- Renogy DCC30S 12V 30A Dual Input DC to DC Battery Charger with MPPT
The only advantage of the Renogy over the KickAss/ITech models is it has Bluetooth monitoring and an App capabilities so you can check the state of the battery/charging/etc from your phone.
- KickAss 12V/24V 25A DCDC Charger With Solar MPPT + Pre-Wired Anderson
- iTECHDCDC25 12V/24V 25A DCDC & MPPT Battery Charger
- Renogy DCC30S 12V 30A Dual Input DC to DC Battery Charger with MPPT
The only advantage of the Renogy over the KickAss/ITech models is it has Bluetooth monitoring and an App capabilities so you can check the state of the battery/charging/etc from your phone.
twtxt.net) so welcome 🤗 (_if you see this_)
twtxt.net) so welcome 🤗 (_if you see this_)
twtxt.net) so welcome 🤗 (_if you see this_)
Site do The Spectator com um artigo do Slavoj Zizek intitulado "Why am I popular on TikTok?"
Site do The Spectator com um artigo do Slavoj Zizek intitulado "Why am I popular on TikTok?"
A mi me da pena por la cabra. 🌩️ ⌘ Read more****
/https://baldo.cat/media/photos/IMG_2334.jpeg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
¡Mejora esto Ayuso! ⌘ Read more****
#catsoftwtxt
#catsoftwtxt
/https://duque-terron.cat/media/photos/IMG_2322.jpeg) #catsoftwtxt
/https://duque-terron.cat/media/photos/IMG_2327.jpeg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
At first, I thought that Antenna acted like a “traditional” blog aggregator, but that’s not really the case. You know, with a blog aggregator, you would normally contact the owner and ask them to include your feed. That step is not needed with Antenna.
So, when someone publishes a blog/gemlog post and you would like to “reply” to it, you can just do that: Write your post and then publish the link on Antenna. This means your Gemini capsule doesn’t need to be well known in order to participate. If I read something interesting and would like to reply, I could do that *right now* – instead of having to wait for the webmaster of the aggregator to include/unlock my feed.
Also, it’s just arbitrary Gemini links in Antenna – unlike a blog aggregator, where everything is a blog post. So I just saw someone publishing a link titled “A wild twtxt appears” and that’s just a link to their twtxt file.
In many ways, this thing is a bit more like a forum than a blog aggregator. Or maybe you could also call it a “bus”.
At first, I thought that Antenna acted like a “traditional” blog aggregator, but that’s not really the case. You know, with a blog aggregator, you would normally contact the owner and ask them to include your feed. That step is not needed with Antenna.
So, when someone publishes a blog/gemlog post and you would like to “reply” to it, you can just do that: Write your post and then publish the link on Antenna. This means your Gemini capsule doesn’t need to be well known in order to participate. If I read something interesting and would like to reply, I could do that *right now* – instead of having to wait for the webmaster of the aggregator to include/unlock my feed.
Also, it’s just arbitrary Gemini links in Antenna – unlike a blog aggregator, where everything is a blog post. So I just saw someone publishing a link titled “A wild twtxt appears” and that’s just a link to their twtxt file.
In many ways, this thing is a bit more like a forum than a blog aggregator. Or maybe you could also call it a “bus”.
At first, I thought that Antenna acted like a “traditional” blog aggregator, but that’s not really the case. You know, with a blog aggregator, you would normally contact the owner and ask them to include your feed. That step is not needed with Antenna.
So, when someone publishes a blog/gemlog post and you would like to “reply” to it, you can just do that: Write your post and then publish the link on Antenna. This means your Gemini capsule doesn’t need to be well known in order to participate. If I read something interesting and would like to reply, I could do that *right now* – instead of having to wait for the webmaster of the aggregator to include/unlock my feed.
Also, it’s just arbitrary Gemini links in Antenna – unlike a blog aggregator, where everything is a blog post. So I just saw someone publishing a link titled “A wild twtxt appears” and that’s just a link to their twtxt file.
In many ways, this thing is a bit more like a forum than a blog aggregator. Or maybe you could also call it a “bus”.
At first, I thought that Antenna acted like a “traditional” blog aggregator, but that’s not really the case. You know, with a blog aggregator, you would normally contact the owner and ask them to include your feed. That step is not needed with Antenna.
So, when someone publishes a blog/gemlog post and you would like to “reply” to it, you can just do that: Write your post and then publish the link on Antenna. This means your Gemini capsule doesn’t need to be well known in order to participate. If I read something interesting and would like to reply, I could do that *right now* – instead of having to wait for the webmaster of the aggregator to include/unlock my feed.
Also, it’s just arbitrary Gemini links in Antenna – unlike a blog aggregator, where everything is a blog post. So I just saw someone publishing a link titled “A wild twtxt appears” and that’s just a link to their twtxt file.
In many ways, this thing is a bit more like a forum than a blog aggregator. Or maybe you could also call it a “bus”.
Me estaba comiendo una sopa y ¡zas!, ahí estaba, Rafa Nadal. ⌘ Read more****
utf-8 period. Just assume it to be true, there is no other content encoding we should ever support 😅
utf-8 period. Just assume it to be true, there is no other content encoding we should ever support 😅
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set
Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set
Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set
Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set
Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
saltyd 😅
saltyd 😅
I just like to send a proper
Content-Type stating the right encoding to be a good web citizen. That's all. :-)
> Clients (and human readers) just assume a flat threading
> structure by default, read things in order […]
I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn't happen very often. Anyway, just a personal preference. Nothing to really worry.
> The v2 spec requires each reply to re-calculate the hash
> of the specific entry I’m replying to […]
Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I'm probably just not getting your point here in the entire paragraph.)
> Clients should not be expected to track conversations back
> across forking points […]
I agree. It totally depends on the client.
> Clients (and human readers) just assume a flat threading
> structure by default, read things in order \n
I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn't happen very often. Anyway, just a personal preference. Nothing to really worry.
> The v2 spec requires each reply to re-calculate the hash
> of the specific entry I’m replying to \n
Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I'm probably just not getting your point here in the entire paragraph.)
> Clients should not be expected to track conversations back
> across forking points \n
I agree. It totally depends on the client.
Content-Type: text/plain might be not enough, as the HTTP spec defaults to Latin1 or whatever, not UTF-8. So there is a gap or room for incorrect interpretation. I could be wrong, but I understand @anth's comment that he doesn't want to even have a Content-Type header in the first place.I reckon it should be optional, but when deciding to sending one, it should be
Content-Type: text/plain; charset=utf-8. That also helps browsers pick up the right encoding right away without guessing wrong (basically always happens with Firefox here). That aids people who read raw feeds in browsers for debugging or what not. (I sometimes do that to decide if there is enough interesting content to follow the feed at hand.)