A tree can be seen as a formal language. Look into L-systems.

If you generalize what a symbol is (the rgb value of a pixel) you can write a grammar that ends producing a list of pixels. You can then place it in a 2d matrix and you have an image.

I guess a better approach would be wave function colapse, but seems to me like it could be formally described as a grammar (CS or CF, dunno, would have to look into it)

Didn’t you go into Turing machines and the Halting problem from that?

That was my intro into computation: regex, automatas, state machines, stack state machines, formal languages, grammars, Turing machines, Hanting Problem, P NP.

Python for excel, grafana for Bi?

I guess depends of your use case.

Refresh speed, font rendering, integrated features like multiplexing, theming…

1.- That would make Lemmy servers ultra unsafe to host. Server owners would not be able to moderate content hosted in their machine. It would make a good distributed solution, but not a federated one.

Maybe we’d prefer a centralized organization, with distributed resources. But seeing the defederation drama every week, it doesn’t look the path anyone wants to follow.

It’s a solution, but I don’t like it.

1.- It’s less resilient. If (more like when) one server goes down it could take the only community in a topic with it.

2.- If the moderators for the community of your interest are kind of dickwads, or absent, or malicious, you have no alternative.

3.- Federation can create weird problems. If your account instance is not the community’s one, you could be effectively banned, without doing anything wrong.

4.- Creates a perverse incentive for using the biggest instance you can for both creating communities and users. Some of the bigger Lemmy instances already are under heavy load and having problems to stay online. Imagine if we discourage using small instances.

Some mechanisms to “merge” communities across servers would be cool addition. Every Android community in every server that still federates with each other lists every post in all of them. Moderators moderate the posts in their instance. Link repetition is the same as inside of one single community. If one of the composing communities moderator team doesn’t does it’s part it could be expelled from the composite. Like a soft de-federation.

Just rambling. It’s a complex problem.

deleted by creator

It’s a solution, but I don’t like it.

1.- It’s less resilient. If (more like when) one server goes down it could take the only community in a topic with it. 2.- If the moderators for the community of your interest are kind of dickwads, or absent, or malicious, you have no alternative. 3.- Federation can create weird problems. If your account instance is not the community’s one, you could be effectively banned, without doing anything wrong. 4.- Creates a perverse incentive for using the biggest instance you can for both creating communities and users. Some of the bigger Lemmy instances already are under heavy load and having problems to stay online. Imagine if we discourage using small instances.

Some mechanisms to “merge” communities across servers would be cool addition. Every Android community in every server that still federates with each other lists every post in all of them. Moderators moderate the posts in their instance. Link repetition is the same as inside of one single community. If one of the composing communities moderator team doesn’t does it’s part it could be expelled from the composite. Like a soft de-federation.

Just rambling. It’s a complex problem.

Multiple communities with the same theme in diverse servers mean lots of repeated information in my home page.

I find hard to find new niche communities. All is all, the common denominator. My home is what I already have subscribed. Local instance communities are there. But I don know a good way to get offended content from communities outside of those categories.

I know it’s a joke, but it’s an old one and it doesn’t make a lot of sense in this day and age.

Why are you comparing null to numbers? Shouldn’t you be assuring your values are valid first? Why are you using the “cast everything to the type you see fit and compare” operator?

Other languages would simply fail. Once more JavaScript greatest sin is not throwing an exception when you ask it to do things that don’t make sense.