> The frame will probably change slightly over time to make them incompatible.
This is probably true.
The rest of your comment is probably not true for most people.
It just depends on how strong your prescription is and how willing the shop/website is to do special orders.
If you are almost blind, then your choice of lenses/frames will be much lower than if you are only slightly blind(most people). Any reputable eyeglass/optician shop should be able to make custom lenses for pretty much any frame. They can't always do the super sleek shades that some people like to wear.
At the time of the SM/CM/CommonMark kerfuffle a decade ago, Gruber was quite explicit that "X Flavored Markdown" was perfectly fine with him— Atwood even includes the relevant podcast snippet:
> As a rule of thumb, if you're processing less than 1000 jobs per day or your jobs are mostly lightweight operations (like sending emails or updating records), you can stick with this solution.
This seems... excessively low? Chancy is on the heavier side and happily does many millions of jobs per day. Postgres has no issue with such low throughput, even on resource constrained systems (think a $5 vps). Maybe they meant 1000 per second?
Forgejo does almost everything Github does around issues that the OP mentioned(I think).
* It doesn't extract the title from the issue on bare linkes, instead the url will become something like: <group>/<repo>#15 Which isn't as nice. So issue #15 in repo tootie/mynotes would look like: tootie/mynotes#15
* It also doesn't do offline sync.
I think that's the only thing it doesn't do. I use Git Touch on iOS and it seems decent enough, you can get to issues and update them, etc.
The bonus is, assuming you run your own Forgejo, or trust whoever runs it for you(say Codeberg), you don't have the MS privacy concerns.
Just like with any other OSS project, you have to convince the upstream developers that your PR is worth merging.
You don't do that by throwing PR's over the wall and then moving on. You do that by being part of the community.
That said sometimes you just don't have the resources to engage another community at the moment, so you push the PR over the wall anyway, assume it won't ever land and act accordingly.
The smaller and less impactful the change, the bigger chance of it landing. I'm always clear with my PR's that I push over the wall though: I probably won't be around to maintain this, feel free to not merge, etc. I also try to thank them for their service to the community and share how their code made my life easier.
We use barman too, but we do hourly and daily restores into different database instances.
So for example our prod db is tootie_prod
We setup another instance the restores from barman every hour and renames the db to tootie_hourly.
We do the same thing daily.
This means we have backup copies of prod that are great for customer service and dev troubleshooting problems. You can make all the changes you want to _daily or _hourly and it will all get erased and updated in a bit.
Since _hourly and _daily are used regularly, this ensures that our backups are working too, since they are now a part of our daily usage to ensure they never break for long.
I ditched for [silverbullet](https://silverbullet.md). MIT licensed, markdown editor with embedded lua scripting. It's a PWA app that works offline and syncs well.
Silverbullet is aptly named but I'd actually wait a month or two because it's going through the transition to V2 which shuffles a few things around.
Other than that it's exactly what it says on the tin, a hacker's digital notebook. While it would take a bit of rolling up your sleeves to make it look as nice as Logseq or Obsidian it's actually closer in form and function to something like org-mode for Emacs (though not quite hitting the mark regarding linking sadly).
It's got some rough edges. I want to sit down and build it so I can add an id to the TOC so I can CSS style it to be floating and submit it upstream.
I'm also having issues with integrating it with Authentik's header proxy auth, keeps directing me to a note with the outpost path as the name. The only guide is for authelia.
I haven't tried putting it behind Authentik or Authelia. They make it known in the Authelia guide what it is they care about being always exposed, vs password protected. Hopefully you get it figured out and you can update the docs so the next person doesn't have the same headache!
I just put it behind a <uuid>.mydomain.com with a domain TLS cert and use the built-in auth.
The wildcard TLS cert keeps the <uuid> from being public in the cert log. The only way you know the URL is if you have access to my DNS queries or have a MITM setup. Plus you still have to know my password.
Good Enough for me.
If I cared a bit more I'd put it behind Tailscale/Nebula/etc instead of having it publicly accessible. Maybe next time I'm bored I'll do that.
This would also apply to farmers when they take out a loan on their land, which they are also unlikely to ever realize, probably for longer period of time then Bezos, et al. I imagine most of rural America, once they figure this out would be very unhappy.
This might be the larger problem with this, since we probably, culturally at least, want more family owned farms and less corporate monster farms. This would not help the current trend away from family owned farms.
You can make a specific exception for loans taken out against the real assets of a business to fund capital improvements of that business. Rules would be similar to when you can deduct business expenses.
This is probably true.
The rest of your comment is probably not true for most people.
It just depends on how strong your prescription is and how willing the shop/website is to do special orders.
If you are almost blind, then your choice of lenses/frames will be much lower than if you are only slightly blind(most people). Any reputable eyeglass/optician shop should be able to make custom lenses for pretty much any frame. They can't always do the super sleek shades that some people like to wear.
reply