Hi, I am a building a platform with the goal of supporting apps like this, and I would be interested to develop a plugin for your use-case as an experiment (no fee).

I am working alone on this and this is not my first priority, so I cannot make any guarantees about the timeline, or the scope of the plugin. But, if you are interested we can have a chat on matrix.

The project is not open source yet, but I am planning on doing so once (a) I figure out how to properly apply licensing, and (b) remove any potentially critical information (credentials) from the repository.

I have been using for the past month. I am not a power user, I mostly use it when I need to access libgen. Previously, I was using nordvpn. I feel proton is faster both when connecting to a server but also the connection is faster/more reliable. For example, if I forget to turn it off, I can watch a yt video without any issues.

Is that adhd? That’s definitely adhd!!!

I would add spaghetti in the middle

They also scare the crap out of my dog, and cause a lot of accidents. Though, they can be beautiful…

Lemmy’s user base is pretty interesting, you will find interesting discussions in pretty much most communities. However, if don’t find something interesting, don’t be afraid to start a discussion on your own. Coming from Reddit I used to be afraid of the harassment, but Lemmy is a safer space ❤️

Some general pointers:

1. Beehaw is a good place to look for interesting discussions
2. If you find an interesting comment, take a look at the author’s profile, chance is they have more interesting stuff for you to find
3. Filter by subscribed and hot/active
4. Look for opinion articles

Is this what autism feels like?

Sometimes yes, a lot of us feel isolated, struggle with socialization and connecting with others. Othen it helps to find other ND people, they are just as interested in whatever niche topic you are thinking about.

PS Yesterday, I started a post on AskLemmy after pondering about how technology and science is changing at a faster pace than people (mostly professionals) can adapt.

Yes, I always review the code, just avoid nitpicking the hell out of it.

Not really, we are a small team and we generally trust each other. Sure there are things that could have been better, but it’s not bad either.

I am definitely guilt for that, but I find this approach really productive. We use small bug fixes as an opportunity to improve the code quality. Bigger PRs often introduce new features and take a lot of time, you know the other person is tired and needs to move on, so we focus on the bigger picture, requesting changes only if there is a bug or an important structural issue.

That sounds a bit misleading, the server implementation is FOSS too, at any time someone could setup their own instance.

There is Alovoa, it’s open source, still has a small user base, but you don’t have anything to lose…

Here is a list of note-taking apps:

https://github.com/tehtbl/awesome-note-taking

By the way, I am building my own Journaling system, it’s still early stages and I am looking for ideas!

Me neither buddy, me neither…

Falsehoods About Time: … Time always moves forwards.

I had to learn this the hard way… I was working at a platform that pulled measurements from sensors. The sensors did not declare the timezone for the timestamps of the measurement and the platform broke down twice after daylight saving. The first time there were duplicated records which caused conflicts and the second one we weren’t handling impossible timestamps.

So that’s the legal equivalent of the guy committing 10k changes the day before leaving the company…

Reminds me when dayjs decided to change the duration of a month during a random bugfix. I had to update so many tests…

Now I am going to share a horror story: Multitimezone Operational Calendars

Social interactions are totally draining for me, but I cannot understand a person until I had a face to face communication with them.

No, they are using an ORM.

A good place to start is the owasp cheat sheet. They provide up-to-date, high value information about software security, I wish there was a resource like this when I started learning about security.

Even though, I have a decent background in software security, it’s hard to decide on an encryption schema that’s both safe and easy to use. My goal is to increase the number of components an attacker has to compromise in order to get access to the data.

twelve factor app

Great resource!

Write database migrations in both directions so people can downgrade on failures.

Good point. Personally, I take backups before upgrades and restore if anything goes wrong. But, I understand how downgrading sometimes is just easier.

I have trouble coming up with a migration procedure that makes sense to me. I have the following in mind:

1. Provide init scripts that produce a schema that matches beginning state of the current major.
2. Provide major to major migration scripts.
3. For every major, provide minor to minor migration scripts.
4. Schema changes require at least a minor release.

Make it possible to configure your system via ENV variables, ENV files and config files.

I am bit worried about this one, environment variables can be a security concern. Specifically, I am not sure if I should allow providing secrets (like db connection strings) through environment variables. I am inclined to let people do what they want to, but issue a warning.

Make it possible to disable authentication to add Authelia or LDAP through the webserver. Make clear that this is only to be used for external authentication.

I am considering adding support for oauth through keycloak. My assumption is that if you are going to host your own LDAP, you can probably configure keycloak too. Do you think that makes sense?

Make it possible to run multiple parallel instances of your software without affecting the database consistency, e.g. for high availability or horizontal scaling.

Ideally, an instance shouldn’t be big enough to need it. I know, famous last words, but in my case I think it’s a bad problem to have. I am going out of scope, but I am wondering where is the line between discouraging large scale deployments and designing something pre-destined to obscurity.

Telemetry

Not even on my radar, thanks for bringing it into my attention 🙏

Great point, I always consider dependencies from a security perspective, but for management/setup sometimes I am like “the devops are going to figure it out”…

To clarify, would an example be supporting sqlite, so people won’t have to deploy postgres unless they need to?

My plan is to offer a docker-compose configuration people can tinker with. I had the mindset that whatever happens in the container stays in the container, but your comment made me realize I should be mindful of other installation methods. Thanks 🙏