That’s unfortunate - TinyLoRa has never really been suited to use, but more as a crude proof-of-concept.
That said, I can see where you are coming from
A lot of the replies here seem really gatekeepery for people who are just looking for a simple way to make use of LoRa with a really simple library.
LoRaWAN is in fact a rather complex protocol, and IMHO arguably has some design mistakes - it’s intended to support some rather complex situations which rarely occur in practice, and in order to do that pays some penalty in not only software complexity, but in the cost of the actual traffic transmitted, too.
But it’s equally important not to confuse LoRaWAN with LoRa - if you want something simple and barebones, LoRaWan might not be what you want to use.
Low memory devices were likely ill-chosen to begin with - this has been pointed out for quite a while, but some still insist on buying more of them. That said, I suspect that with real care (and dropping Arduino compatibility) optimal code could get the job done. But it’s unlikely to be a productive investment of the time of someone capable of doing so.
It’s clear where this is coming from, though it’s not clear if it actually matches the needs of the community.
Regardless though, the major mistake at present is that it hasn’t been coded with safeguards that will make it degrade gracefully when faced with misbehaving and misconfigured nodes - something that it is unavoidably going to face.
Most basically, the stack needs to have downlink rate limiting, so that regardless if by intention, under-implementation of LoRaWan on the node, misconfiguration, or even intentional DDoS-type abuse, the network refuses to transmit an excessive number of packets down towards a node.