At least one of the advantages in targeting React is being able to leverage the vast existing library of React components to quickly expose new and advanced functionality to the Reflex app.
Thanks for the feedback. I work on Reflex and in a recent release, the team added a template and CLI for creating third-party components and publishing them to PyPI.
Since then, I've built a few authentication libraries that might be of interest:
The problem with having auth built in is that it's been hard to find a solution that actually works for a majority of use cases. That said, as these auth libraries get more popular and refined, they might be moved into the reflex-dev organization as officially maintained components, or even integrated with the core framework.
However, I am concerned that the @reflex_local_auth.require_login decorator [1] merely redirects users to the login page.
> Although this seems to protect the content, it is still publicly accessible when viewing the source code for the page! This should be considered a mechanism to redirect users to the login page, NOT a way to protect data.
So, I have to put an if-else condition on the State data associated with each protected page, in addition to this decorator. The reasonable way to do it would be for the decorator to actually prevent any data load at all before redirecting. This will prevent a lot of mistakes, besides removing boiler plate.
I've recently deployed this trick on my company's confluence instance (with an HTML macro) to create a "poor man's" link shortener that allows me to change the link target after the fact.
Also recently deployed it as a very simple server side denounce: when the client first accesses page X a long running operation is dispatched. Subsequent requests for the same resource before it's done processing return a plain HTML response that says "Still thinking about it" and meta refresh after 1 second.
At the company I work at currently, we're in the process of replacing all Linux-based machines with OpenSUSE... not for any technical merit or reason that I've heard other than, "we should all use the same thing for everything".
So another 20k+ SUSE installations coming from that alone this year.
Market share by mandate; some sales guy at SUSE probably got a big bonus.
For 20k+ users they probably give you more insider info. Did you ask if SLE and Leap are going to continue to be made? Or did you go directly for ALP or MicroOS?
I haven't been privy to those kinds of conversations. Mostly we are replacing Ubuntu LTS and older CentOS with OpenSUSE Leap for servers. Some developers are deploying Tumbleweed as a rolling release.
I'm trying to give it chance, change being hard and all.
The other comments here from long time users are giving me some hope that we may find tangible benefits, especially w.r.t btrfs and snapshots.
FWIW IMNHO "use the same thing for everything" is a technical reason ...
Nothing like logging in to a server running some old legacy app and realizing it's running some bespoke version of ancient Oracle Linux (or Gentoo or whatever you happen to be unfamiliar with, but some previous hire thought was the bomb) - and try to untangle what issues stem from the distro, and which belong to the application...
In the last month, I’ve been experimentally replacing my use of Trello, stickies, and todo lists with a phpBB instance.
So far I’m the only user, but it’s a surprisingly nice system for keeping track of notes and regular status updates on my projects. And when I need to collaborate with someone, the permission system is quite nice as well.
The fact that it’s free, mature, and relatively easy to install and maintain are what led me to give it a try.
I have plans to eventually write a kanban view and scheduled post plug-ins to make it a bit better project tracker.
I have been doing this since 2015 and, I agree! It is amazing how useful it is. I've tried various note taking apps, project management systems, etc and I keep coming back to this system of keeping notes and staying organized. The best part for me is I always have access to my notes even if I don't have my main device with me.
Do you think you'd feel comfortable sharing some images with redacted information to show how you are using it? Would love to peek into how a forum tool is being used in a non conventional way. Thanks!
Just a quick late note of appreciation. My friends and I have been trying to have some community way of each of us sharing progress on hobbies and side projects. After looking at this it was a smack-forehead moment. Setting up a private discourse to keep track of things as we go along :)
It may well be similar to the situation in the UK, where - while it is not really within the terms of a licence for (for example) unlicensed 446MHz radios, no-one is going to do anything about it.
In the US the FCC will go after you for running half a watt over your power limit. In the UK, Ofcom literally cannot be paid to take an interest on what happens on amateur or ISM bands, and will only get involved if you're making a nuisance of yourself on commercially licensed frequencies.
Previously I used Nextcloud News and enjoyed it, but recent versions require 64-bit PHP [1], which I didn’t have on the Raspberry Pi. Never did figure out why this requirement was imposed just for the News app.
As a recent returnee to the world of RSS feeds, I’ve been enjoying the miniflux client [1] self hosted with docker-compose. Fast, cross-platform, not fancy.
I have been using osmo feed [0]. Rather than self hosting, it uses GitHub actions. I have my own usename.github.io/to-read linked to it, to access it from anywhere. So far I have liked this approach.
1. Synced feeds, read/unread status, and consistent UI across all devices
2. Hosted feed reader for friends and family.
The author mentions the friction they imagine their friends or family would have using RSS feeds, so hosting the reader for them can reduce that friction and bootstrap cost (everyone already has a browser). Then they could always export their feeds and move to a different solution later.
