@[email protected] Depends on the inference engine. Some of them will try to load the model until it blows up and runs out of memory. Which can cause its own problems. But it won't overheat the phone, no. But if you DO use a model that the phone can run, like any intense computation, it can cause the phone to heat up. Best not run a long inference prompt while the phone is in your pocket, I think.
projectmoon
joined 1 week ago
@[email protected] said in NodeBB v4.0.0 — Federate good times, come on!: Do we need need to refollow?
@[email protected] said in NodeBB v4.0.0 - Categories not following group actors:
@[email protected] sounds good! I'm actually re-assigning the category before creation, rather than using the helpers in TopicTools, but I'll make the issue in case that should result in the same behavior
I'm very eager to try this plugin lol. Have you put it up on GitHub somewhere yet?
They show up as a link to a long uuid, which when clicked, goes to 404.
If you have a wireless card (or don't need wireless) capable of working with Linux Libre, then by all means use it. There is no technological advantage to using Linux-Libre. There are principle advantages. I say this as someone who uses Linux-Libre on my Gentoo laptop (and maintains an overlay with an ebuild for Linux-Libre).
@[email protected] said in NodeBB v4.0.0 - Categories not following group actors:
@[email protected] Adding UI for settings today. Will put on github once that's done (though I can share the core snippet in a bit). It can also work for auto-moving local tagged posts as well.
Should also mention that not every post from remote actors is tagged, so it might not catch everything. Could possibly have it just read any uncategorized posts and move based on users instead? Might be a better workaround for core, but if you have any thoughts let me know @[email protected]
Sounds good. Looking forward to trying it out. If there's a way to tie the post back to a Group Actor "user" (which are the local NodeBB users that share/boost the content within NodeBB), then you could probably make the algorithm more reliable. I don't know anything about the internals of NodeBB, though. Just spitballing ideas.
@[email protected] said in NodeBB v4.0.0 — Federate good times, come on!:
@[email protected] careful with that though, not all tags are the same, some have a higher signal-to-noise ratio, but others would just be filled with garbage 😬
I think the best way, then, would be to have rules that map various group actor URLs to categories, and possibly also tags. Nothing automatic. Only configured. Of course, once Lemmy fixes the ability of Group actors to follow other Group actors, this will be a non-issue.
One other possible solution, which is employed by Misskey et al., is a proxy actor. It's a special user that follows other users, and relays info within its own instance. It's used for doing things like adding a remote user to a list without directly following them. The proxy account follows the user, and then your local instance adds the remote user to your list. But all ActivityPub interactions go through the proxy user.
Was a link posted to it? Also I'm noticing that edits don't seem to fully federate. 🤨
@[email protected] funnily enough, I switched from Linkwarden to Hoarder. I like the smart lists. Just bookmark everything, check it later.
I see this in my own forum, because it synchronized to nodebb.org, and then to me. How was it posted? By using the NodeBB forum as a Lemmy community?
view more: next ›
@[email protected] yes, that function is there. Then maybe the best compromise would be to essentially add a reverse of that reply spotlight feature, so you can read the original post without the page jumping.