prologic

twtxt.net

No description provided.

Recent twts from prologic
In-reply-to » I forget who it was but someone here pushed back on me when I said there were a bunch of Nazi instances on mastodon, but it's true. They were one of the earliest adopters and they're still a big nuisance over there. If yarn ever becomes super popular watch out!

@abucci@anthony.buc.ci I wonder though whether that’ll even be a problem for Yarn? 🤔 We already make it quite hard (impossible?) to prop one’s position up over another, or become “popular”, or whatever. Anything else you think we could do more of to slow things down, and keep possible abuses of the ecosystem down? 🤔 – I’ve always been of the opinion that well your opinion is just as valid as mine and you have a right to it, so I’m very much against things like popularism (as seen on the bird site) and censoring (as seen on the blue book site) and other sorts of silly shit™ 🤣 – If you don’t like me or what I have to say, mute me, unfollow me, but don’t be an ass 😆

⤋ Read More
In-reply-to » @prologic you know, it doesn't seem to be widely appreciated but the bad segments of the right wing have always been very tech savvy. They're usually one of the first big groups on the scene when new technology arises, and they're often some of the last holdouts too. Like some kind of fungus.

@abucci@anthony.buc.ci When you say “right wing”, can you clarify what you mean? 🤔 (just in case our language is not the same somehow…) – I never understood these (silly IMO) terms “left wing” vs. “right wing” and once day I set out to try to “educate” myself on the matter and read up on the political compass – Took the rest too. Seems like it was well worth the effort and these guys appears to do good research on the subject(s) (economic positions and social positions).

⤋ Read More
In-reply-to » @lyse @prologic @mckinley That website becomes porn eventually. Given the content, and the fact that "reich" is in the URL, I believe this is probably a very bad (e.g., neo-Nazi) person and is best avoided. I know it seems cute but this is what you see when you visit forums like 4chan--same aesthetic, same surprise porn, same sneaky plausibly deniable Nazi references.

@abucci@anthony.buc.ci Oh it got really bad IMO. I left the community as a result of the disgusting shit I was seeing out of the bitreich.org folks 🤯

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net Yeah I’m kind of thinking that the JSON API / REST API + SSR Templating calls a “middle” layer. In other words, abstract out the actual data handling and logic with interfaces that can be used for a real response directly (content negotiated) or rendered with some HTML templates.

⤋ Read More
In-reply-to » @lyse @prologic @mckinley That website becomes porn eventually. Given the content, and the fact that "reich" is in the URL, I believe this is probably a very bad (e.g., neo-Nazi) person and is best avoided. I know it seems cute but this is what you see when you visit forums like 4chan--same aesthetic, same surprise porn, same sneaky plausibly deniable Nazi references.

@abucci@anthony.buc.ci You should see my outrage at the Gopher mailing list some years ago regarding some of the “asshole” attitude of these guys 😅

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net So, we’ll build a few data models that represents data we need to store and mutate and some logic to fetch that data and perform actions on it. Then an API layer will use that and serialise as either a JSON RPC API or JSON Rest API. Another layer will call the same code to fill out template contexts and render templates. Does this sound about right? 🤔

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net Yup 👌 I’m going to experiment on someyhing a bit contrived add aee what pattern I can come up with 🤞

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net Yeah I have a few ideas for how to structure this, but I’ve never seen anyone do it, probably because these days everyone just does this React shit™ 🤣 Gotta give this a try though… 🤔

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net Can we still maintain a nice SSR (Server-side Rendered) UI though? This is something I never quite managed to “get right”, it would be nice to not have any Javascript (or ever little) for the UI but to still power the SSR and API with the same data structures (which is what I think you’re talking about?)

⤋ Read More
In-reply-to » https://github.com/driusan/bug <-- cool way to handle/manage project issues/bugs

@justamoment@twtxt.net I think, at least that’s the idea, and it allegedly doesn’t pollute the actual repo with unrelated files (I don’t think) – I still haven’t been able to get it to work locally though so hoping someone will answer my comment on the issue. But yeah depending on how git-bug evolves over time we could just integrate with it “somehow”

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net I guess we start with:

  • An interface to manager repos
  • Support for git push over SSH with key management

What already works (mostly):

  • Hosting
  • Cloning via git clone over HTTP/SSH

What still needs consideration/experimentation:

  • Code reviews
  • Issue tracking

⤋ Read More
In-reply-to » Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress -- Another good blog post on working with Git patches via Email as well as applying them. -- The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - -- Hmmm 🤔 -- I think we can do better than this...

@justamoment@twtxt.net Yup pretty much. That’s what I’m thinking here… So the Web UI we build need to support IndieAuth I think (well it would be nice if it did I think) so we can manage repos… Repo descriptions can be stored/retrieved from .git/description – Likewise we can probably do something with SSH keys like storing the keys permitted for “write” access in .git/authorized_keys. What else? Hmmm 🤔

⤋ Read More

Speaking of Git hosting / forges / thingies… I just realised that the way in which sr.ht manages patches is actually very similar to what I had in mind, at least conceptually. And… it looks like they somehow have figured out a way to represent whether or not the patches were applied in this nifty Web UI

Download

– If you follow the link to a proposed patch for example you also get another nice interface explaining how to deal with the patch

Download

– As well as a nifty (if you expand it out) little CLI snippet you can paste into your Terminal like:

$ curl -s https://lists.sr.ht/~migadu/alps-devel/patches/36196/mbox | git am -3

Neat! 👌 Some good inspiration to draw from there… (even if I still don’t like the idea of using Email).

⤋ Read More