It doesn't need all that. All the complexity is because of stuff that's been added to the spec. 500ma@5v will just work if all you only connect is + & -
Tribler has inbuilt onion routing. If I understand it correctly, tribler <-> tribler connections don't need exit nodes and it's fast enough to stream video
I wonder if she signed an NDA that prevents her from saying she was greeted on her last day by a manic sweaty wide-eyed Elon musk demanding he be referred to as mechahitler.
I've always thought the trope was based on the idea of stunted development. Kids are heavily encouraged to drink milk, so films making a point of adults drinking it are indicating that there's some part of growing up that they've missed.
I'm a bit confused by the wording of this post? Is the problem that you have two .stl files that you want to edit and munge together into a new object? If that's the case, then as @AmazingAwesomator@lemmy.world you can import them both into openscad, subtract what you don't need or intersect what you do and place them into a new part for export. You can also do this in prusa slic3r if openscad is being buggy which it sometimes is with stl imports, but it's a massive pain in the arse
It's a failure on the part of mastodon. I don't really care about whatever drama dansup is embroiled in. Mastodon shouldn't imply a post is only readable by followers when it's just a public post that doesn't show by default in their frontend.
Honestly pixelfed should have just not fixed it. It's a fediverse problem that can be fixed and mastodon is just misleading people.
Platforms should either make it clear that it means just that the post isn't advertised by default on all platforms but is always accessible to anyone that wants it or actually implement e2e encryption.
As funny as this is, I'd rather people understood how the AI actually works. It doesn't reveal secrets because it doesn't have any. It's not aware that Musk is trying to tweak it. It's not coming to logical conclusions the way a person would. It's simply trying to create a sensible statement based on what's statistically likely based on all the stolen content that it's trained on. It just so happens that Musk gets called out for lying so often that grok infers it when it gets conflicting data.
When it comes to searching the database, the index will have already been created. When you create an index, it might take a while as the database engine reads all the data and creates a structure to shadow it. Each engine is probably different and I don't know if any work exactly like that, but it's an intuitive way to understand the basics of how B-trees work. You don't really need to think much about how it works, just that if you want to use a column as a filter, you want to index it.
However, when you're thinking about the structure of a database it's a good idea to think what you'll want to do with it before hand and how you'll structure queries. Sometimes searching columns without an index is unavoidable and then you've got to come up with other tricks to speed up your search. Like your doctor might find you (i'm presuming gaz is sort for gary and/or gareth here) with a query like
SELECT * FROM patients WHERE birthdate = "01-01-1980" AND firstname LIKE "gar%"
The db engine will first filter by birthdate which will massively reduce the amount of times it has to do the more intensive LIKE operation.
I'd go for syncthing over nextcloud for your specific usecase. Nextcloud isn't good for unreliable connections and they're sticking with the annoying decision of not supporting server to server synchronization.
If there's something you want to search by in a database, you should index it.
Indexing will create an ordered data structure that will allow much faster queries. If you were looking for the username gazter in an unindexed column, it would have to check literally every username entry. In a table of 1000000 entries it would check 1000000 times.
In an indexed column it might do something like ask to be pointed to every name beginning with "g", then of those ask to be pointed to every name with the second letter "a" and so on. It would find out where in the database gazter is by checking only six times.
Substring matching is much more computationally difficult as it has to pull out each potentially matching value and run it through a function that checks if gazter exists somewhere in that value. Basically if you find yourself doing it you need to come up with a better plan.
Cartesian explosion would be when your query ends up doing a shit load of redundant work. Like if the query to load this thread were to look up all the posters here, get all their posts, get the threads from those posts and filter on the thread id.
I don't know how far owncloud and nextcloud have diverged, but in the nextcloud client you can add filters to ignore files by clicking the three dots on the folder in settings.
You can also free up local space by using virtual folders, but it only works properly on windows.
It doesn't need all that. All the complexity is because of stuff that's been added to the spec. 500ma@5v will just work if all you only connect is + & -