Librewolf is, to me, the way better alternative as this is really in the FOSS mindset : a tool for everyone to use and by anyone to contribute. Seeing their plateform alone (Lemmy/Matrix/Codeberg, they also have a reddit community it seems) you can already see this is an other world than Waterwolf's bluesky/reddit/github. To be fair I can understand the SNS part but the github is a big redflag to me.

As usual I can see people that are very probably sincere in their goals not realizing the way they are going will lead to the usual enshitification: company focus, brave dependency, etc.

I note that Waterfox seems to legally originate from UK and it is refreshing to have an ecosystem that is not centralized in 1 country : for the sake of everyone it is better not to rely to much on 1 legislator (see age verification for instance).

  Input data to the clipboard
  Access your data for sites in the dropboxapi.com domain
  Access your data for www.google.com
  Access your data for www.googleapis.com
  Access your data for accounts.google.com
  Access your data for graph.microsoft.com
  Access your data for login.microsoftonline.com

  Display notifications to you
  Access browser tabs
  Access browser activity during navigation
  Access your data for all websites

Talking about unknown code there is a lot of work to be done on reproducible build as anything touching web has nearly nothing about it.

The good part is that if you have better solution you actually can suggest a PR and/or implement it for yourself.

The bot verification is not specific to Forgejo/Codeberg a lot of Foss project and organization use this method to avoid unnecessary bot traffic. I understand the issue you have with it but the problem is way larger than codeberg here.

Also about the login with GitHub button would be immensely annoying for the community : you came from GitHub and you might think that your experience is more important but as this is community driven and not a business the people actually creating and using the software don't need nor want to prioritize such button but leave the option for those who wants it, which is very nice of them. Eventually if the majority start thinking a GitHub login is preferred an issue can be created and a change made in that direction.

I like the extensive benchmark from hardkernel, the only issue is that any ARM-based product is very tricky to boot and the only savior is armbian.

Aside from the bitter words against Github (and I read comments here forgetting about the very real consequences with people lives like collaboration with ICE), using codeberg is using Forgejo : those technology are by us and for us. Unlike Github we can run our own if necessary and all the technology (actions and such) can be improved and be shared between us.

An other benefit of Forgejo/Codeberg is the absence of pushing for paying more, Github is not free and lives of users going to Azure/Gemini or other Mircrosoft services. There are many parts that are made/changed to nudge people into paying more and more and be vendor-locked.

I like my life to have the fewest dark patterns as possible and Coderberg is extremely helpful.

Digging a little bit I found that git-annex is coded in haskell (not a fan) and seems to be 50% slower (expected from haskell but also only 1 source so far so not really reliable).

I don't see appeal of the complexity of the commands, they probably serve a purpose. Once you opened a .gitattributes from git-LFS you pretty much know all you need and you barely need any commands anymore.

Also I like how setting up a .gitattribute makes everything transparent the same way .gitignore works. I don't see any equivalent with git-annex.

Lastly any "tutorial" or guide about git-annex that won't show me an equivalent of 'git lfs ls-files' will definitely not appeal to me. I'm a big user of 'git status' and 'git lfs ls-files' to check/re-check everything.

  pub const SinglyLinkedList(comptime T: type) type {
    return struct {
      first: ?*Node = null,

      pub const Node = struct {
        next: ?*Node = null,
      };

      const Self = @This(); 
      pub fn data(self: Self) *T {
        return @fieldParentPtr("node", self);
      }
  };

"Partial clones Commutation makes it possible to clone only a small subset of a repository: indeed, one can only apply the changes related to that subset. Working on a partial clone produces changes that can readily be sent to the large repository. "

OK, now I am interested.

It is scary that someone can say it is "encrypting" a private key by applying a simple XOR.

Also :

"File-Based Index: We track file hashes in a small JSON index instead of re-hashing everything on every commit or switch. This makes commits and merges faster because Evo only re-hashes files if it notices a changed modtime"

Using modtime is not a good idea at all, this is very telling about how much author knows about different workflow. For those who don't know : you can have remotely mounted files where your machine and the server time is different (happens to me and realized that makefile is modtime based and it creates problem), also obviously clock can change and you do not want your version control system to be blind on changed file, ever.

He is a famous activist behind the Creative Commons. Died too young in 2013 at the age of 26. https://en.m.wikipedia.org/wiki/Aaron_Swartz

Is this still valid? If not does that mean that this app has no license?

I have always hated YAML, and still to this day, because I cannot write a yaml file, the indentation makes no sense to me and the list syntax is black magic (you actually have several ways to write those, once again the indentation implication is obscure). So while agreeing on the goal to be written/edited by humans to my perspective it fails at it.

Also 1e2 might not be the best example as this is just 100, but as someone who had to pass a lot of neural network training hyper-parameters : passing 1e-3 and so on is definitely a use-case. I am on the negative values Xe-XX (and YAML 1.1 would parsed it OK) but I guess other domains could also use the positive side to pass values (maybe as upper limits like 1e5 or so).

I think the YAML format should have parsed those number formats from the beginning. If this is fixed now, good job, hopefully the default yaml parsers are going to be "fixed". I would still use TOML over YAML any day, waiting for a human-json (some already exist) to be popularized one day.

Sorry but pass.

Nice calling syntax though.

A solution is to use ipset and have fail2ban adding/removing up with ipset. I intend to write a blog about it, and other things about running your own server, as soon as I get some free time.

* Web with python : yes, make sense, python is very friendly it's kind of the closest to no-code we can do

* No benchmark : ouch, no way I am touching this without knowing, at least in the big picture, what to expect

* Front-end : so this is a wrapper of Chackra UI which is itself a wrapper of React (which is the slowest framework out there) -> not really what I am looking for. I can understand that for some quickly made website this can be OK. For a serious dev I don't think this will have much appeal. I guess you need to target casual users.

* Not much bloat on the dependencies so this is quiet good on that front, I was expecting way worse.

* Your a startup and backed by YC and I see no business plan, priced service nor anything alike This is very suspect, for me as long as I don't understand how you are meant to work in the long run I will not involved myself using your library.

I am probably not your target user, I will stick with flask/tornado for prototyping my back-end and use lesser known but amazingly light and fast front-end framework. Good luck going forward.