
- SpacePirate@lemmy.mlBanned
- 0 Posts
- 7 Comments
- SpacePirate@lemmy.mlBannedto
Selfhosted@lemmy.world•Is there anything like a self-hosted version of medium of substack ?English
2·1 year ago
- SpacePirate@lemmy.mlBannedto
Free and Open Source Software@beehaw.org•We have to solve the money problem!
2·1 year agoThey haven’t updated their wikis for Operating Costs or Hosting since late 2022, somewhat aligned with their blog post on handling the mass influx of users from “E-day”.
Back then this was 6 AMD 5950 16/32 with 128GB of RAM and 2x3.84TB SSDs, with one “storage provider” with an AMD epyc 32/64 with 400GB of RAM and 10TB of storage.
Their hosting provider doesn’t offer these same SKUs, but roughly equivalent could be about €200/mo for each of the former, and the beefiest high RAM option is like €800/mo, totalling €2K/mo?
Curious how much the infrastructure has grown, but I haven’t seen anything else. Even so, these costs are extremely high.
- SpacePirate@lemmy.mlBannedto
Free and Open Source Software@beehaw.org•We have to solve the money problem!
1·1 year agodeleted by creator
- SpacePirate@lemmy.mlBannedto
Selfhosted@lemmy.world•Best way to get IPv4 connectivity to my self-hosted servicesEnglish
81·1 year agoCurious question, why would IPv6 introduce additional latency?
- SpacePirate@lemmy.mlBannedto
Privacy@lemmy.ml•JPMorgan Chase is about to let advertisers target customers based on their spending
391·3 years agoThis is nothing new, other than that Chase has brought this capability in-house. Credit card companies have shared purchase information with second parties forever.
Chase Media Solutions follows from the integration of card-linked marketing platform Figg, which JPMorgan Chase & Co. acquired in 2022
- SpacePirate@lemmy.mlBannedto
Selfhosted@lemmy.world•How Nginx Went From Being the Little Engine That Could to Become the Fork of the DayEnglish
542·3 years agoFrom my understanding, the impetus was that F5 submitted a CVE for a vulnerability, for an optional, “beta” feature that can be enabled. Dounin did not think a CVE should be submitted, since he did not considered it to be “production” feature.
That said, the vulnerability is in shipping code, regardless of whether it is optional or not, so per industry coding practices, it should either be patched or removed entirely in order to resolve the issue.
You can always reflash it with your own if you hold that concern.

Self hosted != FOSS