cyclohexane

joined 3 years ago
MODERATOR OF
[–] [email protected] 6 points 7 months ago (8 children)

I never really quite understood IPFS and why it gets used where I see it today. What problem is it solving?

[–] [email protected] 1 points 9 months ago
[–] [email protected] 14 points 10 months ago* (last edited 9 months ago) (2 children)

I know someone who's literally making that right now. Remind me in a week, I'll send you the link. He'll probably be done by then.

Edit: donetick.com

[–] [email protected] 6 points 1 year ago

For XMPP, have you looked into using snikket? It does most things you'd want out of the box without having to setup extensions yourself.

[–] [email protected] 1 points 1 year ago

I got into ocaml recently. I love it. I honestly don't see issues with the syntax, maybe because I haven't used it enough.

[–] [email protected] 14 points 1 year ago (2 children)

Here is a docker compose: https://snikket.org/service/resources/docker-compose.yml

You only two configuration options in the config file: domain and email.

[–] [email protected] 2 points 1 year ago (1 children)

I've been wanting to do this exact thing. I already have wireguard setup. Please update us if you do this.

[–] [email protected] 13 points 1 year ago

This makes matrix even less attractive to me lol. But you're right, that's a very good point.

[–] [email protected] 2 points 1 year ago (1 children)

cumbersome to parse

Parsers have already existed for so long in every major language. Why need to worry about parsing?

And why need to worry about transports working differently if they achieve the same thing? They seem similarly convenient if I understood what you said correctly

[–] [email protected] 3 points 1 year ago (7 children)

Why is JSON better than XML? It's more modern, sure, but from technical perspective it is not objectively better right? Not something worth switching protocols for.

You mention XMPP has transports as opposed to Matrix bridges. I thought they give you roughly the same outcome. What's the difference?

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Any examples other than ocaml? From my understanding, ocaml's type strength may only be found in a couple other languages. Haskell, scala, and maybe Rust. Any others?

[–] [email protected] 18 points 1 year ago* (last edited 1 year ago)

Comparing cost to AWS Aurora is unfair. Give us the self host price, and compare to that.

Also, they should have tried Scylla or Cassandra. It's very scalable and handles a lot of writes.

 

why?

Because bash feels clunky to write and work with for anything non-trivial, especially compared to other scripting languages.

Why not another scripting language (no compile necessary)?

Because bash and sh are installed nearly everywhere. Any other scripting language means the user is required to have that installed, and that is far less likely to be the case.

If I could write my scripts in a nice syntax, but be sure my users will be able to use it effortlessly by distributing to them compiled versions, then that would make both of our lives easier!

Thoughts? Are there any languges that do this?

 

Hello all,

I am looking for suggestions for libraries to use on my project. It is a personal project, so I'm happy to experiment with lesser known or new libraries.

The application will be a mix of content-focus and client side interactivity (think to-do list with server side persistence).

My current approach is as follows:

  • Server side rendering on NodeJS with a template engine, complemented with client side scripting for interactivity (mostly vanilla JS)
  • Use liquidJS as template engine (any alternatives?)
  • Use fastify as the HTTP / Backend server with @fastify/view plugin for serving liquidJS (and other template engines)
  • use vanilla JS scripts for interactivity and DOM manipulation
  • use vanilla-SWR for data fetching, mutation and persistence on server side. Link: droyson/vanilla-swr

Any other suggestions?

 

React (and Vue, et al) was built with client side rendering in mind. It just does not seem to fit the server side rendering pattern.

What are the use cases? From my perspective, if your app is a rich web app with a lot of interactivity, you probably want CSR and don't benefit much from SSR.

If you have a content-centric site, or a site with some interactivity but not much, you want a static site generator, or SSR. But in that case, a template engine with some smaller client side libraries (jQuery or AlpineJS or idk what all is out there).

Using React SSR for all of these seems like the wrong tool. What am I missing?

 

It seems that around July 15th, the repo for Barinsta, the FOSS instagram frontend that was abandoned about 1-2 years ago has been taken down.

The repo was hosted on codeberg, after the original author took the github repo down. The second maintainer moved the repo to codeberg, but it seems little was done to maintain it. The second maintainer seems to have deleted previous blog posts about barinsta as well.

I have the repo backed up locally (hence why I noticed), but it does not work in its current state.

Its probably not worth using instagram anyways

 

I've been using geometric weather, but wondering if people have other options for weather apps.

Widgets aren't necessary

 

I've been using geometric weather, but wondering if people have other options for weather apps.

Widgets aren't necessary

 

Binance.US ceased USD deposits, and became a crypto-only exchange

Are there any ways to buy crypto in the US, with the ability to withdraw easily, without paying fees? Or at least something with cheap fees?

I've looked into BISQ, but I am afraid of law enforcement retaliation. I'm not doing anything illegal, but I read stories of people getting arrested for not verifying the identity of who they sold to. Don't want that to be me.

 

Hello friends,

I am looking for a self-hosted task / to-do list app that supports:

  • syncing across devices, preferably self-hosted
  • sort items myself rather than by deadline or built-in priority features, and preserve that order when syncing
  • allow defining arbitrary custom attributes

Some really nice to haves but not absolutely necessary features:

  • treat custom attributes as first-class. i.e. allow showing those attributes on the task-list view, without having to view all details to see it. Or be able to filter or by the attribute or sort by it.
  • allow custom logic for sorting
  • just scriptable features in general would be nice

I have been thinking of making my own, but wanted to see if this exists first.

 

One of the things I like the fediverse is the oppposition to unhealthy social media use. I think infinite scrolling is one of the worst things about mainstream social media. Even when youre consciously against it, it is very hard not to forget and get consumed by the infinite scrolling.

My proposal is that front-ends should default (or at least provide the option) to a paginated interface. You get to the bottom and have to click a "Next" button. It acts as sort of a wake up call to your scroll-numbed mind. It is also a much more ergonomic interface anyways, and more lightweight on resources.

I strongly believe that, if presented the option, most people would prefer pagination over infinite scroll. It seems corporations forced infinite scroll on us for maximum time wasted.

 

And I guess this question is two parts: 1. Regarding the current lemmy implementation, and 2. The activityPub protocol in general

 

what is better for single user instance, or maybe something small like under 10 users (no communities)? which is lighter on resources? how much storage should I allocate?

any alternatives to lemmy and kbin that are still somewhat similar?

 

anonymity and privacy seem to come at odds with a social platform's ability to moderate content and control spam.

If users have sufficient privacy and anonymity, then they can simply use another identity to come back, or use multiple identities.

Are there ways around this? It seems that any method of ensuring that a banned user is kept off the platform would necessitate the platform knowing information about the user and their identity

view more: ‹ prev next ›