I run seafile, but holy shit do I regret looking at the source code.
I run seafile, but holy shit do I regret looking at the source code.
Red hat I can live with. The problem is IBM.
It’s really nice hardware. And for some segments of the market, it’s not even particularly expensive compared to alternatives of similar build quality.
Yes. Very slow. And only accessible from tor clients or tor2web/onion.to-like constructions. Which adds additional delay and errors.
There are things for which onion addresses are the right solution. This is not one of them.
It’s very possible. If you carefully manage your attack surface and update your software regularly, you can mitigate your security risks quite a bit.
The main problem is going to be email. I have found no reliable way to send email that does not start with “have someone else do it for you” or “obtain an IP block delegation”.
That sure does seem to tick a lot of boxes. I’m going to check it out!
That’s true. The bizarre paradox of the centralization of edge infrastructure is real.
That said, the other edge-lords (haha) could offer similar functionality, but they chose not to.
I am not sure what that would accomplish.
I have all that, but I still use cf for a ton of stuff.
The trouble with cloudflare is that there is just one. It’s one of the best registrars out there, the only free/cheap and usable DNS host (have you seen what route53 charges per zone??). That without getting into the whole tunnels and DDoS mitigation end of things, which is nearly unique at any price point.
The problem with cloudflare is that we’re missing three other cloudflares to move to if they decide to pull evil shit.
M’lady…
I’m pretty sure AST would agree with you.
Still, the award is richly deserved.
The solution to that is to buy a net block. IPV6 address space is very affordable.
A constructor can’t be async so now I need to restructure my code to use async factories instead of constructors
It sounds like you’re trying to do OOD/OOP. In js that’s usually not the way to go. You might want to restructure into a more functional architecture anyway.
Thus insisting on any other way is a major flaw in the developer not the language.
I mean, I understand the idea, but this is a pretty asshole way to frame it. I don’t think I deserve that, and certainly OP doesn’t deserve that.
From browsing your other comments on this thread I understand that you are in a context where you can’t await, that you expect the invocation to take very little time, and that the library offers no complementary sync interface.
As far was I know you’re stuck in this case. I consider the stubborn refusal to add “resolve this promise synchronously right now” a major flaw in js.
It’s standard for operations that take a while and can be performed asynchronously.
What’s your problem with it?
I mean, that’s fair. It’s certainly not a technical impossibility to get it right and keep getting it right.
Unpopular opinion: the only vendor that does sleep right is Apple. The only reason they can is the tight vertical integration of the platform where they control all the hardware, all the drivers, and can exercise control over all the applications in the App Store.
More open platforms are essentially fucked.
That’s fair.
There was something wonky with the mapping of OIDC attributes to user properties, so I decided to look at the seahub source and see if it would be easy to fix.
Turns out, the whole thing is held together with hope and spit. Literal beginner code.