Clients can work around it by making a search on the home instance that filters by community id and submitter id. Something like this.
Clients can work around it by making a search on the home instance that filters by community id and submitter id. Something like this.
You can’t have content addressing because it’s mutable. On the other hand, UUIDs are made for that. There’s even multiple types of UUIDs made for distributed computing with namespaces and such.
Amazing. One feature that is desperately needed on Lemmy is to open a post in another instance, not just a community or a user.
Well, that reminds me that Mastodon has huge, unresolved problems, such as tags being part of the post’s body like Twitter rather than being a separate field like Tumblr.
Reading tweets with a hundred hashtags at the bottom seem really thirsty for attention, which is bad because Mastodon wants to fundamentally work with these, yet doesn’t have good in-post integration for them. It makes interactions less genuine, more performative.
Rome wasn’t built in a day, and Mastodon won’t be good tomorrow either. In the meantime, you can vote to make it better on https://github.com/mastodon/mastodon/issues/10743.
The issue with gaming on laptops is that you’ll need to spend at least 1200$ at the bare minimum to play anything and 1600$ to have a good experience. And even then, the laptop is pretty much disposable and will be severely outdated in 5 years.
The best option for a laptop would be the Framework Laptop, but these can go for 3000$. The big advantage is that they’re worth every penny as they are upgradable. You can literally swap every part, including the motherboard. The aftermarket value for these laptops is going to be amazing.
Tumblr is a blogging experience that’s similar to Twitter, but more focused on the user itself than on the central feed.
Yep. And clients would be able to participate to the seeding.
Servers software developers would still have a massive amount of work to do to implement IPFS integration, but it’s doable. IPFS also has work to do here to make IPFS work natively with cloud storage protocols (like Amazon S3), but it already exists.
One issue with open source software is that you often have to pick the least-effort solution to avoid burning out your free labour. Free time is limited, and if IPFS takes slightly too much work to add, then it’s off the table.
And also the importance of APIs. It’s the only reason why there’s so many Lemmy clients compared to Kbin.
Right? Like, my app is definitely not ready yet its source code is available for all to see. And since I’m currently inactive, you could even fork it and get a bigger following than me if you wanted to.
These people just think too highly of themselves.
Steam Controller! Excellent idea!
… or just use Rust?
It’s a better foot-gun, that’s for sure
Even if we wanted to solve that problem, right now there is no way to cross-post on Lemmy. There’s a cross-post button, but it actually does a repost. I think we should think about that when Lemmy implements a cross-post feature in the first place.
Keeping communities separate is the simplest way to go, tbh. Sharing karma could lead to weird brigades, like r/ScreenshotsAreHard cross-posting from every picture of screens on the Fediverse and then mass-downvoting from there.
To me, the best solution would be to implement multireddits. That way, you can have your cat multilemmy of 100 communities without affecting your main feed, but you could also do the same for related or identical communities. Plus, moderators could create a multilemmy and display it prominently in their sidebar.
Being able to subscribe to a multi would solve that issue
That UI is called VSCode
At the top of your
.yaml
file, you can set a JSON Schema. Example:# yaml-language-server: $schema=https://json.schemastore.org/prometheus.json scrape_configs: - job_name: caddy static_configs: - targets: - caddy:2019
This way, you don’t have to memorize every possible setting and what it does and risk making a typo in the config. VSCode will just tell you.