What is n8n?

deleted by creator

There was an update when they disabled a lot of cities for some reason. I remember I could use it in my city, but now it’s not supported…

I haven’t heard about Bimba before, @dafunkkk@lemmy.world recommended here, it seems it has better coverage.

General Transit Feed Specification

It’s called OpenStreetMap, the last character is P, it’s singular.

For reviews there are multiple ongoing projects, none of them is mature enough for everyday use, they have a very few content:

• https://lib.reviews/
• https://mangrove.reviews/

There was a long and very interesting thread about this last year on the osm forum: https://community.openstreetmap.org/t/a-crowd-sourced-review-service-for-openstreetmap/136235/24

For timetables, it’s an existing standard called GTFS, public transport companies should publish their timetables in this format. Transportr is a mature app which supports a lot of companies and cities: https://transportr.app/

CoMaps (a better fork of OrganicMaps) already have a lot of issues about integrating GTFS feeds, e.g. https://codeberg.org/comaps/comaps/issues/1651

The exclamation mark at the beginning is important, without it it doesn’t work

Instance independent link: !Promotion@lemmy.world

Please use this format if you link to communities.

And last, as both pilots died

Saved you a click:

After much debate, the new policy is in effect: Wikipedia authors are not allowed to use LLMs for generating or rewriting article content. There are two primary exceptions, though.

First, editors can use LLMs to suggest refinements to their own writing, as long as the edits are checked for accuracy. In other words, it’s being treated like any other grammar checker or writing assistance tool. The policy says, “ LLMs can go beyond what you ask of them and change the meaning of the text such that it is not supported by the sources cited.”

The second exemption for LLMs is with translation assistance. Editors can use AI tools for the first pass at translating text, but they still need to be fluent enough in both languages to catch errors. As with regular writing refinements, anyone using LLMs also has to check that incorrect information hasn’t been injected.

That whatever happens the problem is always systemd. Chain of events:

• voters vote for corrupt politician
• big tech compaies bribe said politician to have shitty law
• freedesktop requests systemd for backend to comply with said law
• systemd just adds the field to the userdb

Who is to blame for all of this? Poettering who else…

Basically that’s the other option. But considering a lot of the maintainers live there, it’s just easier to comply with the stupid law until it’s reversed.

So it’s the legistlation’s fault again, why aren’t you mad at them, why only systemd? In other jurisdictions you don’t have to use this field. And I don’t see anything in the PR about the verifability of the date. It’s just an optional number it stores in a db, offline.

Programmers have to become lawyers now?

Also a lot other projects has a birthday field, e.g. last time I worked with was LDAP: https://ldapwiki.com/wiki/Wiki.jsp?page=Birthdate I guess it’s there since the 90s.

Ok, who decides which law is clown and which isn’t? You? Or Sam Altman? I guess he has a different idea what laws he wants to follow. See, it’s a slippery slope you recommend.

Change your clown laws, and don’t bully projects who just wants linux to become viable alternative to common people. Don’t make perfect enemy of good.

No they haven’t, they added a field where a user can store their birthday, as required by law in parts of the US.

Or do you recommend them to ignore the law, and jeopardize the whole project? Do you want linux get banned in California? You are mad at the wrong people

Hdparm: https://wiki.archlinux.org/title/Hdparm

E.g:

hdparm -B 127 /dev/sda

I know it’s archwiki, but it’s the same on every distro

From the docs:

The Standard Debian Kernel (selectable) can be used for ZFS. However, since ZFS kernel modules are not installed in the Debian kernel by default, they must be built by the ZFS plugin when it is installed. While this process works, building the modules is a long process that requires continuous access to online repos. Accordingly, the potential for a build error exists. For this reason, while the Standard Kernel is very usable for ZFS, it is not ideal.

I can pay with my degoogled rooted phone with official lineageos, with microG with curve pay: https://play.google.com/store/apps/details?id=com.imaginecurve.curve.prd

I guess it’s not available in all countries, and I had to do not privacy friendly KYC, scan my government ID.

ZFS is in the omv extras repo: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs

As it’s just plain debian under the hood you can use any basic debian stuff, e.g. I use zfs-auto-snapshot from apt, and the zfs plugin can list and manage the snapshots perfectly.

It’s not in there by default, you have to install the omv extras plugin, from there you can install zfs: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs