\i2028 characters in them and replace with \n π
\\i2028 characters in them and replace with \\n π
So I turned to Go and love it π
So I turned to Go and love it π
I just wanted you to understand something, I respect your opinion that arrow-functions and classes are _maybe_ a good thing, I don't think so personally but that doesn't matter π€£ The truth is I have a strong bias towards readability, and languages that opt for obscure and abrupt/blunt syntax are hard to read, hard to maintain and often even hard to reason about π€
I just wanted you to understand something, I respect your opinion that arrow-functions and classes are _maybe_ a good thing, I don't think so personally but that doesn't matter π€£ The truth is I have a strong bias towards readability, and languages that opt for obscure and abrupt/blunt syntax are hard to read, hard to maintain and often even hard to reason about π€
=> (arrow functions) and all the new so-called "modern" language in Javascript is just well umm crap IHMO π
=> (arrow functions) and all the new so-called "modern" language in Javascript is just well umm crap IHMO π
yarnd and the separate SPA/PWA with a mobile-first design and a more "native"(ish) feel π
The _trick_ will be to reuse as much code between what drives the API and the SSR so changes, improvements or new features can be rolled out to the API, SSR and PWA all at once quite easily... π€
yarnd and the separate SPA/PWA with a mobile-first design and a more "native"(ish) feel π
The _trick_ will be to reuse as much code between what drives the API and the SSR so changes, improvements or new features can be rolled out to the API, SSR and PWA all at once quite easily... π€
I'd like to steer clear of things ike JSX, etc. MithrilJS fortunately lets you just write regular things like:
export default function Login (vnode) {
const { context } = vnode.attrs;
return {
view: function () {
return m("twt-login",
m("form", [
m("input", {"type":"text","placeholder":"Username"}),
...
π
I'd like to steer clear of things ike JSX, etc. MithrilJS fortunately lets you just write regular things like:
export default function Login (vnode) {
const { context } = vnode.attrs;
return {
view: function () {
return m("twt-login",
m("form", [
m("input", {"type":"text","placeholder":"Username"}),
...
π
There are of course things that _can_ be done at the L7 hTTP aching level -- ala CDN(s) / Proxies like Cloudflare, etc, which I run my Pod and my home Infra behind.
If you have ideas around this that don't break some of the "deliberate" design choices, I'm all ears π
There are of course things that _can_ be done at the L7 hTTP aching level -- ala CDN(s) / Proxies like Cloudflare, etc, which I run my Pod and my home Infra behind.
If you have ideas around this that don't break some of the "deliberate" design choices, I'm all ears π
macOS is the only UNIX-like OS that actually has decent accessibility that's just baked in π~
macOS is the only UNIX-like OS that actually has decent accessibility that's just baked in π~
- Deploy Prometheus as your metrics storage and wiry engine
- Deploy Node_Exporter for scraping and exposing CPI, Memory, UI, Network and much more..
- Deploy Grafana for querying and dashboard
- Deploy AlertManager for alerting and notifications
- Deploy Prometheus as your metrics storage and wiry engine
- Deploy Node_Exporter for scraping and exposing CPI, Memory, UI, Network and much more..
- Deploy Grafana for querying and dashboard
- Deploy AlertManager for alerting and notifications
> but I can also see that a user could put links there that arenβt their own. π€
This is my main concern. I don't _think_ we can make this assumption.
The Metadata spec on Links doesn't really allow for anything else besides a
Title and URL anyway, so I'm not sure how we can deal with this except to have some Pod-specific behaviour we attach to the links? π€ (some kind of UI/UX around the user indicating whether the link is in fact theirs and maybe a custom icon?) cc @ullarah
> but I can also see that a user could put links there that arenβt their own. π€
This is my main concern. I don't _think_ we can make this assumption.
The Metadata spec on Links doesn't really allow for anything else besides a
Title and URL anyway, so I'm not sure how we can deal with this except to have some Pod-specific behaviour we attach to the links? π€ (some kind of UI/UX around the user indicating whether the link is in fact theirs and maybe a custom icon?) cc @ullarah
Has anyone else noticed drops in CPU usage on their Pods since enabling
websub? π€
Has anyone else noticed drops in CPU usage on their Pods since enabling
websub? π€
yarnd server via -t/--theme to the directory for the pwa theme and voila. But this is probably a bad idea, so you can largely ignore most of the templating you see there, it would only get used once to render the index.html or / anyway -- the PWA takes over at that point via it's Javascript and Service Worker, etc...
yarnd server via -t/--theme to the directory for the pwa theme and voila. But this is probably a bad idea, so you can largely ignore most of the templating you see there, it would only get used once to render the index.html or / anyway -- the PWA takes over at that point via it's Javascript and Service Worker, etc...
rel=me attribute works and why it's important -- I guess I was missing something though in the back of my mind I didn't make clear...Do we just assume that any User Link a user inputs into their profile or we find on their feed (it's actually part of the Metadata spec) should have a
rel=me attr? π€ Ca we make that assumption?
rel=me attribute works and why it's important -- I guess I was missing something though in the back of my mind I didn't make clear...Do we just assume that any User Link a user inputs into their profile or we find on their feed (it's actually part of the Metadata spec) should have a
rel=me attr? π€ Ca we make that assumption?
> On the face of it itβs a generalisation, but s/People/99.99% of people/ and the statement becomes objectively true.
Yes you are right, but ask yourself "Why? How did this happen?"
I'm old enough to remember the times when everyone had their own server, everyone could run their own website easily and many people did. What changed?
> On the face of it itβs a generalisation, but s/People/99.99% of people/ and the statement becomes objectively true.
Yes you are right, but ask yourself "Why? How did this happen?"
I'm old enough to remember the times when everyone had their own server, everyone could run their own website easily and many people did. What changed?
(#tv3tyba) @<jlj https://twt.nfld.uk/user/jlj> by the fact ...
(#tv3tyba) @<jlj https://twt.nfld.uk/user/jlj> by the fact ...
But this "Federation" thing is a joke. It doesn't mean what anyone thinks it means, it's just the latest hyped up BS in my opinion π -- Just call it what it really is, server to server communications protocols / API / whatever. And for the love of god, why make it so hard?! π€¦ββοΈ
But this "Federation" thing is a joke. It doesn't mean what anyone thinks it means, it's just the latest hyped up BS in my opinion π -- Just call it what it really is, server to server communications protocols / API / whatever. And for the love of god, why make it so hard?! π€¦ββοΈ
It's one thing to build shitty UI/UX which I'm honestly quite terrible at, but it's another to write shit software, over engineering, poor logging, poor documentation, and well fuck, you've just grown so big that no-one gives a fuck π (please correct me if I'm guilty of some of these too! probably am π)
It's one thing to build shitty UI/UX which I'm honestly quite terrible at, but it's another to write shit software, over engineering, poor logging, poor documentation, and well fuck, you've just grown so big that no-one gives a fuck π (please correct me if I'm guilty of some of these too! probably am π)
I honestly can't believe this simple concept of "servers talking to other servers" is so freak'n hard π€·ββοΈ
I honestly can't believe this simple concept of "servers talking to other servers" is so freak'n hard π€·ββοΈ
> A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.
WOW! π³ Who let that patch through?! π
> A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.
WOW! π³ Who let that patch through?! π
> Decentralisation starts with decentering yourself.
> Decentralisation starts with decentering yourself.