At least that's my hope π€
At least that's my hope π€
> Most tutorials are shallow and don't cover enough depth
I dunno π
> Most tutorials are shallow and don't cover enough depth
I dunno π
That's it, I'm out! π
I have no respect for anyone that starts peddling the "mainstream" narrative. If you don't understand the space you're talking/blogging about, just don't try. "Must tutorials promote misinformation"?! seriously π€¦ββοΈ wtf is this guy smoking?! π
That's it, I'm out! π
I have no respect for anyone that starts peddling the "mainstream" narrative. If you don't understand the space you're talking/blogging about, just don't try. "Must tutorials promote misinformation"?! seriously π€¦ββοΈ wtf is this guy smoking?! π
> Programming is DIFFICULT
No it's not.
> Programming is a difficult topic to break into. It's a complicated field
No it's not. We've just created a HUGE industry around it and made it harder than it has to be.
> Programming is DIFFICULT
No it's not.
> Programming is a difficult topic to break into. It's a complicated field
No it's not. We've just created a HUGE industry around it and made it harder than it has to be.
websub too π
websub too π
This _must_ be what "first world problems" are like π
This _must_ be what "first world problems" are like π
prologic/yarnd:latest -- If you do the later, you _might_ have to docker pull prologic/yarnd first π
prologic/yarnd:latest -- If you do the later, you _might_ have to docker pull prologic/yarnd first π
Actually, if you're good with Javascript and specifically MithrilJS you _could_ help us get the PWA repo/project -- Currently it's just a bit of a skeleton. I also don't like to use NodeJS or NPM as you can tell π over complicates things for me!)
Actually, if you're good with Javascript and specifically MithrilJS you _could_ help us get the PWA repo/project -- Currently it's just a bit of a skeleton. I also don't like to use NodeJS or NPM as you can tell π over complicates things for me!)
> Sadly, I donβt know Go Lang though, so my help is limited to the HTML/JS parts. π
This is fine! π― There's a lot you can contribute to in the default theme -- No real Go experience required really, the Go html/template is not hard to get used to π
There is also a Guide for Template Authors on our Wiki.
> Sadly, I donβt know Go Lang though, so my help is limited to the HTML/JS parts. π
This is fine! π― There's a lot you can contribute to in the default theme -- No real Go experience required really, the Go html/template is not hard to get used to π
There is also a Guide for Template Authors on our Wiki.
Man fuck the bird! π
Man fuck the bird! π
tilde\.team to the "Permitted Image Domains" -- as will I for my pod πExample:
π
tilde\.team to the "Permitted Image Domains" -- as will I for my pod πExample:
π
tilde\\.team to the "Permitted Image Domains" -- as will I for my pod πExample:
π
twtxt.net CPU LoadThe dip back up was me turning it off to fix some bugs π
twtxt.net CPU LoadThe dip back up was me turning it off to fix some bugs π
--fetch-intervalBasically, fetching "subscribed" feeds will be done via WebSub. During the Cache fetch cycle, which is controlled by
--fetch-interval, subscribed feeds are skipped.This has the effect of reducing inbound and outbound load on pods via "polling" and instead pods are notified in _near_ real-time of a feed on a Pod being updated (note this is a
yarnd only feature).
--fetch-intervalBasically, fetching "subscribed" feeds will be done via WebSub. During the Cache fetch cycle, which is controlled by
--fetch-interval, subscribed feeds are skipped.This has the effect of reducing inbound and outbound load on pods via "polling" and instead pods are notified in _near_ real-time of a feed on a Pod being updated (note this is a
yarnd only feature).
No, this will likely never change with the SSR (Server-Side Rendered)
yarnd Web Interface as-is. We _may_ (I've been talking about it for a while now) introduce a "You have X new items, Click here to refresh" banner at the top at some point when @ullarah and I figure out how to build that.
No, this will likely never change with the SSR (Server-Side Rendered)
yarnd Web Interface as-is. We _may_ (I've been talking about it for a while now) introduce a "You have X new items, Click here to refresh" banner at the top at some point when @ullarah and I figure out how to build that.
> what are the visible subtleties for users?
Hopefully none. The _only noticeable difference for cross-pod users in the Yarn.social network is real-time(ish) feed/cache refreshes as User A on Pod X makes a Twt and User B on Pod Y sees it within ~5s or so._~
> what are the visible subtleties for users?
Hopefully none. The _only noticeable difference for cross-pod users in the Yarn.social network is real-time(ish) feed/cache refreshes as User A on Pod X makes a Twt and User B on Pod Y sees it within ~5s or so._~
> DevOps was never intended to make developers do both application and platform operations.
π
> DevOps was never intended to make developers do both application and platform operations.
π
> Enabling them to do so, on a technical level, is the job of the platform operators. This team works in the background, and keeps the platforms and systems humming along nicely. They are the enablers who lay the foundation upon which developers can perform their new duties in a DevOps way.
> Enabling them to do so, on a technical level, is the job of the platform operators. This team works in the background, and keeps the platforms and systems humming along nicely. They are the enablers who lay the foundation upon which developers can perform their new duties in a DevOps way.
> Developers can practice the DevOps way of working by taking on the responsibilities of development and application operations. This allows developers to iterate fast. They can monitor, analyze, plan, and execute code changes in an agile way. It allows them to focus and put all their efforts into building value for the organization via application development.
> Developers can practice the DevOps way of working by taking on the responsibilities of development and application operations. This allows developers to iterate fast. They can monitor, analyze, plan, and execute code changes in an agile way. It allows them to focus and put all their efforts into building value for the organization via application development.