It's not like you have to maintain a fork, it's pretty minimal, all you need is a Dockerfile with what you want and build the container. Other than that you just keep bumping the version like you would the standard distribution.
For example to use rate limiting I just have a Dockerfile like this:
FROM caddy:2.9.1-builder AS builder
RUN xcaddy build --with github.com/mholt/caddy-ratelimit
Security and accessibility/simplicity are almost always at odds with each others. It's a tradeoff that needs to be made. You are entitled to dislike the current trend and prefer making security optional. But you can't possibly be surprised if most people are happy to prioritize their privacy and security over "the barrier of access to disruptive counter-corporate/counter-state information".
HTTP 1 is on a depreciation path and HTTP3 requires TLS, which would mean getting the blessing of a trusted (typically corporate) root cert every 90 days to continue letting random people access my website.
In the US, states recently passed anti-abortion laws which also banned aiding and abetting people seeking the procedure. That would cover ___domain names and certs if any relevant tech companies had headquartered in those states - or if passed as federal law.
Trans rights are actively heading in that direction, and supporters are the very same that lambasted NYT and others as "fake news" that needed to be banned while pushing narratives of contrived electoral processes.
Fear of political regression is real in America, without even looking internationally.
Societal and technical systems evolve together. With the depreciation of HTTP1, future cheap middleware boxes will likely effectively enforce using HTTP3 and consolidate the tech landscape around a system that is far more amenable to authoritarian control that the prior generation of protocols.
It's fair and valid to call out such scenarios when discussing international technical standards. These protocols and the consequences will be around for decades in an ever evolving world.
The "most" in your strawman here is just companies like Google who want to a) bend to those who want to DRM the entire web b) hide and lock away their tracking traffic from those being tracked c) make ad blocking impossible.
Yes, Django is a quite some decently sized CMS framework, with it's occasional security quirks and attack surface. I expected it to be some lightweight go application to be honest, based on their ___domain.
Exactly, someone with more time than me please create a nice looking, lurker friendly, read-only aggregator with all the different content in all the different servers/communities. Ideally merging submissions and comments when possible. You would have me immediately as a user and I bet I wouldn’t be the only one.
It’s so obvious that I guess someone must have done it and I just haven’t heard about it yet.
I've been drawn to kbin, it is part of the "Fediverse", so you can see kbin, lemmy, and I believe also mastodon posts from it. If you just anonymously browse to https://kbin.social/ (the main instance right now) you'll have something similar to the reddit front page, content from a bunch of different instances. It is definitely still a little rough around the edges, but considering it is one dev and the first commit was only two years ago, it seems pretty good.
Is it automatically pulling content from all other instances??? That was not clear to me, I though it was some form of cross-posting and required someone to submit things.
So... Sounds like you want what I keep thinking about:
Front end that works with feeds from multiple sources, like RSS, and permits comments, posts etc using SSO, with all interactions logged centrally in the SSO account (for later edits deletes etc).
Sound about right?
Because you me it seems like every provider in that list should be able to make a profit off the data and interactions... With users who want increased privacy able to pay for an SSO subscription to prevent the sale of data on that end.
And we already have all the parts to make it work...
I was thinking about this yesterday and in other threads people are writing about similar systems. The key thing for me and the word that keeps getting written is "RSS", I want a powerful client to experience different content in different ways. There are many communities and content creators that I want to follow but it's too complicated with modern platforms. From a usability standpoint it's bad both for creators and for end users, the result of this is that you miss out on some important stuff.
For example I might not have time to watch Twitch streams or Youtube videos from a creator over a couple months but I would still be able to go to a weekend event in my city or buy some some new merch that he announced. In general I would need to use another platform to not miss out (Twitter, Instagram).
If I controlled a client capable of aggregating all types of content I could decide to filter things out according to my immediate needs.
Content creators would own their own platform or choose a generic service provider and have freedom about what to make (video, image or text posts) and how to monetize.
The problems are who pays who, content discovery, and a decently sized userbase.
I only use RSS to convey the concept of a standardized syndication system, thus "like" being used rather than saying RSS itself....
But yes, what you say is exactly the point of what I'm talking about.
Some sites would focus on being the universal front end for casual browsing while others would focus on niche purposes such as moderation or unique content types/presentations.
The data would be stored with the user by default in my model, ensuring they have control of their content, and offloading a bunch of the delivery work from the front end site (essentially every users SSO becomes the cdn for their chunk of the content).
It has some problems but it's really not much different than now except it's easy as pie for people to get eyeballs on their content (does mean monetization has some issues, as it does now).
Yes although me being primarily a lurker I need even less. More than post or comment, if I have an account it would be to block some things and prfioritize other things more closely. What you describe would make sense for more extended functionality, but there is silent majority of lazy lurkers like myself that could be served very easily.
So my model would be one where you pick a site as your front end, most of which would have default curation and subscription to various subs, providing an experience like /all by default.
Though it would look like /all what it would really be is more like an RSS reader aggregating multiple sources according to your preferences.
A Reddit alternative would naturally form in this ecosystem, with smaller alternative front ends abounding, and take dominance just as Reddit did, but unlike Reddit it would not be able to screw over sub mods etc.
Subs would be truly independent of the front end site, even if they are themselves also front end providers.
It's Distributed Reddit in a sense.... Though in my view it'd be best to make it content agnostic, so it can be adapted to other uses, specifically for a YouTube clone and such.
Really, there's a model where for most it's essentially a Facebook alternative that integrates into thousands of third party forums seemlessly...
I would use that. Please go for it! It's so obvious to me. There's a giant discoverability gap in the whole fediverse thing that can be easily addressed. This is by design in mastodon, but I don't think these reddit alternatives are so against virality. The only risk is that the whole thing fizzles out so hard that even an aggregated view of the entire ecosystem doesn't produce enough content to keep people engaged.
If you do it, please keep in mind merging submissions and their comments, 6 separate entries for the same thing each with a couple of comments is a much worse experience than a single entry with a dozen comments. You can start by simply using the URL as a grouping key and try more sophisticated things later.
SSO only applies to those engaging, with those lurking being presented the default selection of subs for that front end site.
Essentially, Reddit Appollo and all the others are the front ends, with the subreddits being independent back ends (which would certainly also have their own front ends, even if restricted to their own sub).
Thus, the most popular front end would almost certainly just be a clone of old.reddit with the /all and /popular being made of the aggregate communities that front end has selected for default inclusion (with the most inclusive front end almost certainly "winning").
Tldr - SSO only matters for commenting/posting, lurkers would/could get literally the exact same experience as Reddit...
Yeah, but for the platform to succeed, there needs to be one /main aggregator site that I can point people to, I don't want to remember random servers.
Why would they buy something that is open source? They could acqui-hire but Hotz doesn't strike me as a person that would stay at a big corp like AMD for a significant amount of time.
To control it. If they are successful at making AMD cards competitive in AI, and I agree that what's missing it's only the software, that would create immense value for AMD. Too much to not have control over how it evolves. If they are successful it will not just be Hotz, he will hire other devs and an entire community will form around it.
Sure they could just fork it and try to continue development themselves, but the community and momentum might very well not go with them.
If/when tinygrad is successful then AMD acquiring control of the stewardship/direction-setting of the software that drives the incremental demand for their hardware is far more valuable than Hotz's talent itself.
simplesurance GmbH | Berlin, Lisbon, Remote in Germany | Full Time https://www.simplesurance.com/
We are building one of the world’s leading platforms to make insurance accessible.
Since 2012, we are proudly “Made in Berlin”: we are very international with 150+ people from over 30+ countries working daily in our central Berlin office. Our internationalism is reflected also in our business since we are active in over 28 countries.
simplesurance GmbH | Berlin, Lisbon, Remote in Germany | Full Time https://www.simplesurance.com/
We are building one of the world’s leading platforms to make insurance accessible.
Since 2012, we are proudly “Made in Berlin”: we are very international with 150+ people from over 30+ countries working daily in our central Berlin office. Our internationalism is reflected also in our business since we are active in over 28 countries.
simplesurance GmbH | Berlin, Lisbon, Remote in Germany | Full Time https://www.simplesurance.com/
We are building one of the world’s leading platforms to make insurance accessible.
Since 2012, we are proudly “Made in Berlin”: we are very international with 150+ people from over 30+ countries working daily in our central Berlin office. Our internationalism is reflected also in our business since we are active in over 28 countries.
simplesurance GmbH | Berlin, Lisbon, Remote in Germany | Full Time https://www.simplesurance.com/
We are building one of the world’s leading platforms to make insurance accessible.
Since 2012, we are proudly “Made in Berlin”: we are very international with 150+ people from over 30+ countries working daily in our central Berlin office. Our internationalism is reflected also in our business since we are active in over 28 countries.
simplesurance GmbH | Berlin, Lisbon, Remote in Germany | Full Time https://www.simplesurance.com/
We are building one of the world’s leading platforms to make insurance accessible.
Since 2012, we are proudly “Made in Berlin”: we are very international with 150+ people from over 30+ countries working daily in our central Berlin office. Our internationalism is reflected also in our business since we are active in over 28 countries.
For example to use rate limiting I just have a Dockerfile like this:
FROM caddy:2.9.1-builder AS builder
RUN xcaddy build --with github.com/mholt/caddy-ratelimit
FROM caddy:2.9.1
COPY --from=builder /usr/bin/caddy /usr/bin/caddy