adparadox

I do a check for `request.htmx` in my views and conditionally return a template partial as needed. This reduced my need for one-off view functions that were only returning partials for htmx. Works pretty well from my experience.

CapRover has a UI to install new apps or configure existing ones.

https://coltrane.readthedocs.io/en/latest/#other-minimal-dja... has a list of a few options, but the most recent is https://github.com/pauloxnet/uDjango.

You can see posts on any server to "find out what the vibe is" without registering. For example: https://fosstodon.org/public/local. What are the transactional costs here?

Stop trying to make Mastodon be Twitter. If that's what you want, go use Twitter.

I don't see how using an optional, open-source, non-chronological feed means that someone should just "go use Twitter". For one, the incentives are completely different between Twitter which generates revenue based on engaging users (and juicing subsequent algorithms), and someone who builds a separate feed interface for Mastodon.

I don't get this mentality of "I like X, but I don't want to use X, so imma go turn Y into X" some devs seem to have.

Developers like to solve problems and build things. I've re-created other projects and products lots of times. Why is it a problem what someone chooses to do with their own time for their own reasons?

Playing into people's FOMO is what got the Internet into the rat's nest

Disagree. Incentives tied to advertising-based business models is the root cause here, not FOMO.

Disclaimer: I made my own alternative timeline for Mastodon as well, so I'm pretty biased. :)

I'm the creator of Unicorn, so this is neat to see it on Hacker News again. I've been working on Unicorn nights and weekends since July 2020, slowly adding in new functionality and improving it. I have a conference talk explaining the origins a little bit: https://github.com/adamghill/djangocon-eu-2021-conference-ta....

I never expected Unicorn to completely replace larger SPA frameworks, but I have found it solves for most of the use cases I need for my sites.

Thanks for checking it out -- all PRs are greatly appreciated to add new features or fix bugs!

I had the exact same problem with Render, but I wouldn't expect them to handle this situation because I'm guessing it's kind of an edge case? I ended up using a DigitalOcean Droplet + CapRover to do this, and then wrote a giant article detailing all my steps in case that's useful: https://alldjango.com/articles/serve-multiple-django-sites-f....

Good suggestion! I now show the license if it's set on the repo.

I find it ironic this website is written in Python. It's a single HTML page. Make it a static site and host it for free/low-cost on S3 or something. Why do you need to host this website on a server, use Docker, etc?

Originally it _was_ just HTML + CSS, but I wanted each library's repository metadata (latest version, last commit, etc) to be dynamically retrieved and doing that client-side was brittle and way too slow. So, I used it as an excuse to see how far I could push my own personal static-site framework (https://coltrane.readthedocs.io/en/latest/).

Yikes! Thanks for letting me know. I'll fix that asap.

Thanks for the recommendation! I'll add it to the list as soon as possible.

Shouldn't the items be in the row

Maybe! I was messing with different UI approaches to relay this data and this made sense to me, but I'll see if switching to rows is more clear. Thanks for the idea!

Good idea! I'll add it to the subtitle.

It definitely might make more sense that way! I was playing around with different ways to display the data and landed on this approach even though maybe it's a little clunky. I could flip it and see how it feels -- thanks for the suggestion!

Thanks for the recommendation -- looking through the docs, it seems like it fits! I'll add it in a few or feel free to make a PR.

Not requiring NPM was one of my original requirements for anything on this list. All of these libraries should be available from HTML directly -- let me know or make a PR if that isn't the case.

It's there because some libraries explicitly call it out as a benefit so I included it. The code is OSS (https://github.com/adamghill/unsuckjs.com) -- feel free to make a PR to be the change you want to see in the world.

Nice, thanks for reminding me of unpoly! I will add it soon.

I didn't post the site to HN, but I did create it. Adding the first commit is an interesting idea. Or some way to measure longevity (i.e. how long has the library been worked on). I'll try to figure out a good way to do that or if you put up a PR I will take a look at it: https://github.com/adamghill/unsuckjs.com.

I added `dom-proxy` because that looked like the closest to a complete solution from a quick skim. Let me know if you want to swap for another one, though.

Thanks for the correction. Just updated it to be accurate... for now. :)

Nice write-up, I look forward to seeing how Strawberry progresses. I keep a list of JS front end frameworks where no build step is required at https://unsuckjs.com/. I'll add this there (and a few of the others mentioned in the comments here).

https://fastapi.tiangolo.com/ is pretty awesome.

https://github.com/adamghill/dlite/blob/main/src/component.j... ;)

I'm in the same camp and never want to run a build process for JavaScript ever again. I've been slowly improving https://dlitejs.com/ which is a minimal (5kB minified + gzipped) JavaScript framework which works great loaded from unpkg. It's pretty crazy to see how lean a framework can be nowadays (even with two-way binding, directives, and event binding) when leveraging newer standards like Web Components and the Shadow DOM.

Hello, I've been building this for the past week or so based on https://github.com/hodgesmr/mastodon_digest. Let me know if you have any questions of feedback!

I don't think there is an RSS feed, but looks like there is a JSON endpoint: https://github.com/mastodon/mastodon/issues/17269.

Even more tangential, I've been building an algorithmic digest of Mastodon (supports home, local, or federated) at https://fediview.com/. It might be interesting if you want a summary of Mastodon posts. Adding in RSS support might even be possible at some point.

I love the simplicity of this idea because for lots of sites the database works just fine as a queue backend and it reduces the amount of infrastructure needed. I currently use https://github.com/dabapps/django-db-queue for https://devmarks.io which also uses the database to store tasks instead of a dedicated queue infrastructure. `Django Q` also has an option to use the database, but I haven't tested it at all: https://django-q.readthedocs.io/en/latest/configure.html#orm. And if you are already running `redis` for your site, https://github.com/rq/django-rq is another option.

The one benefit of this package is that it is async-first which will be beneficial as Django continually adds in more async capabilities. Nice work! I'm looking forward to trying this out and seeing how it works!

A few days late, but I just saw this post in my referrals. I wanted to chime in I've been working on devmarks.io for the past few months. It is still pretty early, but hopefully it's helpful for a few people. Feel free to reach out to me if you run into any issues!

I totally agree about mimestream. It's everything I want in an app -- single focus, Mac-native, fast, and works well.

Two other Mac-native tools that I really enjoy using every day: GitUp (http://www.gitup.co/) and Postico (https://eggerapps.at/postico/).