web dev and digital artist making !lemmynade@lemm.ee
Of course! Yeah, this post was intended to be less of a proposal and more of a brainstorm session. Maybe licenses aren’t the way to go about this, or we create our own licenses to be compatible with ActivityPub and match Lemmy’s values? Maybe it doesn’t matter how our content is used, or there’s nothing we can do?
You might be right, I definitely see your point. ActivityPub adds a whole new layer to this too. In the end though, isn’t the content we post no different than anything else published on the Internet? I guess it’s important to note that technically nothing public can be 100% prevented from being used in unwanted ways. However, there might be other ways (legally, socially, etc.) we could discourage it.
Regardless, I’d love to get a better sense of how much this matters to us here on Lemmy—or if it should even matter in the first place
!lemmynade@lemm.ee has this
I’ve been annoyed by this too. Here’s the issue on GitHub for discussion, I doubt anyone will have any objections but it still might be a little while until it’s implemented
We can’t force people to join, but we can emphasize the negatives of Reddit and the ways Lemmy solves those. Things like:
People that value those things are the ones that will consider moving over. You might say that you’ve read over Reddit’s terms and conditions, and then present the Lemmy community as a private and safe alternative if anyone wishes to join?
The closest I know of is not completely free or open source, but it’s by Ubiquiti Labs and it’s really good for a mobile video editor. Mentioning it because it might still meet some people’s criteria:
Ah, it ended up being my language settings for me
Same thing happened on !lemmynade@lemm.ee from a new test account I created on lemmy.ml. All posts are still visible from other accounts.
Definitely take this all with a grain of salt—I am by no means a legal expert, this is just my advice.
Required by law in Germany if you are collecting any sort of data about your users (even if it is being collected by a third party through your app, or if it is entirely anonymous data).
Required by law in Germany for the same reasons as the Privacy Policy. This agreement makes it clear how your users’ data is used.
Required by law in Germany if your application uses cookies of any kind (mostly applies to web app and web technologies)
Highly recommended. This may protect you immensely if and when you end up in a legal situation down the road.
Otherwise, you should look into these as well if applicable:
These documents matter most if (1) there is money involved or (2) when you are receiving, processing, storing, or sharing user-submitted content or any data about your users. This is because you are less likely to end up in a legal mess if you’re not taking people’s money or data.
Starting out, you can find templates for these online. A template will be better than nothing at all. Then, if you are able down the road, you can hire a legal professional to write and review your documents for you. A legal professional might recommend more specific documents or different versions of the same document as well.
Not sure about Germany, but in the United States it’s fairly inexpensive to start an LLC. You can then put legal documents under that new entity instead of your own personal name. This can protect you and your own belongings from any unfortunate financial or legal situations.
Again, if you’re not receiving money or any user data, you don’t have to worry quite as much. However, it never hurts to play it safe. Mistakes happen and anyone can get sued.
This is not possible on the official Lemmy UI and as far as I know no third-party apps or clients support this either. What some third-party apps do support is hiding content based on keywords. If the content that annoys you has some words in common, maybe you could use those keywords in a third-party app to filter it that way?
Codium does surprisingly well at generating JSDoc, and it processes your code within the context of your entire codebase. Still not quite there yet, but you might be surprised
I know there are documentation generators (like JSDoc in JavaScript) where you can literally write documentation in your code and have a documentation site auto-generated at each deployment. There’s definitely mixed views on this though
something like !memes@lemmy.ml/281723 isn’t the best, but would at least make things more consistent across instances and could be formatted by apps and the web UI to look nicer
Really cool! Reminds me a bit of the Numi calculator too
Yeah you might be right, not sure if migration will require any extra space but it’s possible. Some providers offer very cheap snapshots or backups and you could just make one while you attempt to migrate. If it doesn’t work, it would be easy to revert at least
There’s not much more of an option unless someone else knows of one, but at some point you will need more storage again and object storage is just cheaper than block storage
Media is likely what’s taking up the most space. Pict-rs supports object storage, at the least that would be more cost-effective (usually around $4 per month for 250gb) than scaling up your machine’s disk space
Mastodon accounts automatically add the @
EasyPanel is a hidden gem. Caprover feels very robust and the main dev is really friendly. Coolify is still under development but looks very promising.
I use Caprover mostly since it supports managing multiple servers through Docker Swarm, otherwise I’d probably be using EasyPanel.