[-] toastal@lemmy.ml 2 points 3 months ago

What does indexing have to do with actually getting to own your data & not participating in corporate-owned social media? If you want to straight hide it all, you would never post it to the internet. Most of us sought the refuge of Lemmy to avoid these platforms & know our post aren’t harvested to profit for a Lemmy IPO.

Recruiters can find you regardless, but also are not very useful for getting a job versus having a network & the cut they take means you get the shaft if hired thru them too. A platform like LinkedIn is drivel that will absolutely rot your mind so it should be an easy skip.

[-] toastal@lemmy.ml 2 points 3 months ago

You can easily self-host your static landing pages. There are decentralized (& self-hostable) social media options—such as Lemmy that you are on now. There is no need to involve Microsoft, & these big places like Reddit, or whatever, someone will eventually repost your content if it is good.

Also you code forge itself doesn’t need to be social media web 2.0. You can keep these separate.

[-] toastal@lemmy.ml 2 points 3 months ago* (last edited 3 months ago)

Cheeky answer would be: CodeForges ∩ {MS GitHub}^c^ (anything but)

I’ve been primarily using Darcs & a little Pijul, but have been using Codeberg when I need to use Git or just self-hosting via SSH.

[-] toastal@lemmy.ml 2 points 5 months ago

XMPP is battle-tested* and thriving*

I don’t think you know how many commercial use cases are relying on XMPP, nor how much the community has been working on updates. Older technologies tend to have maturity is spec but also in implementations where the servers are robust & already at the point of optimization over chasing features. We see this with how little specs it takes to run a server & have Conversation forks on Android have some of the best battery life & data plan usage in the chat space. The network is massively decentralized too… unlike Matrix where almost everyone is on Matrix.org or a server provided/hosted by Matrix.org giving them all the metadata.

[-] toastal@lemmy.ml 2 points 5 months ago* (last edited 5 months ago)

These aren’t well established where you can see the post was created in ’18. If they were established, you would seem them in the raw CONTRIBUTING.md. You can see folks having issues with using Discourse as a mailing list since it doesn’t quite work as expected & still requires review by someone with merge access to the primary repository. There is a SourceHut one that actually has some activity & I believe was once listed under the one of the contributing guides, but I can’t remember where it was listed. I doubt many maintainers are properly checking their email too despite listing them on the maintainer.nix file. I would hedge to say that unless the community migrates away, you would see folks complaining the tread above about disliking that there is no pull requests with instead push to the default branch so we would asume all contributions in practices will be expected to be done thru MS GitHub. As it stands going thru the mailing list puts a lot of friction on everyone & wastes time of other maintainers that are expected to then raise a PR on your behalf for review. Say that PR does get opened on your behalf, now you want to follow it since it’s your patch… well too bad since MS GitHub has no way of subscribing to PR threads like it does some aspects of by adding .atom to the end of a URL. As such, if you really want the in-practice option to not be under Microsoft’s domain, you’ll need to remove Microsoft from being the primary forge, relegating it to a mirror or dropping it outright.

[-] toastal@lemmy.ml 2 points 5 months ago

I agree with donation to upstream Conversations since it is the basis of many forks, but I still prefer the differences of Cheogram: 1) webxdc support, 2) black theme (not dark). The JMP support stuff could be great if I had a use for it, but currently don’t.

[-] toastal@lemmy.ml 2 points 5 months ago

I use XMPP every day to talk to friends & self-host a Prosody server (may move to ejabberd in the future).

The client & server situation can be a bit loosey-goosey since the base XMPP spec isn’t large, but involves a ton of opt-in XEPs. Luckily the Conversations compliance helps define a common set of expected specifications for servers & in many senses, I’m happy to see there is a zoo of clients you can find that fit your need from a CLI, to TUI, to web, to native clients that something will meet your needs & written in several different languages so you could find something that fits your interest for contributing to if you have the skills.

[-] toastal@lemmy.ml 2 points 5 months ago

Thai/Lao is ไม่เป็นไร/ບໍ່​ເປັນ​ຫຍັງ translated as (implied subject “it”) + negation marker + copula + anything or “it’s nothing”

[-] toastal@lemmy.ml 2 points 5 months ago

What a waste. You can buy a lot of indulgences with that.

[-] toastal@lemmy.ml 2 points 6 months ago

Learn to love OpenStreetMap

[-] toastal@lemmy.ml 2 points 8 months ago

Replicating all chat history + attachments provides a lot of resilience to the network from a node going down, but at the cost preventing to the home lab user from practically hosting a server which just means everything centralizes around Matrix.org, & when anyone on Matrix.org chats with you or your group, that metadata gets synced back to the central hub server once outwardly funded by Israeli intelligence.

[-] toastal@lemmy.ml 2 points 10 months ago* (last edited 10 months ago)

An ejabberd instance can handle 2 million concurrent users. The free software XMPP server is used by the likes of League of Legends, Fortnite, Zoom. If it’s a good enough for them, it would easily handle your community, big or small.

view more: ‹ prev next ›

toastal

joined 4 years ago