I'd see this to be implemented in Lemmy itself. Hashtags are a global thing, not instance-specific, and should already be available to Lemmy via AP.
Lemmy would "just" need the ability to display a hashtag as a "community" containing posts made under that hashtag. Question is what to do with replies but given Lemmys design, they could probably simply be left out because, if it's truly on-topic, the post will likely contain the hashtag too and therefore land in the hashtag "community".
Oh sweet summer child...
That's by far not the only proprietary component in that or any phone.
Sustainability has a price. You're indirectly paying that price for the Pixel too btw, it's just not on the bill.
Wat's the OSK?
Choose two:
Btw, mATX boards and cases aren't that large and usually cost the same or less than full ATX. Might be a good middle-ground.
Also has an extensive SElinux setup.
Scheduling priority on Linux is borderline broken. Nice doesn't even do anything noticeable on modern systems.
Why the overlay? If you just want to give the drvs names (good practice IMO), simply use a let binding.
The buildEnv is unnecessary: systemPackages does the same with all the derivations in the list in the end anyways.
I don't know what you're getting excited about here; this is all publicly available information which Facebook could scrape at any time they wanted (federated or not), even right this very second.
While paperless processing is indeed quite intensive, it's not like this is a latency-sensitive task. If it takes 5m to OCR a scan, so be it. That doesn't make it unusably slow.
With that kind of hardware, nothing you could tweak would help a whole lot.
You need an upgrade mate.
I was being a bit unclear here, what I meant was that replies mentioning a hashtag shouldn't show up as posts in its pseudo-community; only posts. Replies to a post with a hashtag would show up regardless of content.