Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)GR
grant 🍞 @ grant @toast.ooo
Posts
24
Comments
80
Joined
2 yr. ago

  • Key reselling sites are often pretty sketchy, I’d go HumbleBundle route as that’s approved by the game devs

    If you are worried about unwanted charges on your card I’d try Privacy.com to get a temporary card at least

  • With the feature request I posted on GitHub, it would work similarly to reposting/reblogging on Mastodon.

    Except inside Lemmy anyone who can post in the community would (most likely) create a post linking to an existing post and it would appear that the post mentioned just got posted into that community

    Moderators would ideally see who created that crosspost and have the ability to block that person from crossposting (or posting entirely) to that community w/o affecting the third-party post

    If someone wouldn't want their posts crossposted they can just block the community's actor (account)

  • It would also allow for Lemmy users to crosspost posts from other Fediverse services, such as Mastodon

    Eg you see a post on Mastodon that would fit great in a startrek community, you would be able to cross post that Mastodon post into that community

    This would enable individual posts to gain traction and comments without having comments/replies being spread across multiple places

    Edit: it would work very similarly to reposting/reblogging on mastodon

  • Video hosting is a very expensive process and peertube does a lot more stuff to video files compared to Lemmy/mastodon

    I’m not sure if this would be feasible for development or peertube hosts but idk, it would be a neat idea though

  • I don't know Rust well enough to implement it in the core of Lemmy, instead it'd be another service instances would run then do some reverse proxy magic to properly run it on their servers

    but I'm planning to use it for canvas 2024, so in a couple months there should be at least a functional version published on github (or some other code platform) (i'll post updates to this on !canvas@toast.ooo & probably my mastodon)

  • If you’re worried about notifying the sender that you are a real person, it’s probably not great interacting with the links at all because they are linked directly to your email (same with normal unsubscribe links)

  • Instead of a weather api, it would be better to allow communities to specify locations (stored as coordinates probably?) to allow third party apps to do what they would like with it (like display the weather)

    Either that or make a standardized way to put location information in the community description and then convince a third party app to support it

  • I ran into this issue when writing the Canvas authentication thing

    There is a standard to simplify authentication and identification across the entire web but it isn’t fully implemented everywhere

    OAuth2 is the big name in this, it supplies authorized requests to access data from other companies and services

    OpenID is related to OAuth2 but it only supplies identification in a standardized way. OpenID has mechanisms to announce that a specific domain has support for this and how to automatically register for it (removing the need to have a bunch of login buttons)

    For Canvas 2024 I’m implementing drop in implementations for popular Fediverse software (including Lemmy)

    Hopefully more fedi software implements OAuth2 or at least OpenID to vastly simplify authentication (and possibly replace “login with google”)

    Related Links: