No they don’t. That is an opt-in setting that a user can put on their profile to only have logged in users see their content. The default is open viewing.
Ah ok, I don't use bsky much but I got linked there on another HN post. I could see that but when I clicked on replies I got a login prompt just like twitter.
I normally use nostr more because that really is decentralised. Also mastodon. Though I don't like the short message twitter style blogs anyway. So Lemmy really is my favourite (too bad about all the tankies though)
I have a couple that are honest sub 5mb apps. Some of my favorite apps on my phone. Limited featureset that does what it says on the tin. Loads instantly. Hardly uses battery at all. I wish everything was like this.
You cease to be a "fringe crank" when the Vice President of the most powerful nation on the planet has directly referenced you. Being a verifiable direct influence on the richest people currently calling the shots and guiding the direction of reality also removes your "fringe crank" denomination.
Otherwise, Peter Thiel's company has billions of dollars of contracts with the government in completely non-trivial spaces (mass surveillance and military).
Calling one of the richest, most connected-with-power individuals on the planet a "fringe crank" is somewhat ridiculous.
Our company has been using zoho since we started almost a decade ago. It's been rock solid. We use their CRM & Accounting (Books) as well and everything's integrated nicely. Also has an easy to use API to glue arbitrary things together & scrape emails, etc.
If you have a user flow that requires interaction, hits an API that returns instantly, and then changes something fundamentally, it is better UX to make the user wait for a couple seconds with an animation and then some success state indication. If it all happens at once it can be a bit jarring or confusing.
I don't really understand the appeal. I guess if you're primarily a python programmer it's nice to be able to write the front and back in the same language; potentially sharing code for utilities , etc. Just like using node with a JS front-end... But, the front-end is always a JS frontend, I don't see how layering extra abstractions on top of it could ever result in better performance; and also, I imagine you can't do everything you can do with JS with this tool as well; why take power away?
Your example code @ https://lona-web.org/#what-is-lona imperatively builds a web-page... you still are writing the same amount of code but you're adding another step. When you write the html it's declared and it's done, there is no extra processing like there is when you write a program to produce another program.
This is cool though, clearly it has some real utility for you, I'm curious though; how does it improve the web development experience? How does it make you more efficient?
Thats a very good question! I am a full stack developer and have no problems writing big applications in python, javascript, html, css and juggling multiple frameworks at once. Also i am very experienced with async code and asyncio. But at work i am the only one with this skill set. The most of the other developers only have application specific domain knowledge and can write python code.
One of our biggest internal projects at work is our web based accounting system. If there is a bug that is not a technical issue but an accounting issue, i cant do anything (i have no clue about accounting). If the bug touches multiple layers of the software (backend and frontend) our application developers are sometimes busy for days. Thats slows down development and is expensive.
With Lona, and the Lona widgets i created for our accounting system, i can give them a very simple, abstract and pythonic API for common tasks like "show an table and then update it", "show a progressbar with an abort button" or "show a popup with 3 buttons".
The code is more readable for everyone involved, and the application developers can now solve most of their problems on their own.
Performance: Yes you are right, you have to sacrifice performance for this approach to web, but performance is in this kind of applications no problem. CPU time is cheap these days, developer time is expensive. We are a small team.
