Hi, i’m into programming, sexual transmutation and psychedelics!

  • 12 Posts
  • 53 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle

  • Thank you for your answer!

    Yes I’ve considered using Hugo data sources, but handling all events in one single data file is not really a good way to manage data because Hugo can’t programmatically generate content pages from a single data file sadly… Also again, even if I make a script able to do this, I don’t think you can modify content when already created without handling single posts individually.

    I could generate a “list of events” but not individual pages from it and not an RSS feed for posts which I would need for newsletters etc…

    The thing with CSV is that I kinda lost track of where the actual updated data is, so I’m keeping that updated too, yeah I know I’m a mess.

    All the stuff cited is needed for one single job essentially: contacts, newsletter, events… Which is gathering self published and externally published events and sending them to a list of chosen emails + some integration with social medias.

    I’m not a webdev and I thought I could solve this much more easily, but I think doing this correctly would involve using at least an headless CMS + something that is able to grab data from external APIs + some JS framework for building the frontend.

    Or relying on a ready full CMS like Ghost or WordPress + theme and hosting on a VPS, which honestly is what I’m leaning towards…

    I want to avoid JS if possible as I had terrible coding experiences with it, I know some Rust but webdev in rust is not really a good option from what I’ve learned.

    What do you think?








  • Exactly! I don’t see why we have to rely on the old internet infrastructure for a completely differently conceived type of distributing content!

    There’s stuff like ipfs, and I’m sure there are many ways to make self hosting easier…

    We normalize everyone has a modem/router/access point at home: we should normalize everyone having his own server hosted, bitcoin node, ipfs node etc etc…

    And your right, these services have to be super easy to deploy… I think containerization might be helping with this… Think about docker or Nixos… Make a nice GUI and simplify docker even more and you get packages that can run on any distro in any OS, that even a complete noob could spin up! Maybe paired with repos that host most of the self hostable stuff.

    But yeah I think the whole structure might be have to be rethought, from the way we host to the way we can connect to each other… We got to give everyone the possibility to decide which web they want to be part of, and federation definitely allows this!













  • I mean theoretically if you are hosting your own chat server, for example on Matrix, you can easily make all the chats unaccessible from the clients by issuing a command to shutdown your server or simply the chat server service if there’s no content cached locally.

    I think you can do this pretty easily with a raspberry pi by connecting via ssh…

    Just use a shell script that changes the static ip to something else after the command to shutdown the service/wipe out the data (depending on what your goal is) has been issued, or use a vpn or something like that if possible, because anyone issuing the command would need to know your server ip.

    And issuing a command by ssh to a remote server both from smartphone or pc should be as easy that you can actually build a very small app for that, or use some app that creates shortcuts that directly connects and issue custom commands.

    That way you are forced to give people your new ip every time chats become unaccessible/deleted and someone can’t connect back even if wanting to without talking to you, unless you decide you can use the older ip for whatever reason.

    Of course not using your real ip but using some service like a vpn or proxy (or tor?) would be much better here, but i don’t really know how.

    That can give you full power on the chat history and create the said “panic button” for every client involved.