𝙣𝙪𝙠𝙚
- 0 Posts
- 32 Comments
Browser detection is rarely done through User Agent lookup anymore. Nowadays we determine browser through feature detection.
In my honest and probably very controversial opinion, Lemmy is not more private than say using Reddit.
Not an expert, but I am a self hoster.
Not everything is but yes, some things can be seen. Your saved posts are only visible to your local instance admins not every admin. Your subscriptions are visible to your local admin as well the admin of the community can see you are subscribed. Your DMs are visible to your local admins as well as the recipient’s admins. Your votes and comments will be visible to all federated admins. If you report a post, that report is visible to your local admins, the community’s mods and admins, and the reported person’s instance admins.
Say no more, I’m sold
The killing
Once again, this system does not kill autonomously. It merely drives autonomously.
So automated driving is dystopian? Brace yourself, I have news about self-driving cars
A system that can maneuver autonomously is dystopian? Lol, what? This system does NOT fire autonomously
The tank-like robot has the ability to transport itself to a preset destination. It can also spot and avoid obstacles
Source: this article
I had an idea about this today but I don’t know enough about Lemmy to confirm it. Thought I’d run it by you just in case.
Could you create a post and lock it normally, then directly edit the postgres row to unlock the post? I’m wondering if this would federate the lock but not federate your unlock causing all outside users to see a lock and all internal users see an unlocked post.
Possible edge case: users who subscribe to the community after the unlock will receive the initial data dump of posts and this will include the post in its current unlocked state.
However, this would be an easy way to block the majority commenting on a post while maintaining a seemless experience for your internal users.
The patient was already in the ambulance and died because they got blocked heading to the hospital.
The GPU cluster. The H100 GPUs are about $40,000 each and you need many.
Wouldn’t it make a difference in cases where the nameserver and host are not the same entity?
The F35 costs about 80 million and they sell like hotcakes. Yes, 6 million is cheap.
Great work!
This got me thinking, does Lemmy clear orphan pictrs files? Say a user uploads an image but never submits the comment/post? That file is still on your pictrs and publicly linkable. And what if the post or comment is removed by moderator or deleted by the author? Is Lemmy cleaning these up?
Hey, don’t knock it till you try it
If the intention is to have an internal, instance-only post, I believe such a thing could be enforced with an automoderator bot. I had a lot of success throwing the Lemmy API into an AI and generating my own moderator bot from that. Could work for you.
Fair point, I agree there should be such a check. It seems for now that the only ones affected were people who tried to intentionally mess with it. It will be a hard goal to reach completely because what’s ok and healthy for some could also be a deathly allergic reaction for others. There’s always going to have to be some personal accountability for the person preparing a meal to understand what they’re making is safe.
That’s a bit dramatic of a take. The AI makes recipe suggestions based on ingredients the user inputs. These users inputted things like bleach and glue, and other non-food items, to intentionally generate non-food recipes.
Good thing we have a legit Forbes article to back this up!
I tend to agree. I think there’s little need as a developer to go that extra mile for accurate browser detection without UA unless it’s for fingerprinting. Most feature sets are supported and where it isn’t you have a polyfil or whatever shim to make it work. So in the case of fingerprinting you try not to rely fully on anything the user can alter easily.