lambalicious
@lambalicious@lemmy.sdf.org
- Comment on Mastodon has a new plan to make money: Hosting and support services for the open social web 2 days ago:
I hope we don’t kill this like how we kill Mozilla when it makes a plan to make money.
- Comment on Farewell to the fediverse 1 week ago:
as with F------k, R----t, T-----r
My dude. My gal. Sibling of my Fediverse. We are in the Fediverse. You don’t need to tiktok-censorship yourself like that. You don’t need to fallback to 2000s cringe. Embrace the Fediverse. Embrace the truth.
- Comment on 18% of people running Nextcloud don't know what database they are using 2 weeks ago:
That’s quite senseful yes. In the cases where I want to host somewhere that already has a Postgres service going, I just up and use that.
- Comment on 18% of people running Nextcloud don't know what database they are using 2 weeks ago:
…How come so few people are using SQLite?
- Comment on 2 weeks ago:
It’s on poob. Poob has it for you.
- Comment on 2 weeks ago:
Someone is projecting, I see.
- Comment on How To Use PeerTube for Podcasting 2 weeks ago:
You don’t need to. Content is perfectly discoverable without them. Just about the only real benefit is having the “extra storage”. And nowadays it’s pretty dangerous, as at least Youtube hallucinates edits for uploaded casts and stuff without the creators’s consent or knowledge.
- Comment on Mastodon says it doesn't 'have the means' to comply with age verification laws 2 weeks ago:
Rather than encourage people to leave, we should encourage more enlightened people to move there, and change the political climate
You want to put those “more enlightened people” at risk of being Gestapo’d or killed? We need them where they can actually do a net positive effect!
First clean up the shit in Texas (or any other fascist shithole) and make it livable, then live there.
- Comment on Mastodon says it doesn't 'have the means' to comply with age verification laws 3 weeks ago:
Fair enough. In that case I wish you a very successful revolt, that you hunt down and eliminate the fascists so they can’t come for you never, nowhere.
- Comment on Mastodon says it doesn't 'have the means' to comply with age verification laws 3 weeks ago:
Woudn’t it be smarter to just leave the hellhole that is Texas? Either to the north or to the south, leaving is a win.
- Comment on I'm "use NFS forfilesharing old." what's the current optimal solution for shared drives if I have like 3 linux machines in the house? 3 weeks ago:
You intendeth to mean Beowulf? I would mayhaps have seen one ere the break of my college time. Wouldst you tell me more about it?
- Comment on Mississippi's age assurance law puts decentralized social networks to the test 3 weeks ago:
Why would it affect their bottom line other than positively? Corporations love fascism because it can make it mandatory for people to buy from them, among other things.
- Comment on Mississippi's age assurance law puts decentralized social networks to the test 3 weeks ago:
and keep fighting it in court
> implying those neofash sites would fight against orders to tHiNk Of thE cHiLdReN
- Comment on I made a Firefox fork with Fediverse integration 4 weeks ago:
A central relay/proxy is even worse than your current approach. People are obviously free to set up their own Lemmy/Mastodon server if they want a relay.
Lemmy/Mastodon are quite heavy to set up if all you want is to proxy outbound connections. Just using any available proxy you have (which could very well be eg.: a SOCKS proxy set up on FoxyProxxy) is quite nimble and takes up at most a few kbs of RAM.
That said, for anonymizing the IP origin this only mostly works if enough people use the same general relays (basically the same principle as TOR, VPNs), which means this only becomes effective once enough people use this plugin that it becomes worthwhile to position such infrastructure.
- Comment on [deleted] 4 weeks ago:
The only part that is wrong TMK is the “indivisible” one; and perhaps the last item because I recall that PulseAudio and Wayland were pushed this way worse than systemd was.
- Comment on [deleted] 4 weeks ago:
Because it was not always the case that sysvinit was supported - things were sorta “accidentally hazy” for a while. There was a time (I think during Debian 9 and 10) that systemd not only was the default, but was also enforcedly linked against a large part of the stack (you couldn’t have a desktop environment, PulseAudio or NetworkManager without systemd, for example).
This led to the rise of projects like Devuan, that provide a working system that installs without systemd by default; Antix’s
nosystemdrepo, which allows to install components of the Debian stack without the enforced systemd dependency; and laterlibam-elogind-compatwhich aided shimming some of systemd’s requirements under elogind.Nowadays at least, the only hard part of not using systemd in Debian is 1.- switching (from or to) seems to require rescue mode and 2.- you lose some of the container management goodies (for eg.: Podman services).
- Comment on [deleted] 4 weeks ago:
None. On Alpine you can only use OpenRC and on Debian you can only use systemd. Most distros don’t let you change out the init system. If you want systemdless Debian look into Devuan.
Fake news. On Debian you can use both sysvinit and openrc (I have six servers on sysvinit, tho I do actually intend to shift them to systemd later mostly because of the container management goodies).
Judging from this post, I would say you should not be looking to change out your init system
Mostly agreeing here. For selfhosting the init system matters barely any, since past the default distro setup one would be doing most of everything with Docker, Podman, etc. At that point, none of the usual Linux religious wars matter much (you can perfectl edit a compose file with nano).
- Comment on I made a Firefox fork with Fediverse integration 4 weeks ago:
Sending the current URL and directly from your own IP too is quite the privacy hurdle already. I’ve already posted on what kind of things could be done to improve this, but first, a notice.
Your README says in the Privacy section:
Does not track your browsing
On the current implementation, this should be changed to:
Enables unverified third parties to track your browsing data
As that honesty is quite important.
As for measures that could be taken to improve on this issue, I have three suggestions (I might Issue Tracker them to the codeberg later, if I can find my credentials XD)
- Set up a uBO-stye control pane that allows to set this on or off per-domain or per-site. Bonus points if it allows for per-site specific on which lemmy instances to use the same way as uBO’s “3p” Custom Rules does. This already prevents a number of undesirable use cases, such as automatically sending LAN / non-DNS names to third parties when they can’t really be searched for anyways.
- Anonimyzing assist: Allow for sending only the global context of the visited site (eg.: only the domain) instead of the full URL.
- Anonimyzing assist: Allow to cache requests to send them later / send them in batches, to avoid clock-based / timezone-based tracking attacks.
- Anonimyzing assist: Allow for the browser-specific request being sent through a proxy or relay, so that IP origin information is not leaked. (I think this only really makes sense for users not logged-in?)
- Comment on I made a Firefox fork with Fediverse integration 4 weeks ago:
Yeah. Interesting to think if there are ways to get around that problem.
At a first flance, perhaps a uBlockOrigin-style control pane with per-domain toggle, so that for example you can send the info only when browsing a specific domain (let’s say, a news site; that’d be interesting to find discussion in Lemmy of). This would also prevent the issue of sending URLs that are not internet-wide (eg.: are on a localnet resolver, or an intranet).
As well as the abiity with an option send the request through a relay or proxy, to remove IP origin information that can be used to build the profile.
- Comment on stay weird fedi: in defense of the eccentric, eclectic, and erratic 4 weeks ago:
Newlines and paragraph breaks have my ENTIRE support!
- Comment on I made a Firefox fork with Fediverse integration 4 weeks ago:
The Lemmy extension allows you to see and link directly to lemmy discussions on whatever instance you like (multiple even) if you’re on a site/news article/blog post/whatever. If the extension sees that this has been posted on Lemmy, it will provide you with a direct link to whatever discussions it finds based on the current URL you’re on.
So wait, it reports all browsing activity you do to third parties to search for matching Lemmy posts?
Bad, bad, system.
You’ve completely lost the point of why we’re here in Lemmy in the first place. Restrain or remove this feature ASAP.
- Comment on NSFW on Lemmy 1 month ago:
I am amazed at how helpless some people…
It’s what TikTok did to a generation. It’s incredible.
Back in my day, I could even program the time on the VCR!
- Comment on NSFW on Lemmy 1 month ago:
A new user will know because they sign in and they get access to more features of the instance, such as ability to follow, star, block, etc.
A mere visitor, can simply be pointed to the /all button. It just does not need to be the default.
- Comment on NSFW on Lemmy 1 month ago:
Porn like stuff
Which one, exactly? A woman showing a nipple? Artistic renditions of men in classic statues? A furry? A LGBTQ person existing?
That’s how it begins. We’ve already seen how it ends.
- Comment on NSFW on Lemmy 1 month ago:
There is a fair point to make that it’s instances that should default to /local instead of /all - at least for uncredentialed guests. Since if you want to see more, you can just get to the next instance, and the next, and the next…, and that way we avoid reloading basically the same content and stuff on every instance you visit.
And it helps instances better moderate how they present themselves to potential sign-ups.
- Comment on NSFW on Lemmy 1 month ago:
History has proven you wrong since as early as the Dark Ages and as recently as two weeks ago in the UK.
- Comment on NSFW on Lemmy 1 month ago:
[…] and I don’t want it in /all.
Skill issue. That’s literally what /all is for.
Block what you don’t want, or set your starting page to subscribed and curate from there. That’s half the point of this entire place.
The other half you already did the work: notified the comms they have to set to NFW, etc.
- Comment on Lemmy User Feedback and Improvement Thread: Share Your Complaints, Suggestions, and Ideas 1 month ago:
My usual concern with force redirecting people to “where the stuff is popular” is that it promotes centralization, which is the literal opposite of why we’re here. Besides, as I’ve commented some other times, the feasibility of user participation is not transitive across instances. !soccer@sports.xyz might have a completely different rules, mood or culture than !soccer@euro.pe , or the redirect might lead to !soccer@ya.ml which is blocked in my country or otherwise made unavailable. (I am using examples here ofc but I guess this could very well hit people in and around feddit.uk, for one).
There is literally no punishment for keeping a community open so it can sometime either grow organically or die organically. Locking them however, fully prevents either option.
- Comment on Lemmy User Feedback and Improvement Thread: Share Your Complaints, Suggestions, and Ideas 1 month ago:
…It’s literally a public communication network? The point is that what you post is seen.
If you want private there’s Signal, Jabber, etc. Wholly different purposes.
- Comment on Lemmy User Feedback and Improvement Thread: Share Your Complaints, Suggestions, and Ideas 1 month ago:
If they are locked, the people who come here and see them locked will go elsewhere instead of contributing, because they literally can’t.
Some people came here to creat communities (eg.: in the wake of Reddit stuff) with the hope that it would catch on. But we can’t expect them to do all the work.