GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by LisPi (lispi314@udongein.xyz)

  1. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Tuesday, 10-Feb-2026 21:28:30 JST LisPi LisPi
    Imagine still willingly using languages where buffer overflows are possible.

    (Yes, unfortunately if works mandates it you're out of luck.)
    In conversation about 2 days ago from udongein.xyz permalink
  2. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Monday, 09-Feb-2026 21:27:04 JST LisPi LisPi
    in reply to
    • iced depresso
    @icedquinn > i found a protein based bread i can eat its been quite enjoyable lately :ablobcatnomcookie:

    That sounds nice.

    > not enough people actually understand kaczynsky's point that the system permits dissent only that lets people feel represented, and then shovels the dissent in to a fully contained direction.

    I've seen the point enunciated and made several times over the years. Honestly it's weirder for people to either not notice it themselves or hear it spoonfed to them considering how easy it is to come by it.

    My understanding of neoliberalism is that it primarily promotes the "temporarily embarrassed billionaire" delusion while eliminating controls (and potential points thereof) on the actual ones (who should be used for corpse starch).
    In conversation about 3 days ago from udongein.xyz permalink
  3. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Monday, 09-Feb-2026 21:16:10 JST LisPi LisPi
    in reply to
    • iced depresso
    @icedquinn I have both heard of and observed it. It is something for which people need to be held accountable for.
    In conversation about 3 days ago from udongein.xyz permalink
  4. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Monday, 09-Feb-2026 21:11:19 JST LisPi LisPi
    This being said, chat, do you think it's about a particular one or just a general warning?
    In conversation about 3 days ago from udongein.xyz permalink
  5. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Saturday, 07-Feb-2026 12:30:09 JST LisPi LisPi

    @vie It's worth noticing that the ones most enthusiastic about it are also the ones that care the least about their craft and were only ever in it because it was a well-paying job (in some places, they wouldn't have chosen it otherwise).

    That's not a coincidence.

    In conversation about 5 days ago from udongein.xyz permalink
  6. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Saturday, 07-Feb-2026 12:23:53 JST LisPi LisPi
    I wonder how much of Java's infamous "memory hungry" reputation is simply it not having sane default settings for unused heap.
    In conversation about 5 days ago from udongein.xyz permalink
  7. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Friday, 06-Feb-2026 12:39:41 JST LisPi LisPi
    in reply to
    • iced depresso
    @icedquinn I am/was waiting on relay gossip features being implemented, so that one's posts aren't dependent on the uptime of relays that existed at the time the post was made.

    Then I might bother to review the code for a simple client and try it out.
    In conversation about 6 days ago from udongein.xyz permalink
  8. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Friday, 06-Feb-2026 12:39:38 JST LisPi LisPi
    in reply to
    • iced depresso

    @icedquinn > i'm not too aware of any gossip features, although if relays do negentropy syncs (many softs support it) then a message will eventually crawl across the network that way.

    I don't recall quite perfectly, but the protocol documentation alluded to that being in the works.

    though it looks like the latest generation of nostr has been about gatekeeping. paid relays like primal or FOAF relays like pyramid.

    Huh. Is it going to go to shit before I even get to try it? lol

    In conversation about 6 days ago from udongein.xyz permalink
  9. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Friday, 06-Feb-2026 09:59:26 JST LisPi LisPi

    I think Linux distro system administration guides kind of messed up a lot in the past.

    Especially rolling distros for "didn't update in a while" procedures.

    With adequate partitioning of either LVM or btrfs/zfs managed storage, it's very possible to just use COW snapshots so that failed upgrades are as simple to revert & retry as booting a live CD, destroying the old partition (subvolume/lvm volume) and restoring it from a snapshot.

    I do see mention of chrooting & reinstalling while leaving /home (or similar) untouched but nothing about snapshots despite how long the functionality has been around.

    Sure backup away, but you really shouldn't need to touch your backups at all.

    In conversation about 6 days ago from udongein.xyz permalink
  10. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Sunday, 01-Feb-2026 16:29:36 JST LisPi LisPi
    in reply to
    • Rich Felker
    • Jenniferplusplus
    @dalias @jenniferplusplus Only if it's a bad paper.

    Especially if it then goes on to debunk those very same assumptions while refusing to remark on it.

    This is distinct from presenting a premise as a hypothetical to verify.
    In conversation about 11 days ago from udongein.xyz permalink
  11. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Sunday, 01-Feb-2026 06:35:03 JST LisPi LisPi
    in reply to
    • McNadoMD
    @mcnado I wonder what precautions they take about people tracing where the devices end-up.
    In conversation about 11 days ago from udongein.xyz permalink
  12. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Sunday, 01-Feb-2026 06:34:59 JST LisPi LisPi
    in reply to
    • McNadoMD
    @mcnado The owner is taking some major risks not refusing them business.
    In conversation about 11 days ago from udongein.xyz permalink
  13. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Sunday, 01-Feb-2026 01:25:40 JST LisPi LisPi
    • eris
    @eris The kind of schizo conspiracy thing that turns out true. Damn.
    In conversation about 11 days ago from udongein.xyz permalink
  14. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Friday, 30-Jan-2026 07:55:53 JST LisPi LisPi

    I would recommend the use of the memtest parameter in Linux kernel parameters as a precautionary measure, especially if one doesn't have ECC memory.

    The setting should be >1 (e.g. memtest=7) because if the test is mere zeroing, then that won't be enough on its own to catch a number of malfunctions.

    Errors caught result in segments being automatically reserved so the kernel and programs do not use them.

    This is of course not going to protect against faults that develop during the current uptime of a machine. It is a stopgap measure, not a replacement for ECC memory.

    In conversation about 13 days ago from udongein.xyz permalink
  15. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Thursday, 29-Jan-2026 13:02:29 JST LisPi LisPi
    in reply to
    • djsumdog
    • Natty :butterflyN:
    @djsumdog @natty Python3 had major changes in its JSON library on minor version changes. A breaking change that completely disregarded semver.

    It was not the only one of its kind, that one just stuck with me.
    In conversation about 14 days ago from gnusocial.jp permalink
  16. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Thursday, 29-Jan-2026 12:57:56 JST LisPi LisPi
    in reply to
    • Natty :butterflyN:
    @natty Nontrivial shellscripts should be avoided.

    Shellscripts should be avoided outside of constrained environments.

    While commonly one would recommend Perl or Python, I'd say that some manner of standard-compliant Scheme or Common Lisp should be used if at all possible.

    Perl is somewhat stable and readable (but it also is implementation-defined), but Python is not stable and does a bad job of pretending it is (that script I wrote a decade ago should not have needed any modification to keep working, it had no non-stdlib dependencies).
    In conversation about 14 days ago from gnusocial.jp permalink
  17. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Thursday, 04-Dec-2025 13:57:31 JST LisPi LisPi
    in reply to
    • djsumdog
    • allison
    • Reid 🖤
    @djsumdog @reiddragon @aparrish Mostly not mine directly, but that's pretty much going to happen because we collectively stupidly let silicon manufacture concentrate into a few foreign companies, nevermind how that creates major risks should they be destroyed in some way or other.

    While I will admit that every-nation autarky would be impractical for computer manufacture, it would very much be possible to decentralize it more.
    In conversation about 2 months ago from udongein.xyz permalink
  18. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Thursday, 04-Dec-2025 13:53:00 JST LisPi LisPi
    in reply to
    • allison
    • Reid 🖤
    @reiddragon @aparrish Eagerly awaiting for the AI crash.
    In conversation about 2 months ago from udongein.xyz permalink
  19. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Tuesday, 02-Dec-2025 02:16:39 JST LisPi LisPi
    in reply to
    • Em :official_verified:
    • Rich Felker
    • Dave Mason
    @dalias @DaveMasonDotMe @Em0nM4stodon Site operators who do this are throwing a red flag indicating that you should discontinue use of their site as they have zero respect for you and their other users (and therefore deserve zero respect in return).

    This is again something that would be avoided by key-addressing (which would also provide end-to-end encryption for free) and which reflects fundamental problems with the currently directly-used net.
    In conversation about 2 months ago from udongein.xyz permalink
  20. Embed this notice
    LisPi (lispi314@udongein.xyz)'s status on Sunday, 23-Nov-2025 22:09:52 JST LisPi LisPi
    in reply to
    • iced depresso
    • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
    • affine
    @icedquinn @allison @affine Not what I meant. Consider even just how much the Briar desktop client lags behind compared to the mobile one (for an example that isn't actually abandoned).

    And browsers are *built* for the web, obviously things that rely on it will work with browsers.

    I do not consider delays and difficulties in obtaining distributed data to be the fault of implementations, they are difficulties inherent to the schema. Which I specifically outlined as out of scope.
    In conversation about 3 months ago from udongein.xyz permalink
  • Before

User actions

    LisPi

    LisPi

    Hi, I'm Lispi, Lisp (Technomancer) Wizard (to eventually be).You might know me from @lispi314@mastodon.top I like Free Software, #Emacs and resilient computing a lot.I also like anime girls, animes with cute girls doing cute things and artwork with them too. Cute stories are good too.Some Pins:Software and Assumed Privilege, common problems: https://mastodon.top/@lispi314/111253066257920146Writing Privacy-preserving software & services 101: https://mastodon.top/@lispi314/110849018589421824#Kopimism #FreeSoftware #CommonLisp

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          209694
          Member since
          6 Nov 2023
          Notices
          856
          Daily average
          1

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.