I love to hear about a Canadian alternative.
Detect is way too expensive because of the amount of unique visitors you get. When you federate and post, you’ll see your unique visitors climb fast.
Lemmy.ca gets it free I think because they are a non profit and deflect is being generous.
cross-posted from: https://feddit.uk/post/45160218
cross-posted from: https://feddit.uk/post/45160073
I’ve been working on Habitat for the past two years. It all stemmed from this idea that I posted in April 2024.
Habitat is a free open-source, self hosted social platform for local communities. It is aimed at fostering local community discussions and discovery of areas of interest. This is why it is built primarily around location. A Habitat instance centers on a specific area, and the local community can make generic posts about that area, or they can make posts about specific locations in that area. More about what I’ve been building and the future plans here.
Features
- Habitat specification of location and size - enabling posts related to the local area
- Home feed - Displays the most recent posts
- Nearby feed - Displays posts sorted by proximity to the user
- Create posts - Upload photos, set locations, comments
- Categories - Location rules
- Amazon S3 image storage option
- Personalisation - Overrides Habitat defaults per user: kms/miles, hidden categories
- Moderation tools - User, post, comment moderation, block email addresses
- Announcements - Scheduled announcements
- Public moderation log - Keep moderator actions visible for 30 days
If you’re interest in this at all, please give it a spin and let me know how you get on. I’ll keep an eye here on Lemmy, but you can also post to the Habitat discussion board on GitHub.
That’s an interesting idea. I think this would be most successful in a city that prides itself on being high-tech. Maybe somewhere in Japan or somewhere in Silicon Valley or something.
Nice that doesn’t sound too hard
Piefed currently has anonymous — or more accurately, pseudonymous, voting.
which in my opinion is a great thing. I really think this feature is important.
However, while it works great to hide votes from casual users, the current system is trivially easy to correlate accounts to their voting profiles. Unless they adopt specific behaviours with large friction (ie. not voting on any post or comment you reply to, not voting on any community you participate in). And even then, timestamps of activity and general activity level will probably still be enough.
My question basically is, is there a plan to mitigate this? Possibly through optional features like voting profiles being ephemeral (like you get reassigned a new one every X weeks or posts).
Btw really appreciate the Piefed devs.
The score is just the first 4 lines, up to (and including) the first closing curly bracket. I’m afraid the Attitude and Reputation on the profile page can’t be handled this way (with CSS) as they’re not in some sort of container. You’d need to write a feature request and have that changed in the code.
Once again, thank you very much. I just did that it’s working nice :)
For anyone curious, here is what it looks like now:
Important progress has been made regarding bringing MLS end-to-end encryption to the ActivityPub protocol, with developers already building implementations and providing feedback to a future version of the protocol spec.
nothing per se, depends on implementation
TLDR: an e2ee channel means “everything passing over this channel is super secure and private, but it needs some keys for this to work”. e2ee means something: you can not care about most issues with delivery and protection and such, but you need to care about the keys. if you don’t do that, you are probably ruining the security of such e2ee channel
end-to-end-encryption solves one issue: transport over untrusted middleware, doesn’t mean much by itself. it’s being flung around a lot because without proper understanding sounds secure and private.
it’s like saying that i ship you something valuable with a super strong and impenetrable safe. but what do i do with the key? e2ee is the safe, solves the “how can i send you something confidential when i dont trust those who deliver it”, and it means much! it’s a great way to do it.
but it solves one problem giving a new one: what to do with the key? this usually can be combined with other technologies, such as asymmetric encryption (e.g. RSA), which allows having keys which can be publicly shared without compromising anything. so i send you an impenetrable code-protected safe with an encrypted code attached, and only your privkey can decrypt the code since i used your pubkey!
(note: RSA is used for small data since encryption/decryption is cpu intensive. usually what happens is that you share an AES key encrypted with RSA, and the payload is encrypted using that AES key. AES is symmetric: one key encrypts and decrypts, but AES keys are small. another piece of technology attached to make this system work!)
but now comes the user-friendliness issue: very few are big enough nerds to handle their keys. hell, most folks don’t even want to handle their passwords! so services like matrix offer to hold your keys on the server, encrypted with another passphrase, so that you don’t need to bother doing that, just remember 2 passwords or do the emoji compare stuff. it’s meh: compromising the server could allow getting your keys and kinda spoils e2ee, but it’s convenient and reasonably secure.
what does whatsapp do? i don’t know! but it kind of magically works. if they do e2ee, where are the keys???? how does meta handle reports if messages are e2ee???????
also, e2ee works if you can trust the key you’re sending to! as mentioned in the ‘activitypub keys’ section before, if you ask a middleman the key for your recipient, can you trust that’s the real key? e2ee doesn’t cover that, it’s not in its scope
so what does e2ee mean? it means: super strong channel, ASSUMING keys are safe and trusted. e2ee as a technology doesn’t solve “all privacy” or guarantee that nobody snoops in per se. it offers a super safe channel protected by keys, and lets you handle those keys how you more see fit. which meaning deciding who you trust to send, how you let others know how to encrypt for you (aka share your pubkey) and how you will keep your privkey safe.
