Ah I see, that’s unfortunate then. For what its worth, I still think the bot is a great idea for discoverability and bridging the two services together! I hadn’t seen it before since I usually have bot users muted and happened to see this comment chain while logged out.
I’ve given it a follow from my Mastodon account since I do tend to miss quite a few cool Lemmy posts it seems, and I think it’ll help me find some communities in general that I’ll want to subscribe to from over here.
I wonder if perhaps wrapping the majority of the text in a spoiler would work. Though I don’t know if that translates over to Mastodon (if not, it might look a bit funky on that side).
And if you really want even more barebones, you can just do git init --bare into a directory on your VPS, and then git clone user@your.ip.here:path/to/the/directory and use git as you would normally!
Sometimes the only way out is through :)
Hit escape to enter normal mode, :q to quit if you don’t have any pending changes, :wq to save and quit (or Shift ZZ), :q! if you don’t care about your changes (save without exiting)
If you’re interested in learning Vim, I’d recommend running vimtutor, which should be present on most systems. But of course, the best way to learn it is to simply use it as much as you can!
Continuing on what Rolling Resistance said (sorry for the delay, had to step away for a while), I know plenty of people who do use a password manager and still use a static password in some places (hell, I’ve been guilty of that in a few places - but generally on network-isolated systems). Some people also don’t use 2FA because they find it inconvenient.
Passkeys are more or less very similar to how SSH keys work if you’re familiar with those, your device (or password manager) generates a secret key that it only has access to, and then gives the public key to the website (and a new keypair is generated for every single website). When you login to a website, the website sends you a challenge which you sign with your private key, that the website can then verify using the public key that you used when enrolling the passkey. This way, a website never has any form of secret - making say password hash leaks less relevant, whereas in theory you could give your public key(s) and post it on Google’s homepage without any repercussions… but don’t quote me on that one.
So even if you use a password manager, if you still have a few websites that share the same password, and one of those gets compromised - those other websites may still be vulnerable which wouldn’t be possible with a passkey.
Oh, nice! Doesn’t look like it’s hit the Firefox Addons repo yet, but I’ll be looking forward to it when it does.
They really should have linked the main page which does have a screenshot (and a few partials): https://cinny.in/
I guess it depends on if you’re the type of person who sees VSCode as an IDE or just a text editor.
Vim is effectively the same way.
Yep, my desktop PC may or may not have one of its SSDs not mounted…
I just use whatever text editor I happen to have open - generally that’s (neo)vim for me, but I’ve also used IntelliJ/JetBrains products to do so, along with VSCode on the rare case.
None of them have had the extra features that you mentioned, I don’t use emacs but considering its very powerful org-mode I wouldn’t be surprised if someone has implemented something similar for Markdown? I haven’t specifically seen anything that covers these though (which could just be not looking hard enough, admittedly).
Well yeah, I’d say the same concept applies to using anything tech related these days. It’d be like if you “knew” where all of the keys on a keyboard layout that you don’t normally use are located - you’d still need muscle memory to actually use it efficiently.
I currently use GitLab, but if I were doing things from the start I’d go with Gitea or Forgejo since its lighter. Though I do quite like GitLab CI (which is why I didn’t go with the other initially) but these days I hear Gitea has Actions support built in.
Oh my goodness, is that BlueJ? I haven’t seen that thing in ages…
Plot twist: Coffee is the origin of their username
I guess at the end of the day you’d have to decide for yourself whether you’d prefer submitting bugs to a social media spot (if the project has one), which is a lot more open to drama from others than on GitHub (which is not to say that drama doesn’t happen on Git[Hub/Lab/etc]).
Maybe having a simple form on the project website that can mirror the bug reports to github is oneway to provide people with an easier solution to give feedback that they might not give otherwise.
A couple of issues with this:
It’d be easier to spam / fill with junk, and would require either a custom solution that every project would have to reinvent the wheel on, or another centralized service that acts as the “gatekeeper” to spam… in which you just have the GitHub issue all over again
This method doesn’t give developers an easy way to respond/follow-up on the report. It is very common for “bug reports” to not actually contain enough information on how to reproduce the problem unfortunately. You could say, add a field for an email address (which would need to be filtered out before posting to Git and stored somewhere / tied to the issue that gets opened) but I think most people would be against giving every single individual project their email address than GitLab/GitHub/etc. Additionally if we’re focusing on tech illiterate people as you mentioned, its unlikely they’d even respond to a follow-up email.
Welcome aboard, and hello from across the Fediverse!
You can get the best of both worlds actually. Matrix supports doing video calls through Jitsi Meet!
I want to say that for 1-to-1 calls it does video natively, and for group video calls it uses Jitsi Meet.
Nope, it has to manually be setup again, and you’d have to get everyone to subscribe to the new one as well.
My instance has 13 users, and has been up for 2 months now:
1.5G ./pictrs
3.4G ./postgres
They might’ve done so out of necessity. I don’t know if the dev(s) of the Simple Tools apps were working on it full time, but if they were and just not enough contributions were coming in from it… Well everyone has to eat.
As the saying goes, “everyone has their price”. It’s easy to condemn the developers for their choice until you’re in the exact same scenario as they were. Whether that’s because they were starving, or even just offered enough money to make their lives a lot easier - not too many people would turn it down.