You sure? IDK man, you know, you could be sleeping while she slits your throat.
She seems honest IMO.
There is something seriously wrong with them... that man needs to LEAVE ASAP!
I'm just playing it safe, I've had so many posts removed from this comm, I still have no idea why. Sometimes they give a reason, sometimes they don't.
Pictures don't seem to show up... but I'm guessing this is a caching issue, so it should be resolved by itself.
In the cheap one, we have two perfectly flat brass pieces pressing against each other.
I'll bet you any ammount you want, that's not brass. It's iron with brass coating.
So? It's not like you're gonna get banned here, lol 😂.
It's... confusing 🤨... birthday party in space, but the main character has to fight asgar the destroyer after the party 🤣.
Arrr, me hearty! Ye be askin' for a simple piece o' code in Rust, peppered with pirate comments. Here be a wee program that prints a hearty greeting:
fn main() { // Avast, me hearties! We start our voyage here. let greeting = "Ahoy, matey! Welcome aboard!";
// Yo ho ho! We print our greeting to the open sea! println!("{}", greeting); }
Now ye be havin' a taste o' pirate-infused Rust code! If ye be havin' any more requests or need further assistance, feel free to speak up, and I'll be at yer service!
This platform could be a viable alternative for forums (cuz we know in which state they currently are), but the lack of general attachments (any mime/file type) is what I believe stands in the way. I have an electronics forum I run (a local one, nothing too serious) and I believe Lemmy can make it more intereactive (not die out) because people from all over the world will get the feed and not just people that are online on the forum at that time.
Still, we frequently exchange PDFs, schematics (not always in image form), archives, etc., which makes Lemmy useless if there are no plans to implement something like this, even if disabled by default.
So, are there plans for anything like this being implemented?
At first, I thought it was just a temporary glitch or something, but a few days pass and I still can't comment from any if my accounts (I have 5, 2 are on this instance). And I think it's only exclusive to the Main community, not any other community... the weird thing is, I tried from 4 accounts, the 2 on this instance and another 2, none of them can comment. In particular, I wanted to reply after this comment.
https://readit.buzz/m/main@sh.itjust.works/t/15368/-/comment/113606
Every time it just returns a "language_not_allowed" error. This in Jerboa, I haven't tried commenting from the web UI.
EDIT: Now this is interesting. I'm in the web UI now and if I follow the link I shared in this post, it says it's a KBin instance and asks for my login credentials. I noticed there is something funky with the URL and I really have no idea how I'm following this community through KBin 🤨.
EDIT2: OK, I pinpointed the problem. The link to the reply leads to KBin because the reply is from a KBin user account. I can't seem to be able to reply to that particular comment (seems I can reply to anything that is from a Lemmy instance, but not KBin).
Here's the post.
https://sh.itjust.works/post/308065
Now scroll down and find a comment from a user named ScrumblesPAbernathy and try to reply to that comment, see if you get the same error as me (language_not_allowed in Jerboa, or just hangs in the web UI).
EDIT3: OK, the solution to the problem was to select English as the language in which you wanna write the reply. There is no such option in Jerboa (yet), but the web UI has it and if you just select English, the reply goes through.
Not really networking related (kinda... sorta...), but just had to share it. I think his granma did it 😂.
Thinking about calling her on my next networking gig, lol 😂.
This is a (quite long, LOL :D) tutorial I wrote on the subject and I believe it covers most user scenarios, so it uses safe methods (known to work in generic scenarios, when the printer's manufacturer and model are unknown). I also tried to write it as plain (simple) as I possibly could, so that even regular users (users that are not tech wizards, but can find their way around a computer and can probably install a distro like Ubuntu on a PC) can configure the Linux print server and add the shared printer on a Windows install.
You can download the tutorial in PDF and DOC from here or here. Also, here are the plain (unarchived) PDF and DOC files.
I hope this tutorial helps users that have given up using their old (but working) printers, just because they don't have x64 (64-bit) Windows drivers :).
